.. | .. |
---|
| 1 | +# SPDX-License-Identifier: GPL-2.0-only |
---|
1 | 2 | # |
---|
2 | 3 | # GNSS receiver configuration |
---|
3 | 4 | # |
---|
4 | 5 | |
---|
5 | 6 | menuconfig GNSS |
---|
6 | 7 | tristate "GNSS receiver support" |
---|
7 | | - ---help--- |
---|
| 8 | + help |
---|
8 | 9 | Say Y here if you have a GNSS receiver (e.g. a GPS receiver). |
---|
9 | 10 | |
---|
10 | 11 | To compile this driver as a module, choose M here: the module will |
---|
.. | .. |
---|
15 | 16 | config GNSS_SERIAL |
---|
16 | 17 | tristate |
---|
17 | 18 | |
---|
| 19 | +config GNSS_MTK_SERIAL |
---|
| 20 | + tristate "Mediatek GNSS receiver support" |
---|
| 21 | + depends on SERIAL_DEV_BUS |
---|
| 22 | + select GNSS_SERIAL |
---|
| 23 | + help |
---|
| 24 | + Say Y here if you have a Mediatek-based GNSS receiver which uses a |
---|
| 25 | + serial interface. |
---|
| 26 | + |
---|
| 27 | + To compile this driver as a module, choose M here: the module will |
---|
| 28 | + be called gnss-mtk. |
---|
| 29 | + |
---|
| 30 | + If unsure, say N. |
---|
| 31 | + |
---|
18 | 32 | config GNSS_SIRF_SERIAL |
---|
19 | 33 | tristate "SiRFstar GNSS receiver support" |
---|
20 | 34 | depends on SERIAL_DEV_BUS |
---|
21 | | - ---help--- |
---|
| 35 | + help |
---|
22 | 36 | Say Y here if you have a SiRFstar-based GNSS receiver which uses a |
---|
23 | 37 | serial interface. |
---|
24 | 38 | |
---|
.. | .. |
---|
31 | 45 | tristate "u-blox GNSS receiver support" |
---|
32 | 46 | depends on SERIAL_DEV_BUS |
---|
33 | 47 | select GNSS_SERIAL |
---|
34 | | - ---help--- |
---|
| 48 | + help |
---|
35 | 49 | Say Y here if you have a u-blox GNSS receiver which uses a serial |
---|
36 | 50 | interface. |
---|
37 | 51 | |
---|
.. | .. |
---|
44 | 58 | tristate "Command line test driver for GNSS" |
---|
45 | 59 | depends on SERIAL_DEV_BUS |
---|
46 | 60 | select GNSS_SERIAL |
---|
47 | | - ---help--- |
---|
| 61 | + help |
---|
48 | 62 | Say Y here if you want to test the GNSS subsystem but do not have a |
---|
49 | 63 | way to communicate a binding through firmware such as DT or ACPI. |
---|
50 | 64 | The correct serdev device and protocol type must be specified on |
---|