Home
last modified time | relevance | path

Searched full:gnss (Results 1 – 25 of 45) sorted by relevance

12

/openbmc/linux/drivers/net/ethernet/intel/ice/
H A Dice_gnss.c8 * ice_gnss_do_write - Write data to internal GNSS receiver
13 * Write UBX command data to the GNSS receiver
72 dev_err(ice_pf_to_dev(pf), "GNSS failed to write, offset=%u, size=%u, err=%d\n", in ice_gnss_do_write()
79 * ice_gnss_read - Read data from internal GNSS module
80 * @work: GNSS read work structure
82 * Read the data from internal GNSS receiver, write it to gnss_dev.
86 struct gnss_serial *gnss = container_of(work, struct gnss_serial, in ice_gnss_read() local
98 pf = gnss->back; in ice_gnss_read()
156 kthread_queue_delayed_work(gnss->kworker, &gnss->read_work, delay); in ice_gnss_read()
158 dev_dbg(ice_pf_to_dev(pf), "GNSS failed to read err=%d\n", err); in ice_gnss_read()
[all …]
H A Dice_gnss.h26 * struct gnss_serial - data used to initialize GNSS TTY port
29 * @read_work: read_work function for handling GNSS reads
/openbmc/linux/drivers/gnss/
H A DKconfig3 # GNSS receiver configuration
6 menuconfig GNSS config
7 tristate "GNSS receiver support"
9 Say Y here if you have a GNSS receiver (e.g. a GPS receiver).
12 be called gnss.
14 if GNSS
20 tristate "Mediatek GNSS receiver support"
24 Say Y here if you have a Mediatek-based GNSS receiver which uses a
28 be called gnss-mtk.
33 tristate "SiRFstar GNSS receiver support"
[all …]
H A DMakefile3 # Makefile for the GNSS subsystem.
6 obj-$(CONFIG_GNSS) += gnss.o
7 gnss-y := core.o
9 obj-$(CONFIG_GNSS_SERIAL) += gnss-serial.o
10 gnss-serial-y := serial.o
12 obj-$(CONFIG_GNSS_MTK_SERIAL) += gnss-mtk.o
13 gnss-mtk-y := mtk.o
15 obj-$(CONFIG_GNSS_SIRF_SERIAL) += gnss-sirf.o
16 gnss-sirf-y := sirf.o
18 obj-$(CONFIG_GNSS_UBX_SERIAL) += gnss-ubx.o
[all …]
H A Dcore.c3 * GNSS receiver core
13 #include <linux/gnss.h>
250 dev_set_name(dev, "gnss%d", id); in gnss_allocate_device()
366 ATTRIBUTE_GROUPS(gnss);
384 ret = alloc_chrdev_region(&gnss_first, 0, GNSS_MINORS, "gnss"); in gnss_module_init()
390 gnss_class = class_create("gnss"); in gnss_module_init()
400 pr_info("GNSS driver registered with major %d\n", MAJOR(gnss_first)); in gnss_module_init()
420 MODULE_DESCRIPTION("GNSS receiver core");
H A Dmtk.c3 * Mediatek GNSS receiver driver
9 #include <linux/gnss.h>
141 .name = "gnss-mtk",
151 MODULE_DESCRIPTION("Mediatek GNSS receiver driver");
H A Dubx.c3 * u-blox GNSS receiver driver
9 #include <linux/gnss.h>
143 .name = "gnss-ubx",
153 MODULE_DESCRIPTION("u-blox GNSS receiver driver");
H A Dusb.c3 * Generic USB GNSS receiver driver
9 #include <linux/gnss.h>
205 .name = "gnss-usb",
213 MODULE_DESCRIPTION("Generic USB GNSS receiver driver");
H A Dserial.c3 * Generic serial GNSS receiver driver
9 #include <linux/gnss.h>
275 MODULE_DESCRIPTION("Generic serial GNSS receiver driver");
H A Dsirf.c3 * SiRFstar GNSS receiver driver
9 #include <linux/gnss.h>
570 .name = "gnss-sirf",
580 MODULE_DESCRIPTION("SiRFstar GNSS receiver driver");
H A Dserial.h3 * Generic serial GNSS receiver driver
/openbmc/linux/Documentation/devicetree/bindings/gnss/
H A Dgnss-common.yaml4 $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 GNSS
27 description: A GPIO line that will enable the GNSS receiver when
30 system can rely on asserting the line to enable the GNSS device.
34 description: When a timepulse is provided to the GNSS device using a
49 gnss {
H A Dmediatek.yaml4 $id: http://devicetree.org/schemas/gnss/mediatek.yaml#
7 title: Mediatek GNSS Receiver
13 Mediatek chipsets are used in GNSS-receiver modules produced by several
17 - $ref: gnss-common.yaml#
35 gnss-fix-gpios:
54 gnss {
H A Du-blox,neo-6m.yaml4 $id: http://devicetree.org/schemas/gnss/u-blox,neo-6m.yaml#
7 title: U-blox GNSS Receiver
10 - $ref: gnss-common.yaml#
16 The U-blox GNSS receivers can use UART, DDC (I2C), SPI and USB interfaces.
53 gnss {
H A Dsirfstar.yaml4 $id: http://devicetree.org/schemas/gnss/sirfstar.yaml#
7 title: SiRFstar GNSS Receiver
13 The SiRFstar GNSS receivers have incarnated over the years in different
23 - $ref: gnss-common.yaml#
68 gnss {
H A Dbrcm,bcm4751.yaml4 $id: http://devicetree.org/schemas/gnss/brcm,bcm4751.yaml#
7 title: Broadcom BCM4751 family GNSS Receiver
20 - $ref: gnss-common.yaml#
62 gnss {
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-class-gnss1 What: /sys/class/gnss/gnss<N>/type
6 The GNSS receiver type. The currently identified types reflect
H A Dsysfs-timecard23 TOD adjustments from the GNSS/TOD module
60 GNSS1 output PPS is from the first GNSS module
61 GNSS2 output PPS is from the second GNSS module
173 Description: (RO) Indicates whether a valid GNSS signal is received,
236 Description: (RW) The incoming GNSS signal is in UTC time, and the NMEA
266 associated with the GNSS devices.
/openbmc/linux/Documentation/driver-api/
H A Dptp.rst124 … - Lock to GNSS input, automatic switching between GNSS and user-space PHC control (optional)
/openbmc/linux/include/linux/
H A Dgnss.h3 * GNSS receiver support
/openbmc/linux/Documentation/networking/device_drivers/ethernet/intel/
H A Dice.rst887 GNSS module
890 Allows user to read messages from the GNSS hardware module and write supported
891 commands. If the module is physically present, a GNSS device is spawned:
892 ``/dev/gnss<id>``.
893 The protocol of write command is dependent on the GNSS hardware module as the
894 driver writes raw bytes by the GNSS object to the receiver through i2c. Please
895 refer to the hardware GNSS module documentation for configuration details.
/openbmc/linux/drivers/thunderbolt/
H A Dsb_regs.h25 USB4_SB_OPCODE_GET_NVM_SECTOR_SIZE = 0x53534e47, /* "GNSS" */
/openbmc/linux/drivers/net/ethernet/intel/
H A DKconfig282 depends on GNSS || GNSS = n
/openbmc/linux/drivers/
H A DKconfig24 source "drivers/gnss/Kconfig"
/openbmc/linux/Documentation/devicetree/bindings/serial/
H A Dserial.yaml99 "^(bluetooth|gnss|gps|mcu)$":

12