Searched full:element (Results 1 – 25 of 162) sorted by relevance
1234567
| /Documentation/mhi/ |
| D | mhi.rst | 95 [Read Pointer (RP)] ----------->[Ring Element] } TD
96 [Write Pointer (WP)]- [Ring Element]
97 - [Ring Element]
98 --------->[Ring Element]
99 [Ring Element]
108 * RP indicates the next element to be serviced by the device.
109 * When the host has a new buffer to send, it updates the ring element with
110 buffer information, increments the WP to the next element and rings the
122 [Read Pointer (RP)] ----------->[Ring Element] } ED
123 [Write Pointer (WP)]- [Ring Element]
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | qcom,coresight-tpdm.yaml | 46 qcom,dsb-element-bits:
48 Specifies the DSB(Discrete Single Bit) element size supported by
50 is enabled. DSB element size currently only supports 32-bit and 64-bit.
53 qcom,cmb-element-bits:
55 Specifies the CMB(Continuous Multi-Bit) element size supported by
57 is enabled. CMB element size currently only supports 8-bit, 32-bit
112 qcom,dsb-element-bits = <32>;
132 qcom,cmb-element-bits = <64>;
|
| /Documentation/arch/sparc/oradax/ |
| D | dax-hv-api.txt | 301 36.2.1.1.2. Primary Input Element Size
303 …For primary input data streams with fixed size elements, the element size must be indicated in the…
316 … 0 Element is stored as value minus 1 (0 evaluates to 1, 1 evaluates
318 1 Element is stored as value
320 36.2.1.1.4. Secondary Input Element Size
322 Secondary input element size is encoded as a two bit field:
331 36.2.1.1.5. Input Element Offsets
335 …value of 0 indicates that the first input element begins at the most significant bit in the first …
348 …output encodings, and up to four supported element sizes per encoding. Not all output encodings are
365 0xD 2 byte elements where each element is the index value of a bit,
[all …]
|
| /Documentation/bpf/ |
| D | map_sockmap.rst | 132 - ``BPF_ANY``: Create a new element or update an existing element.
133 - ``BPF_NOEXIST``: Create a new element only if it did not exist.
134 - ``BPF_EXIST``: Update an existing element.
153 - ``BPF_ANY``: Create a new element or update an existing element.
154 - ``BPF_NOEXIST``: Create a new element only if it did not exist.
155 - ``BPF_EXIST``: Update an existing element.
242 For ``sendmsg()`` hooks this is likely the first scatterlist element. But for
282 - BPF_ANY: Create a new element or update an existing element.
283 - BPF_NOEXIST: Create a new element only if it did not exist.
284 - BPF_EXIST: Update an existing element.
[all …]
|
| D | map_bloom_filter.rst | 13 quickly test whether an element exists in a set. In a bloom filter,
20 - push: adding an element to the map
21 - peek: determining whether an element is present in the map
23 BPF programs must use ``bpf_map_push_elem`` to add an element to the
160 This snippet shows how to add an element to a bloom filter from
|
| D | map_queue_stack.rst | 38 An element ``value`` can be added to a queue or stack using the
41 when the queue or stack is full, the oldest element will be removed to
52 This helper fetches an element ``value`` from a queue or stack without
63 This helper removes an element into ``value`` from a queue or
|
| D | map_cpumap.rst | 74 - BPF_ANY: Create a new element or update an existing element.
75 - BPF_NOEXIST: Create a new element only if it did not exist.
76 - BPF_EXIST: Update an existing element.
|
| D | map_array.rst | 43 This helper returns a pointer into the array element, so to avoid data races
60 To clear an array element, you may use ``bpf_map_update_elem()`` to insert a
118 This example BPF program shows how to access an array element.
187 This snippet shows how to retrieve an element value from an array.
|
| D | map_hash.rst | 61 - ``BPF_ANY`` will create a new element or update an existing element
62 - ``BPF_NOEXIST`` will create a new element only if one did not already
64 - ``BPF_EXIST`` will update an existing element
244 size. With a minimum of a single element and maximum budget of 128 at a time.
|
| /Documentation/RCU/ |
| D | rcuref.rst | 50 search_and_reference() could potentially hold reference to an element which
81 Sometimes, a reference to the element needs to be obtained in the
121 search_and_reference() cannot find this element, which means that the value
123 readers that can or ever will be able to reference the element. The
124 element can therefore safely be freed. This in turn guarantees that if
125 any reader finds the element, that reader may safely acquire a reference
|
| D | UP.rst | 21 is referencing element B when it is interrupted by softirq processing,
22 which deletes element B, and then invokes call_rcu() to free element B
27 element B. This situation can greatly decrease the life expectancy of
42 on each element as it is scanned. Suppose further that this function
43 deletes element B from the list, then passes it to call_rcu() for deferred
|
| /Documentation/sound/designs/ |
| D | channel-mapping-api.rst | 39 control element features.
41 As a ground design, each PCM substream may contain a control element
43 element is specified by:
52 Each control element provides at least the TLV read operation and the
148 the given stream. The control element returns an integer array
|
| /Documentation/scsi/ |
| D | scsi-changer.rst | 128 Send INITIALIZE ELEMENT STATUS command to the changer
132 timeout for the INITIALIZE ELEMENT STATUS command
145 are some vendor-specific element types. Grundig for example
147 CDs, which is addressed as element 0xc000 (type 5). To tell the
148 driver about this vendor-specific element, use this::
156 values, this way you can configure the element types 5-8.
|
| /Documentation/devicetree/bindings/net/ |
| D | microchip,lan78xx.txt | 14 - microchip,led-modes: a 0..4 element vector, with each element configuring
|
| /Documentation/driver-api/iio/ |
| D | buffers.rst | 29 called a scan element. The important bits configuring scan elements are
38 * :file:`type`, description of the scan element data storage within the buffer
48 repeat element is 0 or 1, then the repeat value is omitted.
65 will have the following scan element type for each axis::
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | srio-rmu.txt | 65 element is associated with the transmit (TX) interrupt and the
66 second element is associated with the receive (RX) interrupt.
95 element is associated with the transmit (TX) interrupt and the
96 second element is associated with the receive (RX) interrupt.
|
| /Documentation/power/ |
| D | pm_qos_interface.rst | 32 Will insert an element into the CPU latency QoS list with the target value.
39 Will update the list element pointed to by the handle with the new target
44 Will remove the element. After removal it will update the aggregate target
107 Will insert an element into the list for that identified device with the
114 Will update the list element pointed to by the handle with the new target
119 Will remove the element. After removal it will update the aggregate target
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-detect.rst | 57 detection mode. Matrix element (0, 0) represents the cell at the
63 detection mode. Matrix element (0, 0) represents the cell at the
|
| /Documentation/core-api/ |
| D | union_find.rst | 17 Initialization: Resetting each element as an individual set, with
20 Find: Determine which set a particular element belongs to, usually by
21 returning a “representative element” of that set. This operation
|
| /Documentation/filesystems/ |
| D | path-lookup.txt | 10 child with the next element, and so on.
27 next path element. This is inefficient and unscalable. It is inefficient
28 because of the locks and atomic operations required for every dentry element
48 (usually the final element, or parent of final element). This is done by taking
51 iteratively for each subsequent name element, look up the child of the current
69 - perform dcache hash name lookups on (parent, name element) tuples;
248 | inode: 10 | path element which is "home"...
257 +---------------------+ check inode and look up the next element.
318 * NULL dentry (ie. any uncached path element)
344 element, nodentry for missing dentry, revalidate for filesystem revalidate
|
| /Documentation/admin-guide/ |
| D | sysfs-rules.rst | 64 - a directory name, identical to the last element of the devpath
72 last element of the target path
79 last element of the target path
146 path as an element. Assuming the existence of the "device"-link for
156 element. Assuming the existence of these links for devices which are
|
| /Documentation/translations/zh_CN/admin-guide/ |
| D | bootconfig.rst | 124 bar = 1, # 1st element
125 2, # 2nd element
126 3 # 3rd element
|
| /Documentation/translations/zh_TW/admin-guide/ |
| D | bootconfig.rst | 124 bar = 1, # 1st element
125 2, # 2nd element
126 3 # 3rd element
|
| /Documentation/iio/ |
| D | iio_devbuf.rst | 66 a scan element. The scan elements attributes are presented below.
84 Read-only attribute containing the description of the scan element data storage
94 repeat element is 0 or 1, then the repeat value is omitted.
111 will have the following scan element type for each axis:
|
| /Documentation/devicetree/bindings/sound/ |
| D | max9860.txt | 12 - clock-names : Required element: "mclk".
|
1234567