Searched full:expected (Results 1 – 25 of 331) sorted by relevance
12345678910>>...14
| /Documentation/ABI/testing/ |
| D | sysfs-class-rc | 41 Sets the scancode filter expected value.
43 expected value of the bits set in the filter mask.
56 of the scancode which should be compared against the expected
88 Sets the scancode wakeup filter expected value.
90 set the expected value of the bits set in the wakeup filter mask
106 expected value to trigger a system wake event.
|
| D | sysfs-bus-siox | 7 expected to not do anything because their watchdog triggered.
60 expected value.
73 active. "0" means the watchdog is not active and the device is expected to
|
| D | debugfs-olpc | 11 CC is the (hex) command, N is the count of expected reply bytes, and A A A A
|
| /Documentation/media/uapi/rc/ |
| D | rc-sysfs-nodes.rst | 68 Sets the scancode filter expected value.
71 expected value of the bits set in the filter mask. If the hardware
85 should be compared against the expected value. A value of 0 disables the
126 Sets the scancode wakeup filter expected value. Use in combination with
127 ``/sys/class/rc/rcN/wakeup_filter_mask`` to set the expected value of
144 the scancode which should be compared against the expected value to
|
| /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/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 …]
|
| /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/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/virt/kvm/devices/ |
| D | arm-vgic.txt | 56 confirm its expected behavior is aligned with the KVM implementation.
59 the expected behavior. Unless GICD_IIDR has been set from userspace, writes
114 -EINVAL: Value set is out of the expected range
|
| /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/driver-api/80211/ |
| D | introduction.rst | 15 The reader is expected to be familiar with the 802.11 standard as
|
| /Documentation/devicetree/bindings/serial/ |
| D | nvidia,tegra20-hsuart.txt | 37 Standard UART devices are expected to have tolerance for baud rate error by
52 This slight deviation is expcted and Tegra UART is expected to handle it. Due
|
| /Documentation/devicetree/bindings/phy/ |
| D | phy-miphy365x.txt | 33 - st,sata-gen : Generation of locally attached SATA IP. Expected values
35 be expected
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | aspeed_adc.txt | 9 - clocks: Input clock used to derive the sample clock. Expected to be the
|
| /Documentation/devicetree/bindings/net/wireless/ |
| D | esp,esp8089.txt | 4 The node is expected to be specified as a child node to the SDIO controller
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | microchip,ucs1002.txt | 14 Both are expected to be IRQ_TYPE_EDGE_BOTH
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio-mvebu.txt | 21 entry is expected, except for the "marvell,armadaxp-gpio" variant
22 for which two entries are expected: one for the general registers,
|
| /Documentation/ABI/ |
| D | README | 17 (like syscalls) are expected to never change and always be
38 why it is obsolete and when it can be expected to be removed.
|
| /Documentation/driver-api/nvdimm/ |
| D | security.rst | 46 key "passphrase" is expected to be 32bytes long. This is similar to the ATA
71 When doing an update, it is expected that the existing key is removed from
74 keyid when doing the update operation. It is also expected that the new key
|
| /Documentation/driver-api/pm/ |
| D | cpuidle.rst | 94 It may fail, in which case it is expected to return a negative error
109 It is expected to reverse any changes made by the ``->enable()``
157 expected to pass the number of the CPU to
176 The entries in the :c:member:`states` array are expected to be sorted by the
180 :c:member:`target_residency` value is expected to reflect the "depth" of the
279 a ``CPUIdle`` driver is expected to call :c:func:`cpuidle_pause_and_lock()` to
|
| /Documentation/devicetree/bindings/mtd/ |
| D | st-fsm.txt | 13 - st,boot-device-spi : Expected boot-device value if booted via this device
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | zii,rave-sp-wdt.txt | 4 watchdog functionality of RAVE Supervisory Processor. It is expected
|
| /Documentation/RCU/ |
| D | rculist_nulls.txt | 26 if (obj->key != key) { // not the object we expected
135 if (obj->key != key) { // not the object we expected
143 * not the expected one, we must restart lookup.
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | zii,rave-sp-eeprom.txt | 4 attached to RAVE Supervisory Processor. It is expected that its Device
|
12345678910>>...14