Searched full:significant (Results 1 – 25 of 218) sorted by relevance
123456789
| /Documentation/devicetree/bindings/dma/ |
| D | atmel-dma.txt | 25 2. The memory interface (16 most significant bits), the peripheral interface
26 (16 less significant bits).
|
| /Documentation/arch/sparc/oradax/ |
| D | dax-hv-api.txt | 258 … 1); bits are read most significant bit to least significant bit
265 … length encoding 1); bits are read most significant bit to least significant bit
269 … Huffman (CCB version 0) or bits are read most significant bit to least significant bit
273 … Huffman (CCB version 0) or 1); compressed stream bits are read most significant bit to
274 … OZIP (CCB version 1) encoding least significant bit within a byte; pointer to the encoding
277 … Huffman (CCB version 0) or bits are read most significant bit to least significant bit
289 … run length encoding, followed by bits are read most significant bit to least significant bit
295 … Huffman (CCB version 0) or significant bit to least significant bit within a byte; data
310 …s encoded in a fixed width, bit-packed format. The bits are read from most significant bit to least
311 …significant bit within a byte. There are two encoding options for the secondary input stream data …
[all …]
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-set-transmitter-mask.rst | 29 Mask with channels to enable tx. Channel 0 is the least significant bit.
40 encoded by the least significant bit and so on.
|
| /Documentation/devicetree/bindings/mux/ |
| D | gpio-mux.yaml | 17 multiplexer GPIO pins, where the first pin is the least significant
26 List of gpios used to control the multiplexer, least significant bit first.
|
| /Documentation/driver-api/mmc/ |
| D | mmc-async-req.rst | 8 How significant is the cache maintenance overhead?
11 pre-fetch makes the cache overhead relatively significant. If the DMA
31 more significant the prepare request time becomes. Roughly the expected
|
| /Documentation/devicetree/bindings/mips/cavium/ |
| D | ciu3.txt | 21 * 1) Source number (20 significant bits)
|
| /Documentation/devicetree/bindings/net/can/ |
| D | grcan.txt | 23 - systemid : If not present or if the value of the least significant 16 bits
|
| /Documentation/virt/kvm/devices/ |
| D | xics.rst | 43 least-significant end of the word:
64 bitfields, starting from the least-significant end of the word:
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-yuv-luma.rst | 14 - In all the tables that follow, bit 7 is the most significant bit in a byte.
207 leaves the 6 most significant bits of the last byte padded with 0.
211 its padding located in the most significant bits of the 16 bit word.
|
| D | pixfmt-srggb8-pisp-comp.rst | 32 12 significant bits. Mode 2 is a simple sqrt-like companding scheme with 6 PWL
33 chords, preserving up to 12 significant bits. Mode 3 combines both companding
34 (with 4 chords) and the delta scheme, preserving up to 14 significant bits.
|
| D | dev-rds.rst | 101 - Least Significant Byte of RDS Block
104 - Most Significant Byte of RDS Block
|
| /Documentation/dev-tools/ |
| D | index.rst | 7 together without any significant effort to integrate them into a coherent
|
| /Documentation/devicetree/bindings/net/bluetooth/ |
| D | bluetooth-controller.yaml | 23 device. Formatted with least significant byte first (little-endian), e.g.
|
| /Documentation/devicetree/bindings/pci/ |
| D | cdns-pcie-host.yaml | 28 significant bits kept during inbound (PCIe -> AXI) address translations
|
| /Documentation/staging/ |
| D | crc32.rst | 23 CRC is written in hex with the most significant bit omitted. (If you're
30 little-endian; the most significant bit (sometimes used for parity)
82 The most significant coefficient of the remainder polynomial is stored
83 in the least significant bit of the binary "remainder" variable.
|
| /Documentation/devicetree/bindings/timer/ |
| D | brcm,bcm2835-system-timer.yaml | 16 register, which is compared against the 32 least significant bits of the
|
| /Documentation/devicetree/bindings/rtc/ |
| D | maxim-ds1302.txt | 24 - spi-lsb-first : DS-1302 requires least significant bit first
|
| /Documentation/usb/ |
| D | gadget_uvc.rst | 31 This allows a significant degree of flexibility, as many of a UVC device's
249 be multiple-input, though note that this currently has no significant effect.
317 # root. The name of the link is significant here, as it declares this
319 # Other significant link names at function root are vs0_desc and vs1_desc
327 # associates the two, the name of this link is not significant and may
|
| /Documentation/devicetree/bindings/spi/ |
| D | icpdas-lp8841-spi-rtc.txt | 34 - spi-lsb-first: DS-1302 requires least significant bit first
|
| /Documentation/mm/ |
| D | remap_file_pages.rst | 12 Supporting of nonlinear mapping requires significant amount of non-trivial
|
| /Documentation/networking/ |
| D | mctp.rst | 107 ``MCTP_TAG_OWNER`` is set, the 3 least-significant bits of ``smctp_tag`` are not
120 most-significant IC bit is not part of the match). This results in the socket
159 buffer, and the most-significant bit of the message type byte must be 1.
251 - ... and the actual tag value, within the least-significant three bits
|
| /Documentation/virt/kvm/x86/ |
| D | msr.rst | 316 The first, least significant bit of 4 byte memory location will be
328 significant bit while in the current VCPU context, this means that
334 guest and clear the least significant bit in the memory area
338 guest must both read the least significant bit in the memory area and
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-typec | 28 mode index may be significant.
|
| /Documentation/trace/ |
| D | events-kmem.rst | 65 is triggered. Significant amounts of activity here could indicate that the
70 freed in batch with a page list. Significant amounts of activity here could
|
| /Documentation/admin-guide/ |
| D | vga-softcursor.rst | 39 color codes used by the console) and the most significant one turns
|
123456789