Searched full:segment (Results 1 – 25 of 105) sorted by relevance
12345
| /Documentation/devicetree/bindings/auxdisplay/ |
| D | gpio-7-segment.yaml | 4 $id: http://devicetree.org/schemas/auxdisplay/gpio-7-segment.yaml#
7 title: GPIO based LED segment display
14 const: gpio-7-segment
16 segment-gpios:
18 An array of GPIOs one per segment. The first GPIO corresponds to the A
19 segment, the seventh GPIO corresponds to the G segment. Some LED blocks
21 segment.
37 - segment-gpios
47 compatible = "gpio-7-segment";
48 segment-gpios = <&gpio 0 GPIO_ACTIVE_LOW>,
|
| D | maxim,max6959.yaml | 7 title: MAX6958/6959 7-segment LED display controller
13 The Maxim MAX6958/6959 7-segment LED display controller provides
14 an I2C interface to up to four 7-segment LED digits. The MAX6959,
|
| /Documentation/core-api/ |
| D | folio_queue.rst | 24 The folio_queue struct forms a single segment in a segmented list of folios
37 segments on either side of the segment being accessed. Whilst this is a
41 Each segment in the list also stores:
62 A segment should be initialised by calling::
66 with a pointer to the segment to be initialised. Note that this will not
74 Folios can be set in the next unused slot in a segment struct by calling one
123 Information may be retrieved about a particular segment with the following
132 The first function returns the maximum capacity of a segment. It must not be
135 segment has been filled to capacity.
138 segment. These are more about indicating how many slots in the array have been
[all …]
|
| D | this_cpu_ops.rst | 10 done through the use of segment registers (or a dedicated register where
67 On x86 the fs: or the gs: segment registers contain the base of the
68 per cpu area. It is then possible to simply use the segment override
71 instruction via a segment register prefix.
98 instead of the following operations required if there is no segment
141 Note that this operation is usually used in a code segment when
|
| /Documentation/networking/ |
| D | tls-offload.rst | 110 After TX state is installed, the stack guarantees that the first segment
124 so the initial records' TCP sequence number may be anywhere inside the segment.
141 to be possible device has to keep small amount of segment-to-segment state.
144 * partial headers (if a segment carried only a part of the TLS header)
147 authentication tag has to be written or read from the subsequent segment)
187 corresponding to the segment. Networking stack makes sure decrypted
215 Whenever an out of order segment is transmitted the driver provides
218 segment has to be passed to the device as part of the packet context,
226 (next expected segment is the one after the out of order one), or continue
227 with the previous stream state - assuming that the out of order segment
[all …]
|
| D | tcp_ao.rst | 10 of a TCP segment using a hashing function with a password known to both peers.
118 If the segment is a SYN, then this is the first segment of a new
119 connection. Find the matching MKT for this segment, using the segment's
123 i. If there is no matching MKT, remove TCP-AO from the segment.
124 Proceed with further TCP handling of the segment.
163 1. If the MKT corresponding to the segment’s socket pair and RNextKeyID
165 segment needs to match the MKT’s SendID).
175 by TCP-AO when processing received TCP segments as discussed in the segment
184 2. If the matching MKT corresponding to the segment’s socket pair and
194 Multiple MKTs may match a single outgoing segment, e.g., when MKTs
[all …]
|
| D | fib_trie.rst | 21 The number of bits in the key segment used for indexing into the
25 The position (in the key) of the key segment used for indexing into
30 a segment of the key specified by the parent's "pos" and "bits"
124 trie, key segment by key segment, until we find a leaf. check_leaf() does
|
| /Documentation/ABI/testing/ |
| D | sysfs-fs-nilfs2 | 97 Show start block number of the latest segment.
103 Show sequence value of the latest segment.
109 Show checkpoint number of the latest segment.
115 Show segment sequence counter.
121 Show index number of the latest full segment.
127 Show index number of the full segment index
134 Show offset of next partial segment in the current
135 full segment.
147 Show write time of the last segment in
154 Show write time of the last segment in seconds.
[all …]
|
| D | sysfs-class-chromeos-driver-cros-ec-lightbar | 30 This allows you to control each LED segment. If the
39 to select a single segment, or 4 to set all four segments
42 You can update more than one segment at a time by writing
|
| D | sysfs-driver-jz4780-efuse | 14 0x1E0 8 bit Protect Segment
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-jpeg.rst | 92 - Application data segment APP\ :sub:`0`.
94 - Application data segment APP\ :sub:`1`.
96 - Comment segment.
98 - Quantization tables segment.
100 - Huffman tables segment.
|
| D | vidioc-g-jpegcomp.rst | 114 - Comment segment
117 - App segment, driver will always use APP0
|
| /Documentation/filesystems/ |
| D | nilfs2.rst | 115 NILFS_IOCTL_GET_SUINFO Return segment usage info about requested
120 NILFS_IOCTL_SET_SUINFO Modify segment usage info of requested
127 NILFS_IOCTL_GET_SUSTAT Return segment usage statistics. This ioctl
192 for the super block (SB) and segment #0. A segment is the container
197 | |SB| | Segment | Segment | Segment | ... | Segment | |
240 3) Segment usage file (sufile) -- Stores allocation state of segments
252 To stride over segment boundaries, this sequence of files may be split
254 logically one log, is delimited with flags marked in the segment
|
| D | f2fs.rst | 46 segment cleaner to compress the live information from heavily fragmented
72 1. A victim segment is selected through referencing segment usage table.
74 segment summary blocks.
128 segment is cleaned.
217 "fragment:segment" and "fragment:block" are newly added here.
222 In "fragment:segment", f2fs allocates a new segment in ramdom
231 Note that "fragment:block" implicitly enables "fragment:segment"
339 discard_unit=%s Control discard unit, the argument can be "block", "segment"
542 segment size identically, but users can easily modify the sizes by mkfs.
548 |-> align with the segment size
[all …]
|
| /Documentation/arch/powerpc/ |
| D | pci_iov_resource_on_powernv.rst | 96 maps each segment to a PE#. That allows portions of the MMIO space
97 to be assigned to PEs on a segment granularity. For a 2GB window,
98 the segment granularity is 2GB/256 = 8MB.
102 onto a segment alignment/granularity so that the space behind a bridge
120 has 256 segments; however, there is no table for mapping a segment
121 to a PE#. The segment number *is* the PE#.
145 than one segment, we end up with more than one PE#. There is a HW
191 mapped to separate PEs in this window. Each segment can be
195 the segment size matches the smallest VF BAR, which means larger VF
203 PEs (the segment number is the PE#), so there isn't as much
[all …]
|
| /Documentation/i2c/muxes/ |
| D | i2c-mux-gpio.rst | 15 ---------- ---------- Bus segment 1 - - - - -
18 | | | | Bus segment 2 | |
21 | | | | Bus segment M
25 SCL/SDA of the master I2C bus is multiplexed to bus segment 1..M
|
| /Documentation/arch/x86/x86_64/ |
| D | fsgs.rst | 7 memory can use segment register based addressing mode. The following
8 notation is used to address a byte within a segment:
10 Segment-register:Byte-address
12 The segment base address is added to the Byte-address to compute the
16 the segment register.
18 In 32-bit mode the CPU provides 6 segments, which also support segment
28 The FS segment is commonly used to address Thread Local Storage (TLS). FS
37 The GS segment has no common use and can be used freely by
|
| /Documentation/devicetree/bindings/cpufreq/ |
| D | imx-cpufreq-dt.txt | 4 Certain i.MX SoCs support different OPPs depending on the "market segment" and
14 - Supported market segment mask
|
| /Documentation/arch/arm/ |
| D | porting.rst | 78 basis by the kernel. I'll call this the user segment.
81 this the kernel segment.
93 Virtual address for the kernel data segment. Must not be defined
99 The addresses must also be in the kernel segment (see above).
|
| /Documentation/userspace-api/media/ |
| D | frontend.h.rst.exceptions | 13 replace define DTV_ISDBT_LAYERA_SEGMENT_COUNT dtv-isdbt-layer-segment-count
14 replace define DTV_ISDBT_LAYERB_SEGMENT_COUNT dtv-isdbt-layer-segment-count
15 replace define DTV_ISDBT_LAYERC_SEGMENT_COUNT dtv-isdbt-layer-segment-count
|
| /Documentation/usb/ |
| D | misc_usbsevseg.rst | 2 USB 7-Segment Numeric Display
27 raw controls each segment manually,
|
| /Documentation/PCI/ |
| D | pci-error-recovery.rst | 158 If all drivers on the segment/slot return PCI_ERS_RESULT_CAN_RECOVER,
199 all drivers on a segment agree that they can try to recover and if no automatic
212 segment, and thus invalidate the recovery that other devices
213 on the same segment might have done, forcing the whole segment
223 same segment might have failed and thus triggered a
339 drivers if all drivers on the segment have returned
376 recover (disconnect them) and try to let other cards on the same segment
378 be only one driver per segment.
386 device on the segment starting from the error detection and until the
|
| /Documentation/driver-api/ |
| D | i2c.rst | 22 I2C bus segment it manages. On each I2C bus segment will be I2C devices
|
| /Documentation/arch/arm64/ |
| D | memory-tagging-extension.rst | 232 program header for such segment is defined as:
236 :``p_offset``: segment file offset
237 :``p_vaddr``: segment virtual address, same as the corresponding
238 ``PT_LOAD`` segment
240 :``p_filesz``: segment size in file, calculated as ``p_mem_sz / 32``
242 :``p_memsz``: segment size in memory, same as the corresponding
243 ``PT_LOAD`` segment
|
| /Documentation/userspace-api/media/dvb/ |
| D | frontend-property-terrestrial-systems.rst | 150 - :ref:`DTV_ISDBT_SB_SEGMENT_IDX <DTV-ISDBT-SB-SEGMENT-IDX>`
152 - :ref:`DTV_ISDBT_SB_SEGMENT_COUNT <DTV-ISDBT-SB-SEGMENT-COUNT>`
158 - :ref:`DTV_ISDBT_LAYERA_SEGMENT_COUNT <DTV-ISDBT-LAYER-SEGMENT-COUNT>`
166 - :ref:`DTV_ISDBT_LAYERB_SEGMENT_COUNT <DTV-ISDBT-LAYER-SEGMENT-COUNT>`
174 - :ref:`DTV_ISDBT_LAYERC_SEGMENT_COUNT <DTV-ISDBT-LAYER-SEGMENT-COUNT>`
|
12345