Searched full:has (Results 1 – 25 of 2330) sorted by relevance
12345678910>>...94
| /Documentation/ABI/obsolete/ |
| D | sysfs-driver-hid-roccat-ryos | 5 profile will be read next. The data has to be 3 bytes long.
17 The data has to be 3 bytes long.
26 The data has to be 125 bytes long.
27 Before reading this file, control has to be written to select
36 in written data. The data has to be 95 bytes long.
37 Before reading this file, control has to be written to select
46 written data. The data has to be 35 bytes long.
47 Before reading this file, control has to be written to select
56 in written data. The data has to be 23 bytes long.
57 Before reading this file, control has to be written to select
[all …]
|
| D | sysfs-driver-hid-roccat-isku | 26 written data. The data has to be 6 bytes long.
27 Before reading this file, control has to be written to select
36 in written data. The data has to be 6 bytes long.
37 Before reading this file, control has to be written to select
46 in written data. The data has to be 65 bytes long.
47 Before reading this file, control has to be written to select
56 in written data. The data has to be 41 bytes long.
57 Before reading this file, control has to be written to select
66 written data. The data has to be 35 bytes long.
67 Before reading this file, control has to be written to select
[all …]
|
| D | sysfs-driver-hid-roccat-savu | 8 respective profile buttons to the mouse. The data has to be
13 Before reading this file, control has to be written to select
21 profile will be read next. The data has to be 3 bytes long.
33 settings back to the mouse. The data has to be 43 bytes long.
54 The data has to be 2083 bytes long.
55 Before reading this file, control has to be written to select
67 The data has to be 3 bytes long.
74 Description: The mouse has a Avago ADNS-3090 sensor.
76 The data has to be 4 bytes long.
|
| D | sysfs-driver-hid-roccat-konepure | 9 The data has to be 3 bytes long.
17 profile will be read next. The data has to be 3 bytes long.
36 included in written data. The data has to be 2082 bytes long.
47 buttons back to the mouse. The data has to be 59 bytes long.
51 Before reading this file, control has to be written to select
63 settings back to the mouse. The data has to be 31 bytes long.
67 Before reading this file, control has to be written to select
74 Description: The mouse has a tracking- and a distance-control-unit. These
76 set. The data has to be 6 bytes long.
84 The data has to be 16 bytes long.
[all …]
|
| /Documentation/devicetree/bindings/crypto/ |
| D | fsl-sec2.txt | 21 bit 1 = set if SEC has the ARC4 EU (AFEU)
22 bit 2 = set if SEC has the DES/3DES EU (DEU)
23 bit 3 = set if SEC has the message digest EU (MDEU/MDEU-A)
24 bit 4 = set if SEC has the random number generator EU (RNG)
25 bit 5 = set if SEC has the public key EU (PKEU)
26 bit 6 = set if SEC has the AES EU (AESU)
27 bit 7 = set if SEC has the Kasumi EU (KEU)
28 bit 8 = set if SEC has the CRC EU (CRCU)
29 bit 11 = set if SEC has the message digest EU extended alg set (MDEU-B)
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-led-flash | 27 is stopped after this period of time has passed from the start
60 has exceeded the limit specific to the flash controller
63 the timeout set by the user has expired; not all flash
66 the flash controller has
70 of the flash controller has been triggered
73 supply has exceeded the limit specific to the flash
76 the flash controller has detected
80 LED has been below the minimum limit specific to
88 the temperature of the LED has exceeded
|
| D | sysfs-bus-fsi-devices-sbefifo | 5 Indicates whether or not this SBE device has experienced a
7 by the driver. A value of 1 indicates that a timeout has
9 value of 0 indicates that no timeout has occurred, or if one
10 has, more recent transfers have completed successfully.
|
| D | sysfs-class-led-trigger-oneshot | 6 Specifies for how many milliseconds the LED has to stay at
7 LED_FULL brightness after it has been armed.
15 Specifies for how many milliseconds the LED has to stay at
16 LED_OFF brightness after it has been armed.
|
| D | sysfs-devices-platform-docg3 | 7 keylocked. Each docg3 chip (or floor) has 2 protection areas,
9 The protection has information embedded whether it blocks reads,
24 (0 or 1). Each docg3 chip (or floor) has 2 protection areas,
26 The protection has information embedded whether it blocks reads,
|
| D | sysfs-devices-state_synced | 10 means the .sync_state() callback has been called.
12 Generally, if a device has sync_state() support and has some of
18 this only when the sync_state() callback has been called --
|
| D | sysfs-bus-surface_aggregator-tabletsw | 10 - "disconnected": The type-cover has been disconnected.
12 - "closed": The type-cover has been folded closed and lies on
18 - "folded-canvas": The type-cover has been folded back
23 - "folded-back": The type cover has been fully folded back and
46 - "slate": The screen covers the keyboard or has been flipped
|
| D | sysfs-class-wakeup | 40 timeout has expired.
46 This file contains the amount of time the wakeup source has
55 has been active, in milliseconds.
62 source has been continuously active, in milliseconds.
76 has been preventing autosleep, in milliseconds.
|
| /Documentation/devicetree/bindings/nios2/ |
| D | nios2.txt | 26 - altr,has-mul: Specifies CPU hardware multiply support, should be 1.
27 - altr,has-mmu: Specifies CPU support MMU support, should be 1.
28 - altr,has-initda: Specifies CPU support initda instruction, should be 1.
34 - altr,has-div: Specifies CPU hardware divide support
55 altr,has-div = <1>;
56 altr,has-mul = <1>;
60 altr,has-initda = <1>;
61 altr,has-mmu = <1>;
|
| /Documentation/devicetree/bindings/i2c/ |
| D | nvidia,tegra20-i2c.yaml | 16 - description: Tegra20 has 4 generic I2C controller. This can support
21 - description: Tegra20 has specific I2C controller called as DVC I2C
28 Tegra30 has 5 generic I2C controller. This controller is very much
39 Tegra114 has 5 generic I2C controllers. This controller is very much
41 - Tegra30/Tegra20 I2C controller has 2 clock source called div-clk
42 and fast-clk. Tegra114 has only one clock source called as
44 - Tegra30/Tegra20 I2C controller has enabled per packet transfer
45 by default and there is no way to disable it. Tegra114 has this
52 Tegra124 has 6 generic I2C controllers. These controllers are very
57 Tegra210 has 6 generic I2C controllers. These controllers are very
[all …]
|
| D | i2c-gpio.yaml | 59 description: this means that something outside of our control has put
66 description: this means that something outside of our control has put the
70 i2c-gpio,sda-has-no-pullup:
72 description: sda is used in a non-compliant way and has no pull-up.
76 i2c-gpio,scl-has-no-pullup:
78 description: scl is used in a non-compliant way and has no pull-up.
83 i2c-gpio,sda-has-no-pullup:
87 i2c-gpio,scl-has-no-pullup:
|
| /Documentation/driver-api/memory-devices/ |
| D | ti-gpmc.rst | 23 GPMC has certain timings that has to be programmed for proper
24 functioning of the peripheral, while peripheral has another set of
25 timings. To have peripheral work with gpmc, peripheral timings has to
26 be translated to the form gpmc can understand. The way it has to be
32 from gpmc peripheral timings. struct gpmc_device_timings fields has to
35 in time or in cycles, provision to handle this scenario has been
45 Generic timing routine has been verified to work properly on
48 A word of caution: generic timing routine has been developed based
|
| /Documentation/devicetree/bindings/phy/ |
| D | brcm,brcmstb-usb-phy.yaml | 87 brcm,has-xhci:
88 description: Indicates the PHY has an XHCI PHY.
91 brcm,has-eohci:
92 description: Indicates the PHY has an EHCI/OHCI PHY.
108 - brcm,has-xhci
110 - brcm,has-eohci
166 brcm,has-xhci;
167 brcm,has-eohci;
192 brcm,has-xhci;
|
| /Documentation/ABI/stable/ |
| D | sysfs-transport-srp | 13 layer error has been observed before removing a target port.
22 layer error has been observed before failing I/O. Zero means
53 "blocked" if a transport layer error has been encountered but
54 the fast_io_fail_tmo timer has not yet fired; "fail-fast"
55 after the fast_io_fail_tmo timer has fired and before the
56 "dev_loss_tmo" timer has fired; "lost" after the
57 "dev_loss_tmo" timer has fired and before the port is finally
|
| /Documentation/admin-guide/ |
| D | tainted-kernels.rst | 100 15 _/K 32768 kernel has been live patched
103 18 _/N 262144 an in-kernel test has been run
113 any proprietary module has been loaded. Modules without a
121 specification: hardware has been put into an unsupported configuration,
132 bootloader has booted CPUs in different modes.
147 4) ``M`` if any processor has reported a Machine Check Exception,
150 5) ``B`` If a page-release function has found a bad page reference or some
158 7) ``D`` if the kernel has died recently, i.e. there was an OOPS or BUG.
160 8) ``A`` if an ACPI table has been overridden.
162 9) ``W`` if a warning has previously been issued by the kernel.
[all …]
|
| /Documentation/networking/ |
| D | 6pack.rst | 23 6pack has two major advantages:
28 buffer underrun or overrun has occurred, if the PTT is
42 Damaged packets that the TNC has received from the PC are not transmitted.
47 2. Who has developed the 6pack protocol?
50 The 6pack protocol has been developed by Ekki Plicht DF4OR, Henning Rech
92 The driver has been tested with kernel version 2.1.90. Use with older
94 function has been changed in the 2.1.8x kernels.
108 has to be modified.
129 module has printed its initialization message.
139 Although the driver has been tested on various platforms, I still declare it
[all …]
|
| /Documentation/ |
| D | atomic_bitops.txt | 63 Except for a successful test_and_set_bit_lock() which has ACQUIRE semantics,
64 clear_bit_unlock() which has RELEASE semantics and test_bit_acquire which has
67 Since a platform only has a single means of achieving atomic operations
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-flash.rst | 118 period of time has passed from the start of the strobe.
152 - Flash controller voltage to the flash LED has exceeded the limit
156 V4L2_CID_FLASH_TIMEOUT control --- has expired. Not all flash
159 - The flash controller has overheated.
161 - The short circuit protection of the flash controller has been
164 - Current in the LED power supply has exceeded the limit specific to
167 - The flash controller has detected a short or open circuit
170 - Flash controller voltage to the flash LED has been below the
177 - The temperature of the LED has exceeded its allowed upper limit.
|
| D | func-poll.rst | 32 until the driver has captured data or is ready to accept data for
35 When streaming I/O has been negotiated this function waits until a
36 buffer has been filled by the capture device and can be dequeued with
54 field. When the application has called
66 When use of the :c:func:`read()` function has been negotiated and the
69 it waits until data has been captured and can be read. When the driver
73 When use of the :c:func:`write()` function has been negotiated and the
|
| /Documentation/scsi/ |
| D | FlashPoint.rst | 8 The upgrade program described below has been officially terminated effective
17 FREMONT, CA, -- October 8, 1996 -- Mylex Corporation has expanded Linux
85 Ever since its introduction last October, the BusLogic FlashPoint LT has
90 system like Linux, the FlashPoint LT has been touted by computer system
91 vendors as the latest thing, and has been sold even on many of their high
92 end systems, to the exclusion of the older MultiMaster products. This has
126 FlashPoint architecture at all, that debate has not yet been settled either
134 has put in place a direct upgrade program to allow any Linux user worldwide
137 and has all the best features of both the BT-946C and FlashPoint LT,
140 upgrade has been set at US $45 plus shipping and handling, and the upgrade
[all …]
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | ti,lm87.yaml | 27 has-temp3:
34 has-in6:
40 has-in7:
66 has-temp3;
|
12345678910>>...94