Searched full:scheme (Results 1 – 25 of 124) sorted by relevance
12345
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-light-isl29018 | 9 Scheme 0, makes full n (4, 8, 12, 16) bits (unsigned) proximity
10 detection. The range of Scheme 0 proximity count is from 0 to
11 2^n. Logic 1 of this bit, Scheme 1, makes n-1 (3, 7, 11, 15)
13 range of Scheme 1 proximity count is from -2^(n-1) to 2^(n-1).
15 Scheme 0 has wider dynamic range, Scheme 1 proximity detection
|
| D | sysfs-bus-usb | 212 - Bit 0 of this field selects the "old" enumeration scheme,
215 The old enumeration scheme can also be selected globally
217 it is often not desirable as the new scheme was introduced to
|
| /Documentation/devicetree/bindings/mtd/ |
| D | gpmc-nand.txt | 35 Refer below "How to select correct ECC scheme for your device ?"
105 How to select correct ECC scheme for your device ?
107 Higher ECC scheme usually means better protection against bit-flips and
108 increased system lifetime. However, selection of ECC scheme is dependent
120 Other factor which governs the selection of ecc-scheme is oob-size.
137 trying to use BCH16 (ECC_BYTES=26) ecc-scheme.
144 trying to use BCH16 (ECC_BYTES=26) ecc-scheme.
147 (OOBSIZE=128). So this device can use BCH16 ecc-scheme.
|
| D | gpmi-nand.txt | 39 ECC scheme.
|
| /Documentation/filesystems/ |
| D | mandatory-locking.txt | 42 "advisory" locking scheme. However, the world isn't perfect, and there's
46 with a "mandatory" locking scheme, whereby the operating system kernel would
51 The System V mandatory locking scheme was intended to have as little impact as
52 possible on existing user code. The scheme is based on marking individual files
62 Note 2: POSIX.1 does not specify any scheme for mandatory locking, despite
63 borrowing the fcntl() locking scheme from System V. The mandatory locking
64 scheme is defined by the System V Interface Definition (SVID) Version 3.
|
| D | directory-locking.rst | 6 Locking scheme used for directory operations is based on two
65 If no directory is its own ancestor, the scheme above is deadlock-free.
136 While this locking scheme works for arbitrary DAGs, it relies on
|
| /Documentation/devicetree/bindings/mfd/ |
| D | qcom,spmi-pmic.txt | 4 PMICs. These PMICs use a QPNP scheme through SPMI interface.
5 QPNP is effectively a partitioning scheme for dividing the SPMI extended
|
| /Documentation/scsi/ |
| D | aha152x.txt | 107 The BIOS uses a cylinder/head/sector addressing scheme (C/H/S)
108 scheme instead. DOS expects a BIOS or driver that understands this
116 geometry just to be able to support that addressing scheme. The geometry
126 Moreover there are certain limitations to the C/H/S addressing scheme,
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | qnap-poweroff.txt | 8 Synology NAS devices use a similar scheme, but a different baud rate,
|
| /Documentation/filesystems/ext4/ |
| D | ifork.rst | 36 Note that with this block mapping scheme, it is necessary to fill out a
38 led to the creation of the extent mapping scheme, discussed below.
40 Notice also that a file using this mapping scheme cannot be placed
47 tree. Under the old scheme, allocating a contiguous run of 1,000 blocks
|
| D | allocators.rst | 25 Under this scheme, when a file needs more blocks to absorb file writes,
51 this scheme evens out the loading on the block groups, though the author
|
| /Documentation/devicetree/bindings/arm/ti/ |
| D | k3.txt | 5 shall follow the following scheme:
|
| /Documentation/devicetree/bindings/firmware/ |
| D | nvidia,tegra186-bpmp.txt | 53 services. Put another way, the numbering scheme for I2C buses is distinct from
54 the numbering scheme for any other service the BPMP may provide (e.g. a future
|
| /Documentation/devicetree/bindings/sound/ |
| D | ti,tas5086.txt | 25 sequence, otherwise the default Low-Z scheme is used.
|
| /Documentation/admin-guide/perf/ |
| D | qcom_l2_pmu.rst | 26 which is outside the above scheme.
|
| /Documentation/media/dvb-drivers/ |
| D | udev.rst | 34 sysfs device name into the well known dvb adapter / device naming scheme.
|
| /Documentation/leds/ |
| D | leds-blinkm.rst | 21 The registration follows the scheme::
|
| /Documentation/pcmcia/ |
| D | locking.rst | 5 This file explains the locking and exclusion scheme used in the PCCARD
|
| /Documentation/networking/ |
| D | driver.txt | 70 mitigation scheme to let TX packets "hang out" in the TX
|
| /Documentation/devicetree/bindings/clock/ti/ |
| D | mux.txt | 24 "index-starts-at-one" modified the scheme as follows:
|
| /Documentation/trace/ |
| D | coresight.rst | 200 Device Naming scheme
216 devices are a bit cryptic and non-obvious. Thus, a new naming scheme was
233 Thus, with the new scheme the devices could appear as ::
239 Some of the examples below might refer to old naming scheme and some
240 to the newer scheme, to give a confirmation that what you see on your
400 As mentioned above in section "Device Naming scheme", the names of the devices could
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | brcm,bcm2835-armctrl-ic.txt | 4 72 interrupt sources using a 2-level register scheme. The interrupt
|
| /Documentation/iio/ |
| D | ep93xx_adc.rst | 15 Numbering scheme for channels 0..4 is defined in EP9301 and EP9302 datasheets.
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | ingenic,pinctrl.txt | 10 naming scheme "PxN" where x is a character identifying the GPIO port with
|
| /Documentation/devicetree/bindings/arm/ |
| D | qcom.yaml | 15 To support this scheme, we encode this information into the board compatible
|
12345