| /openbmc/linux/drivers/nfc/nfcmrvl/ |
| H A 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 …]
|
| /openbmc/linux/drivers/usb/gadget/function/ |
| H A D | u_ether.h | 96 /* gether_setup - initialize one ethernet-over-usb link
125 * Registers the net device associated with this ethernet-over-usb link
130 /* gether_setup_default - initialize one ethernet-over-usb link
145 * gether_set_gadget - initialize one ethernet-over-usb link with a gadget
149 * This associates one ethernet-over-usb link with a gadget.
154 * gether_set_dev_addr - initialize an ethernet-over-usb link with eth address
158 * This sets the device-side Ethernet address of this ethernet-over-usb link
165 * gether_get_dev_addr - get an ethernet-over-usb link eth address
170 * This gets the device-side Ethernet address of this ethernet-over-usb link.
176 * gether_set_host_addr - initialize an ethernet-over-usb link with host address
[all …]
|
| /openbmc/linux/drivers/net/ppp/ |
| H A 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 …]
|
| /openbmc/linux/drivers/nvme/target/ |
| H A D | Kconfig | 25 NVMe Over Fabrics protocol. It allows for hosts to manage and
43 tristate "NVMe over Fabrics RDMA target support"
49 devices over RDMA.
54 tristate "NVMe over Fabrics FC target driver"
60 devices over FC.
65 tristate "NVMe over Fabrics FC Transport Loopback Test driver"
78 tristate "NVMe over Fabrics TCP target support"
83 devices over TCP.
88 bool "NVMe over Fabrics In-band Authentication support"
98 This enables support for NVMe over Fabrics In-band Authentication
|
| /openbmc/linux/drivers/nvme/host/ |
| H A D | Kconfig | 48 tristate "NVM Express over Fabrics RDMA host driver"
53 This provides support for the NVMe over Fabrics protocol using
57 To configure a NVMe over Fabrics controller use the nvme-cli tool
63 tristate "NVM Express over Fabrics FC host driver"
69 This provides support for the NVMe over Fabrics protocol using
73 To configure a NVMe over Fabrics controller use the nvme-cli tool
79 tristate "NVM Express over Fabrics TCP host driver"
86 This provides support for the NVMe over Fabrics protocol using
90 To configure a NVMe over Fabrics controller use the nvme-cli tool
96 bool "NVM Express over Fabrics In-Band Authentication"
[all …]
|
| /openbmc/linux/drivers/hwtracing/stm/ |
| H A D | Kconfig | 18 This is a simple framing protocol for sending data over STM
34 over the STP transport. In addition to the data payload, it
52 tristate "Kernel console over STM devices"
55 messages to trace hosts over STM devices.
57 If you want to send kernel console messages over STM devices,
61 tristate "Heartbeat over STM devices"
64 heartbeat messages to trace hosts over STM devices. It is
68 If you want to send heartbeat messages over STM devices,
79 If you want to send kernel Ftrace messages over STM devices,
|
| /openbmc/linux/drivers/misc/lkdtm/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/ABI/stable/ |
| H A D | sysfs-driver-firmware-zynqmp | 125 the features at runtime. The supported features are over
134 disable the over temperature feature.
136 over temperature limit in Degree Celsius.
144 Select over temperature config ID to enable/disable feature
147 Check over temperature config ID is selected or not
151 Select over temperature config ID to configure OT limit
154 Check over temperature config ID is selected or not
182 at runtime. The supported features are over temperature and
193 The default limit for the over temperature is 90 Degree Celsius.
198 disable the over temperature feature.
[all …]
|
| /openbmc/linux/net/core/ |
| H A 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
|
| /openbmc/linux/Documentation/devicetree/bindings/power/supply/ |
| H A D | maxim,max17042.yaml | 44 maxim,over-heat-temp:
47 Temperature threshold to report battery as over heated (in tenths of degree Celsius).
48 Default is not to report over heating events.
56 maxim,over-volt:
59 Voltage threshold to report battery as over voltage (in mV).
60 Default is not to report over-voltage events.
80 maxim,over-heat-temp = <600>;
81 maxim,over-volt = <4300>;
|
| /openbmc/linux/Documentation/devicetree/bindings/input/ |
| H A D | hid-over-i2c.yaml | 4 $id: http://devicetree.org/schemas/input/hid-over-i2c.yaml#
7 title: HID over I2C Devices
14 HID over I2C provides support for various Human Interface Devices over the
33 - const: hid-over-i2c
34 - description: Just "hid-over-i2c" alone is allowed, but not recommended.
35 const: hid-over-i2c
79 compatible = "hid-over-i2c";
|
| /openbmc/linux/Documentation/devicetree/bindings/iio/adc/ |
| H A D | ti,ads1015.yaml | 53 0: Voltage over AIN0 and AIN1.
54 1: Voltage over AIN0 and AIN3.
55 2: Voltage over AIN1 and AIN3.
56 3: Voltage over AIN2 and AIN3.
57 4: Voltage over AIN0 and GND.
58 5: Voltage over AIN1 and GND.
59 6: Voltage over AIN2 and GND.
60 7: Voltage over AIN3 and GND.
|
| /openbmc/phosphor-misc/http-redirect/ |
| H A D | tests | 13 echo "/over/the/rainbow /over/the/rainbow" > $URLFILE
25 expect='^location: https://somewhere.example.com/over/the/rainbow.$'
27 GET http://somewhere.example.com/over/the/rainbow HTTP/1.1
62 expect='^location: https://elsewhere.example/over/the/rainbow.$'
64 GET /over/the/rainbow HTTP/1.1
82 expect='^location: https://somewhere.com/over/the/rainbow.$'
84 GET /over/the/rainbow HTTP/1.1
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | crps.rst | 60 in1_crit Critical input over voltage
61 in1_crit_alarm Critical input over voltage alarm
62 in1_max Maximum input over voltage
63 in1_max_alarm Maximum input over voltage alarm
69 in2_crit Critical input over voltage
70 in2_crit_alarm Critical input over voltage alarm
73 in2_max Maximum input over voltage
74 in2_max_alarm Maximum input over voltage alarm
|
| /openbmc/linux/drivers/infiniband/ulp/ipoib/ |
| H A 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"
|
| /openbmc/linux/net/hsr/ |
| H A 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
|
| /openbmc/openbmc-test-automation/gui/test/server_overview/ |
| H A D | test_obmc_gui_server_overview.robot | 20 ${string_launch_serial_over_lan} Serial over LAN console
25 Verify Serial Over LAN Button
26 [Documentation] Verify console page on clicking serial over lan console button
31 Verify Display Content Access the Serial over LAN console
84 Verify Launching Of Serial Over LAN Console At OBMC Power Off State
85 [Documentation] Will open the serial over the lan command prompt window.
131 Verify Launching Of Serial Over LAN Console At OBMC Power Running State
132 [Documentation] Will open the serial over the lan command prompt window.
|
| /openbmc/linux/include/linux/ |
| H A D | hashtable.h | 120 * hash_for_each - iterate over a hashtable
132 * hash_for_each_rcu - iterate over a rcu enabled hashtable
144 * hash_for_each_safe - iterate over a hashtable safe against removal of
158 * hash_for_each_possible - iterate over all possible objects hashing to the
163 * @key: the key of the objects to iterate over
169 * hash_for_each_possible_rcu - iterate over all possible objects hashing to the
174 * @key: the key of the objects to iterate over
181 * hash_for_each_possible_rcu_notrace - iterate over all possible objects hashing
186 * @key: the key of the objects to iterate over
196 * hash_for_each_possible_safe - iterate over all possible objects hashing to the
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/regulator/ |
| H A D | regulator.yaml | 117 regulator-over-current-protection:
118 description: Enable over current protection.
122 description: Set over current protection limit. This is a limit where
128 description: Set over current error limit. This is a limit where part of
134 description: Set over current warning limit. This is a limit where hardware
141 description: Set over voltage protection limit. This is a limit where
148 description: Set over voltage error limit. This is a limit where part of
155 description: Set over voltage warning limit. This is a limit where hardware
163 description: Set over under voltage protection limit. This is a limit where
177 description: Set over under voltage warning limit. This is a limit where
[all …]
|
| /openbmc/linux/drivers/fpga/ |
| H A D | Kconfig | 41 tristate "Altera FPGA Passive Serial over SPI"
46 using the passive serial interface over SPI.
53 Arria 10 and Stratix10 Altera FPGAs using the CvP interface over PCIe.
68 tristate "Xilinx Configuration over Slave Serial (SPI)"
72 over slave serial interface.
78 FPGA manager driver support for Lattice iCE40 FPGAs over SPI.
85 over slave SPI interface.
265 programming over slave SPI interface with .dat formatted
276 FPGA manager driver support for Lattice FPGAs programming over slave
|
| /openbmc/linux/include/linux/regulator/ |
| H A D | machine.h | 111 * @over_curr_limits: Limits for acting on over current.
112 * @over_voltage_limits: Limits for acting on over voltage.
114 * @temp_limits: Limits for acting on over temperature.
130 * @over_current_protection: Auto disable on over current event.
132 * @over_current_detection: Configure over current limits.
133 * @over_voltage_detection: Configure over voltage limits.
135 * @over_temp_detection: Configure over temperature limits.
217 unsigned over_current_protection:1; /* auto disable on over current */
218 unsigned over_current_detection:1; /* notify on over current */
219 unsigned over_voltage_detection:1; /* notify on over voltage */
[all …]
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | PDDL-1.0 | 20 Rightsholders can also use this document to cover any copyright or database rights claims over only…
28 The Rightsholder (the Person holding rights or claims over the Work) agrees as follows:
38 "Database Right" - Means rights over Data resulting from the Chapter III ("sui generis") rights in …
56 …a. A dedication to the public domain and waiver of Copyright and Database Rights over the Work; and
58 …b. A licence of Copyright and Database Rights over the Work in jurisdictions that do not allow for…
64 …rt of the Data. Database Rights can apply even when there is no copyright over the Database. Datab…
70 …b. This Document does not cover any patents over the Data or the Database. Please see Section 4.2 …
82 …e benefit of the public and relinquishes all rights in Copyright and Database Rights over the Work.
84 …t the Rightsholder has no further rights in Copyright and Database Rights over the Work, and that …
90 …ves any rights and claims that the Rightsholder may have or acquire in the future over the Work in:
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/hwmon/ |
| H A D | max6697.txt | 34 - over-temperature-mask
35 Over-temperature bit mask. Over-temperature reporting disabled for
38 If not specified, over-temperature reporting will be enabled for all
63 over-temperature-mask = <0x7f>;
|
| /openbmc/linux/drivers/net/slip/ |
| H A D | Kconfig | 14 Internet Protocol) is a protocol used to send Internet traffic over
23 allows you to use SLIP over a regular dial up shell connection. If
56 allows you to use SLIP over a regular dial up shell connection, you
73 Just occasionally you may need to run IP over hostile serial
76 "slip6". In this mode, SLIP will only send normal ASCII symbols over
79 over the async ports of a Camtec JNT Pad. If unsure, say N.
|
| /openbmc/docs/designs/mctp/ |
| H A D | mctp-userspace.md | 19 over a configurable hardware channel (eg., Serial UART, I2C or PCIe), and
30 2. one or more binding implementations (eg, MCTP-over-serial), which interact
33 3. an interface to handler applications over a unix-domain socket.
67 over the MCTP channel, and connect to the central daemon over a UNIX domain
101 Subsequent messages sent over the socket are MCTP messages sent/received by the
127 possible functionality that is available over MCTP, which may be quite a
135 messages over dbus instead. The reason for the choice of sockets rather than
|