| /kernel/linux/linux-5.10/drivers/nfc/nfcmrvl/ |
| D | Kconfig | 11 tristate "Marvell NFC-over-USB driver"
15 Marvell NFC-over-USB driver.
17 This driver provides support for Marvell NFC-over-USB devices:
20 Say Y here to compile support for Marvell NFC-over-USB driver
24 tristate "Marvell NFC-over-UART driver"
28 Marvell NFC-over-UART driver.
30 This driver provides support for Marvell NFC-over-UART devices
32 Say Y here to compile support for Marvell NFC-over-UART driver
36 tristate "Marvell NFC-over-I2C driver"
39 Marvell NFC-over-I2C driver.
[all …]
|
| /kernel/linux/linux-4.19/drivers/nfc/nfcmrvl/ |
| D | Kconfig | 10 tristate "Marvell NFC-over-USB driver"
14 Marvell NFC-over-USB driver.
16 This driver provides support for Marvell NFC-over-USB devices:
19 Say Y here to compile support for Marvell NFC-over-USB driver
23 tristate "Marvell NFC-over-UART driver"
27 Marvell NFC-over-UART driver.
29 This driver provides support for Marvell NFC-over-UART devices
31 Say Y here to compile support for Marvell NFC-over-UART driver
35 tristate "Marvell NFC-over-I2C driver"
38 Marvell NFC-over-I2C driver.
[all …]
|
| /kernel/linux/linux-5.10/drivers/usb/gadget/function/ |
| D | u_ether.h | 95 /* gether_setup - initialize one ethernet-over-usb link
124 * Registers the net device associated with this ethernet-over-usb link
129 /* gether_setup_default - initialize one ethernet-over-usb link
144 * gether_set_gadget - initialize one ethernet-over-usb link with a gadget
148 * This associates one ethernet-over-usb link with a gadget.
153 * gether_set_dev_addr - initialize an ethernet-over-usb link with eth address
157 * This sets the device-side Ethernet address of this ethernet-over-usb link
164 * gether_get_dev_addr - get an ethernet-over-usb link eth address
169 * This gets the device-side Ethernet address of this ethernet-over-usb link.
175 * gether_set_host_addr - initialize an ethernet-over-usb link with host address
[all …]
|
| /kernel/linux/linux-4.19/drivers/usb/gadget/function/ |
| D | u_ether.h | 95 /* gether_setup - initialize one ethernet-over-usb link
124 * Registers the net device associated with this ethernet-over-usb link
129 /* gether_setup_default - initialize one ethernet-over-usb link
144 * gether_set_gadget - initialize one ethernet-over-usb link with a gadget
148 * This associates one ethernet-over-usb link with a gadget.
153 * gether_set_dev_addr - initialize an ethernet-over-usb link with eth address
157 * This sets the device-side Ethernet address of this ethernet-over-usb link
164 * gether_get_dev_addr - get an ethernet-over-usb link eth address
169 * This gets the device-side Ethernet address of this ethernet-over-usb link.
175 * gether_set_host_addr - initialize an ethernet-over-usb link with host address
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/ppp/ |
| D | Kconfig | 11 the same purpose: sending Internet traffic over telephone (and other
24 synchronous PPP which can be used over digital ISDN lines for
25 example. If you want to use PPP over phone lines or other
27 the next option, "PPP support for async serial ports". For PPP over
44 sent over the wire. The machine at the other end of the PPP link
65 each PPP packet before it is sent over the wire. The machine at the
76 Say Y here if you want to be able to filter the packets passing over
112 tristate "PPP over ATM"
121 tristate "PPP over Ethernet"
124 Support for PPP over Ethernet.
[all …]
|
| /kernel/linux/linux-4.19/drivers/net/ppp/ |
| D | Kconfig | 10 the same purpose: sending Internet traffic over telephone (and other
23 synchronous PPP which can be used over digital ISDN lines for
24 example. If you want to use PPP over phone lines or other
26 the next option, "PPP support for async serial ports". For PPP over
43 sent over the wire. The machine at the other end of the PPP link
64 each PPP packet before it is sent over the wire. The machine at the
75 Say Y here if you want to be able to filter the packets passing over
112 tristate "PPP over ATM"
121 tristate "PPP over Ethernet"
124 Support for PPP over Ethernet.
[all …]
|
| /kernel/linux/linux-4.19/drivers/misc/lkdtm/ |
| D | refcount.c | 37 refcount_t over = REFCOUNT_INIT(REFCOUNT_MAX - 1); in lkdtm_REFCOUNT_INC_OVERFLOW() local
40 refcount_dec(&over); in lkdtm_REFCOUNT_INC_OVERFLOW()
41 refcount_inc(&over); in lkdtm_REFCOUNT_INC_OVERFLOW()
44 refcount_inc(&over); in lkdtm_REFCOUNT_INC_OVERFLOW()
45 refcount_inc(&over); in lkdtm_REFCOUNT_INC_OVERFLOW()
47 overflow_check(&over); in lkdtm_REFCOUNT_INC_OVERFLOW()
53 refcount_t over = REFCOUNT_INIT(REFCOUNT_MAX - 1); in lkdtm_REFCOUNT_ADD_OVERFLOW() local
56 refcount_dec(&over); in lkdtm_REFCOUNT_ADD_OVERFLOW()
57 refcount_dec(&over); in lkdtm_REFCOUNT_ADD_OVERFLOW()
58 refcount_dec(&over); in lkdtm_REFCOUNT_ADD_OVERFLOW()
[all …]
|
| /kernel/linux/linux-5.10/drivers/misc/lkdtm/ |
| D | refcount.c | 29 refcount_t over = REFCOUNT_INIT(REFCOUNT_MAX - 1); in lkdtm_REFCOUNT_INC_OVERFLOW() local
32 refcount_dec(&over); in lkdtm_REFCOUNT_INC_OVERFLOW()
33 refcount_inc(&over); in lkdtm_REFCOUNT_INC_OVERFLOW()
36 refcount_inc(&over); in lkdtm_REFCOUNT_INC_OVERFLOW()
37 refcount_inc(&over); in lkdtm_REFCOUNT_INC_OVERFLOW()
39 overflow_check(&over); in lkdtm_REFCOUNT_INC_OVERFLOW()
45 refcount_t over = REFCOUNT_INIT(REFCOUNT_MAX - 1); in lkdtm_REFCOUNT_ADD_OVERFLOW() local
48 refcount_dec(&over); in lkdtm_REFCOUNT_ADD_OVERFLOW()
49 refcount_dec(&over); in lkdtm_REFCOUNT_ADD_OVERFLOW()
50 refcount_dec(&over); in lkdtm_REFCOUNT_ADD_OVERFLOW()
[all …]
|
| /kernel/linux/linux-5.10/drivers/hwtracing/stm/ |
| D | Kconfig | 19 This is a simple framing protocol for sending data over STM
35 over the STP transport. In addition to the data payload, it
53 tristate "Kernel console over STM devices"
56 messages to trace hosts over STM devices.
58 If you want to send kernel console messages over STM devices,
62 tristate "Heartbeat over STM devices"
65 heartbeat messages to trace hosts over STM devices. It is
69 If you want to send heartbeat messages over STM devices,
80 If you want to send kernel Ftrace messages over STM devices,
|
| /kernel/linux/linux-5.10/drivers/nvme/host/ |
| D | Kconfig | 39 tristate "NVM Express over Fabrics RDMA host driver"
45 This provides support for the NVMe over Fabrics protocol using
49 To configure a NVMe over Fabrics controller use the nvme-cli tool
55 tristate "NVM Express over Fabrics FC host driver"
62 This provides support for the NVMe over Fabrics protocol using
66 To configure a NVMe over Fabrics controller use the nvme-cli tool
72 tristate "NVM Express over Fabrics TCP host driver"
80 This provides support for the NVMe over Fabrics protocol using
84 To configure a NVMe over Fabrics controller use the nvme-cli tool
|
| /kernel/linux/linux-4.19/net/core/ |
| D | ptp_classifier.c | 22 * ; PTP over UDP over IPv4 over Ethernet
38 * ; PTP over UDP over IPv6 over Ethernet
51 * ; PTP over 802.1Q over Ethernet
64 * ; PTP over UDP over IPv4 over 802.1Q over Ethernet
80 * ; PTP over UDP over IPv6 over 802.1Q over Ethernet
93 * ; PTP over Ethernet
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/hwmon/ |
| D | ads1015.txt | 8 0: Voltage over AIN0 and AIN1.
9 1: Voltage over AIN0 and AIN3.
10 2: Voltage over AIN1 and AIN3.
11 3: Voltage over AIN2 and AIN3.
12 4: Voltage over AIN0 and GND.
13 5: Voltage over AIN1 and GND.
14 6: Voltage over AIN2 and GND.
15 7: Voltage over AIN3 and GND.
|
| /kernel/linux/linux-5.10/drivers/nvme/target/ |
| D | Kconfig | 25 NVMe Over Fabrics protocol. It allows for hosts to manage and
44 tristate "NVMe over Fabrics RDMA target support"
50 devices over RDMA.
55 tristate "NVMe over Fabrics FC target driver"
61 devices over FC.
66 tristate "NVMe over Fabrics FC Transport Loopback Test driver"
80 tristate "NVMe over Fabrics TCP target support"
85 devices over TCP.
|
| /kernel/linux/linux-5.10/net/core/ |
| D | ptp_classifier.c | 14 * ; PTP over UDP over IPv4 over Ethernet
30 * ; PTP over UDP over IPv6 over Ethernet
43 * ; PTP over 802.1Q over Ethernet
56 * ; PTP over UDP over IPv4 over 802.1Q over Ethernet
72 * ; PTP over UDP over IPv6 over 802.1Q over Ethernet
85 * ; PTP over Ethernet
|
| /kernel/linux/linux-4.19/drivers/hwtracing/stm/ |
| D | Kconfig | 23 tristate "Kernel console over STM devices"
26 messages to trace hosts over STM devices.
28 If you want to send kernel console messages over STM devices,
32 tristate "Heartbeat over STM devices"
35 heartbeat messages to trace hosts over STM devices. It is
39 If you want to send heartbeat messages over STM devices,
50 If you want to send kernel Ftrace messages over STM devices,
|
| /kernel/linux/linux-4.19/Documentation/hwmon/ |
| D | ads1015 | 27 in0: Voltage over AIN0 and AIN1.
28 in1: Voltage over AIN0 and AIN3.
29 in2: Voltage over AIN1 and AIN3.
30 in3: Voltage over AIN2 and AIN3.
31 in4: Voltage over AIN0 and GND.
32 in5: Voltage over AIN1 and GND.
33 in6: Voltage over AIN2 and GND.
34 in7: Voltage over AIN3 and GND.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/adc/ |
| D | ti,ads1015.yaml | 49 0: Voltage over AIN0 and AIN1.
50 1: Voltage over AIN0 and AIN3.
51 2: Voltage over AIN1 and AIN3.
52 3: Voltage over AIN2 and AIN3.
53 4: Voltage over AIN0 and GND.
54 5: Voltage over AIN1 and GND.
55 6: Voltage over AIN2 and GND.
56 7: Voltage over AIN3 and GND.
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/power/supply/ |
| D | max17042_battery.txt | 16 - maxim,over-heat-temp : Temperature threshold to report battery
17 as over heated (in tenths of degree Celsius).
20 - maxim,over-volt : Voltage threshold to report battery
21 as over voltage (in mV).
29 maxim,over-heat-temp = <600>;
30 maxim,over-volt = <4300>;
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/supply/ |
| D | max17042_battery.txt | 20 - maxim,over-heat-temp : Temperature threshold to report battery
21 as over heated (in tenths of degree Celsius).
24 - maxim,over-volt : Voltage threshold to report battery
25 as over voltage (in mV).
33 maxim,over-heat-temp = <600>;
34 maxim,over-volt = <4300>;
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/ |
| D | hid-over-i2c.txt | 1 * HID over I2C Device-Tree bindings
3 HID over I2C provides support for various Human Interface Devices over the
14 - compatible: must be "hid-over-i2c"
24 "hid-over-i2c" string.
39 compatible = "hid-over-i2c";
|
| /kernel/linux/linux-5.10/drivers/infiniband/ulp/ipoib/ |
| D | Kconfig | 3 tristate "IP-over-InfiniBand"
6 Support for the IP-over-InfiniBand protocol (IPoIB). This
7 transports IP packets over InfiniBand so you can use your IB
13 bool "IP-over-InfiniBand Connected Mode support"
28 bool "IP-over-InfiniBand debugging" if EXPERT
43 bool "IP-over-InfiniBand data path debugging"
|
| /kernel/linux/linux-4.19/drivers/nvme/host/ |
| D | Kconfig | 29 tristate "NVM Express over Fabrics RDMA host driver"
35 This provides support for the NVMe over Fabrics protocol using
39 To configure a NVMe over Fabrics controller use the nvme-cli tool
45 tristate "NVM Express over Fabrics FC host driver"
52 This provides support for the NVMe over Fabrics protocol using
56 To configure a NVMe over Fabrics controller use the nvme-cli tool
|
| /kernel/linux/linux-4.19/drivers/infiniband/ulp/ipoib/ |
| D | Kconfig | 2 tristate "IP-over-InfiniBand"
5 Support for the IP-over-InfiniBand protocol (IPoIB). This
6 transports IP packets over InfiniBand so you can use your IB
12 bool "IP-over-InfiniBand Connected Mode support"
27 bool "IP-over-InfiniBand debugging" if EXPERT
42 bool "IP-over-InfiniBand data path debugging"
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/input/ |
| D | hid-over-i2c.txt | 1 * HID over I2C Device-Tree bindings
3 HID over I2C provides support for various Human Interface Devices over the
14 - compatible: must be "hid-over-i2c"
24 "hid-over-i2c" string.
39 compatible = "hid-over-i2c";
|
| /kernel/linux/linux-5.10/net/hsr/ |
| D | Kconfig | 18 with other HSR capable nodes. All Ethernet frames sent over the HSR
19 device will be sent in both directions on the ring (over both slave
20 ports), giving a redundant, instant fail-over network. Each HSR node
25 separate networks over the two slave interfaces. Like HSR, Ethernet
26 frames sent over the PRP device will be sent to both networks giving
27 a redundant, instant fail-over network. Unlike HSR, PRP networks
|