Searched full:gnss (Results 1 – 25 of 37) sorted by relevance
12
4 $id: http://devicetree.org/schemas/gnss/gnss-common.yaml#7 title: Common Properties for Global Navigation Satellite Systems (GNSS)19 pattern: "^gnss(@.*)?$"23 Amplifier (LNA). This is an amplifier connected between the GNSS27 description: A GPIO line that will enable the GNSS receiver when30 system can rely on asserting the line to enable the GNSS device.34 description: When a timepulse is provided to the GNSS device using a44 gnss {
1 Mediatek-based GNSS Receiver DT binding3 Mediatek chipsets are used in GNSS-receiver modules produced by several6 Please see Documentation/devicetree/bindings/gnss/gnss.txt for generic20 - gnss-fix-gpios : GPIO used to determine device position fix state31 gnss {
4 $id: http://devicetree.org/schemas/gnss/mediatek.yaml#7 title: Mediatek GNSS Receiver13 Mediatek chipsets are used in GNSS-receiver modules produced by several17 - $ref: gnss-common.yaml#36 gnss-fix-gpios:55 gnss {
1 GNSS Receiver DT binding3 This documents the binding structure and common properties for GNSS receiver6 A GNSS receiver node is a node named "gnss" and typically resides on a serial29 gnss {
1 u-blox GNSS Receiver DT binding3 The u-blox GNSS receivers can use UART, DDC (I2C), SPI and USB interfaces.5 Please see Documentation/devicetree/bindings/gnss/gnss.txt for generic39 gnss {
1 SiRFstar-based GNSS Receiver DT binding3 SiRFstar chipsets are used in GNSS-receiver modules produced by several6 Please see Documentation/devicetree/bindings/gnss/gnss.txt for generic39 gnss {
4 $id: http://devicetree.org/schemas/gnss/u-blox,neo-6m.yaml#7 title: U-blox GNSS Receiver10 - $ref: gnss-common.yaml#17 The U-blox GNSS receivers can use UART, DDC (I2C), SPI and USB interfaces.59 gnss {
4 $id: http://devicetree.org/schemas/gnss/sirfstar.yaml#7 title: SiRFstar GNSS Receiver13 The SiRFstar GNSS receivers have incarnated over the years in different23 - $ref: gnss-common.yaml#69 gnss {
4 $id: http://devicetree.org/schemas/gnss/brcm,bcm4751.yaml#7 title: Broadcom BCM4751 family GNSS Receiver20 - $ref: gnss-common.yaml#63 gnss {
91 "^(bluetooth|bluetooth-gnss|embedded-controller|gnss|gps|mcu|onewire)$":
2 * ntp_calgps.h - calendar for GPS/GNSS based clocks9 * This module implements stuff often used with GPS/GNSS receivers
37 rfkill-m2-gnss {39 label = "m.2 GNSS";
103 rfkill-m2-gnss {105 label = "m.2 gnss (J21)";
215 GNSS receivers use a distinct talker ID for the GNSS they230 receiver modules. It is therefore undefined which GNSS actually232 especially true if the different GNSS provide very different signal236 single GNSS (which would defeat its purpose) or to emit only the
137 reg_gnss: regulator-gnss {141 regulator-name = "GNSS";1295 gnss {
2 * ntp_calgps.c - calendar for GPS/GNSS based clocks9 * This module implements stuff often used with GPS/GNSS receivers
698 gnss: gnss { label
466 bluetooth-gnss {
362 ngff-gnss-off-conf {
425 gnss {
486 gnss {
15 /* GNSS UART-B pinmux */
29 /* GNSS UART-B pinmux */
299 gnss {
319 gnss {