Searched full:expected (Results 1 – 25 of 446) sorted by relevance
12345678910>>...18
| /Documentation/ABI/testing/ |
| D | sysfs-class-rc | 48 Sets the scancode filter expected value.
51 expected value of the bits set in the filter mask.
65 of the scancode which should be compared against the expected
106 Sets the scancode wakeup filter expected value.
109 set the expected value of the bits set in the wakeup filter mask
129 expected value to trigger a system wake event.
|
| D | sysfs-bus-siox | 7 expected to not do anything because their watchdog triggered.
63 expected value.
76 active. "0" means the watchdog is not active and the device is expected to
|
| D | sysfs-class-rtrs-client | 12 Description: RW, adds a new path (connection) to an existing session. Expected format is the
123 how many interrupts where generated on a non expected CPU.
126 is the CPU on which the IRQ was expected, but not generated.
128 is the CPU on which the IRQ was generated, but not expected.
|
| D | debugfs-olpc | 11 CC is the (hex) command, N is the count of expected reply bytes, and A A A A
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-firmware-zynqmp | 149 The expected result is 1.
156 The expected result is 2.
163 The expected result is 3.
170 The expected result is 4.
214 The expected result is 1.
222 The expected result is 0.
230 The expected result is 50.
238 The expected result is 1.
246 The expected result is 0.
254 The expected result is 500.
|
| /Documentation/userspace-api/media/rc/ |
| D | rc-sysfs-nodes.rst | 61 Sets the scancode filter expected value.
64 expected value of the bits set in the filter mask. If the hardware
78 should be compared against the expected value. A value of 0 disables the
119 Sets the scancode wakeup filter expected value. Use in combination with
120 ``/sys/class/rc/rcN/wakeup_filter_mask`` to set the expected value of
137 the scancode which should be compared against the expected value to
|
| /Documentation/networking/devlink/ |
| D | devlink-flash.rst | 41 are provided, it is expected that the device only update firmware binaries
42 in the components being updated. Settings and identifiers are expected to be
66 Drivers are expected to implement ``devlink-flash`` and ``devlink-info``
99 # Find out the expected overall firmware versions
116 is expected to fetch up-to-date information from the kernel.
|
| /Documentation/infiniband/ |
| D | tag_matching.rst | 24 this is an expected message, otherwise it is called an unexpected message.
48 maintained by the hardware, with the software expected to shadow this list.
64 Software is expected to shadow this list, to help with processing MPI cancel
65 operations. In addition, because hardware and software are not expected to be
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | adc-battery.yaml | 17 The voltage is expected to be measured between the battery terminals
18 and mandatory. The optional current/power channel is expected to
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | gpio-poweroff.yaml | 14 executed the operating system is expected to switch the GPIO
16 is expected to be switched back to inactive. After another
|
| /Documentation/devicetree/bindings/regulator/ |
| D | vctrl.txt | 21 margin from the expected value for a given control
29 down in the worst case (lightest expected load).
|
| /Documentation/devicetree/bindings/serial/ |
| D | nvidia,tegra20-hsuart.yaml | 70 Standard UART devices are expected to have tolerance for baud rate error by -4 to +4 %. All
81 to 9600 has 1% deviation 9600 to 115200 2% deviation. This slight deviation is expected and
82 Tegra UART is expected to handle it. Due to the issue stated above, baud rate on Tegra UART
|
| /Documentation/networking/ |
| D | tls-offload.rst | 116 the expected sequence number and will have kernel record information.
135 * expected TCP sequence number
159 Both the device and the driver maintain expected TCP sequence numbers
179 number is the expected one and proceeds to TLS handling (record delineation,
226 (next expected segment is the one after the out of order one), or continue
237 sequence number is lower than expected the driver assumes retransmission
248 Until resync is complete driver should not access its expected TCP
285 of expected window of the device so it's passed as is without special
308 numbers more than a max size record past the expected TCP sequence number,
312 the device continues attempting parsing headers at expected locations
[all …]
|
| D | xfrm_proc.rst | 77 …State direction mismatch (lookup found an output state on the input path, expected input or no dir…
119 …State direction mismatch (lookup found an input state on the output path, expected output or no di…
|
| /Documentation/arch/arm/ |
| D | interrupts.rst | 58 * If this is a level-based IRQ, then it is expected to mask the IRQ
89 IRQs that use this 'irqchip'. Generally expected to re-trigger
123 2. New functions to manipulate the irqdesc array. The first 4 are expected
151 5. A handler is expected to perform any necessary acknowledgement of the
|
| /Documentation/admin-guide/ |
| D | abi-obsolete.rst | 8 obsolete and when it can be expected to be removed.
|
| D | abi-stable.rst | 10 Most interfaces (like syscalls) are expected to never change and always
|
| /Documentation/livepatch/ |
| D | reliable-stacktrace.rst | 57 expected by the unwinder. For example, an unwinder may expect that
85 services) not following the conventions expected by the unwinder.
89 architectures verify that a stacktrace ends at an expected location, e.g.
93 * At a specific location on a stack expected for a kernel entry point.
95 * On a specific stack expected for a kernel entry point (e.g. if the
135 At function call boundaries the stack and other unwind state is expected to be
|
| /Documentation/arch/sh/ |
| D | booting.rst | 6 Device-tree compatible SH bootloaders are expected to provide the physical
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | zii,rave-sp-backlight.txt | 4 backlight functionality of RAVE Supervisory Processor. It is expected
|
| /Documentation/devicetree/bindings/input/ |
| D | zii,rave-sp-pwrbutton.txt | 4 button functionality of RAVE Supervisory Processor. It is expected
|
| /Documentation/core-api/ |
| D | floating-point.rst | 41 Architectures are expected to define one or both of these variables in their
62 platform. The value returned by this function is not expected to change
|
| /Documentation/driver-api/ |
| D | wbrf.rst | 58 The expected flow for the producers:
66 The expected flow for the consumers:
|
| /Documentation/devicetree/bindings/phy/ |
| D | phy-miphy365x.txt | 33 - st,sata-gen : Generation of locally attached SATA IP. Expected values
35 be expected
|
| /Documentation/driver-api/80211/ |
| D | introduction.rst | 15 The reader is expected to be familiar with the 802.11 standard as
|
12345678910>>...18