Home
last modified time | relevance | path

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

12

/linux/drivers/net/ethernet/intel/ice/
H A Dice_gnss.c9 * ice_gnss_do_write - Write data to internal GNSS receiver
14 * Write UBX command data to the GNSS receiver
73 dev_err(ice_pf_to_dev(pf), "GNSS failed to write, offset=%u, size=%u, err=%d\n", in ice_gnss_do_write()
80 * ice_gnss_read - Read data from internal GNSS module
81 * @work: GNSS read work structure
83 * Read the data from internal GNSS receiver, write it to gnss_dev.
87 struct gnss_serial *gnss = container_of(work, struct gnss_serial, in ice_gnss_read() local
99 pf = gnss->back; in ice_gnss_read()
157 kthread_queue_delayed_work(gnss->kworker, &gnss->read_work, delay); in ice_gnss_read()
159 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
/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>
249 dev_set_name(dev, "gnss%d", id); in gnss_allocate_device()
365 ATTRIBUTE_GROUPS(gnss);
383 ret = alloc_chrdev_region(&gnss_first, 0, GNSS_MINORS, "gnss"); in gnss_module_init()
389 gnss_class = class_create("gnss"); in gnss_module_init()
399 pr_info("GNSS driver registered with major %d\n", MAJOR(gnss_first)); in gnss_module_init()
419 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 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
/linux/Documentation/devicetree/bindings/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#
36 gnss-fix-gpios:
55 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#
69 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#
63 gnss {
/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
271 ports associated with the GNSS devices.
/linux/Documentation/devicetree/bindings/dpll/
H A Dmicrochip,zl30731.yaml84 connection-type = "gnss";
110 connection-type = "gnss";
117 connection-type = "gnss";
130 connection-type = "gnss";
/linux/drivers/net/wwan/
H A Dwwan_core.c23 #include <linux/gnss.h>
84 * @gnss: Pointer to GNSS device associated with this port
103 struct gnss_device *gnss; member
353 /* WWAN_PORT_NMEA is exported via the GNSS subsystem */
568 /* GNSS port specific device registration */
580 * the GNSS port type. If more GNSS WWAN port types will be added, in wwan_port_register_gnss()
581 * then we should dynamically map WWAN port type to GNSS type. in wwan_port_register_gnss()
587 port->gnss = gdev; in wwan_port_register_gnss()
600 /* GNSS port specific device unregistration */
604 struct gnss_device *gdev = port->gnss; in wwan_port_unregister_gnss()
[all …]
/linux/Documentation/driver-api/
H A Dptp.rst124 … - Lock to GNSS input, automatic switching between GNSS and user-space PHC control (optional)
/linux/include/linux/
H A Dgnss.h3 * GNSS receiver support
/linux/Documentation/networking/device_drivers/ethernet/intel/
H A Dice.rst944 GNSS module
947 Allows user to read messages from the GNSS hardware module and write supported
948 commands. If the module is physically present, a GNSS device is spawned:
949 ``/dev/gnss<id>``.
950 The protocol of write command is dependent on the GNSS hardware module as the
951 driver writes raw bytes by the GNSS object to the receiver through i2c. Please
952 refer to the hardware GNSS module documentation for configuration details.
/linux/arch/arm/boot/dts/ti/omap/
H A Dlogicpd-torpedo-37xx-devkit.dts55 bluetooth-gnss {
/linux/drivers/net/ethernet/intel/
H A DKconfig296 depends on GNSS || GNSS = n
/linux/drivers/
H A DKconfig32 source "drivers/gnss/Kconfig"
/linux/arch/arm64/boot/dts/marvell/
H A Dcn9132-clearfog.dts103 rfkill-m2-gnss {
105 label = "m.2 gnss (J21)";
/linux/Documentation/netlink/specs/
H A Ddpll.yaml166 name: gnss
167 doc: GNSS recovered clock

12