Searched refs:GNSS (Results 1 – 16 of 16) sorted by relevance
3 # GNSS receiver configuration6 menuconfig GNSS config7 tristate "GNSS receiver support"9 Say Y here if you have a GNSS receiver (e.g. a GPS receiver).14 if GNSS20 tristate "Mediatek GNSS receiver support"24 Say Y here if you have a Mediatek-based GNSS receiver which uses a33 tristate "SiRFstar GNSS receiver support"36 Say Y here if you have a SiRFstar-based GNSS receiver which uses a45 tristate "u-blox GNSS receiver support"[all …]
6 The GNSS receiver type. The currently identified types reflect
23 TOD adjustments from the GNSS/TOD module60 GNSS1 output PPS is from the first GNSS module61 GNSS2 output PPS is from the second GNSS module173 Description: (RO) Indicates whether a valid GNSS signal is received,236 Description: (RW) The incoming GNSS signal is in UTC time, and the NMEA271 ports associated with the GNSS devices.
124 … - Lock to GNSS input, automatic switching between GNSS and user-space PHC control (optional)
39 label = "m.2 GNSS";
184 GNSS = 0, enumerator
296 depends on GNSS || GNSS = n
944 GNSS module947 Allows user to read messages from the GNSS hardware module and write supported948 commands. If the module is physically present, a GNSS device is spawned:950 The protocol of write command is dependent on the GNSS hardware module as the951 driver writes raw bytes by the GNSS object to the receiver through i2c. Please952 refer to the hardware GNSS module documentation for configuration details.
15 /* GNSS UART-B pinmux */
119 /* GNSS UART-B pinmux */919 /* GNSS GSD5T */
185 /* GNSS UART-B pinmux */
958 &uart3 { /* GNSS */
141 regulator-name = "GNSS";
345 * IOT Module - GNSS UART
3461 static EXT_TTY_ATTR_RO(GNSS, PORT_GNSS);
10680 GNSS SUBSYSTEM