Searched full:chain (Results 1 – 25 of 121) sorted by relevance
12345
| /Documentation/devicetree/bindings/iio/adc/ |
| D | adi,ad7944.yaml | 41 enum: [ single, chain ]
60 * chain: The datasheet calls this "chain mode". This mode is used to save
62 one chip is tied to the SDO of the next chip in the chain and the SDI of
63 the last chip in the chain is tied to GND. Only the first chip in the
64 chain is connected to the SPI bus. The CNV line of all chips are tied
103 the conversions and selects the SPI mode of the device (chain or CS). In
129 line goes high while the SDI and CNV lines are high (chain mode),
162 # chain mode has lower SCLK max rate and doesn't work when TURBO is enabled
168 const: chain
|
| D | nxp,imx93-adc.yaml | 32 ECH (End of Chain), JEOC (End of Injected Conversion) and
33 JECH (End of injected Chain).
|
| /Documentation/arch/x86/ |
| D | kernel-stacks.rst | 125 If it fits into the frame pointer chain, we print it without a question
128 If the address does not fit into our expected frame pointer chain we
131 - either the address is not part of the call chain: it's just stale
135 - or it is part of the call chain, but the frame pointer was not set
138 This way we will always print out the real call chain (plus a few more
140 or not - but in most cases we'll get the call chain right as well. The
147 we still print out the real call chain as well - just with more question
152 reconstructing the call chain. This works most of the time.
|
| /Documentation/netlink/specs/ |
| D | nftables.yaml | 116 name: chain-flags
272 name: chain-attrs
277 doc: name of the table containing the chain
282 doc: numeric handle of the chain
286 doc: name of the chain
296 doc: numeric policy of the chain
301 doc: number of references to this chain
305 doc: type name of the chain
310 doc: counter specification of the chain
315 doc: chain flags
[all …]
|
| /Documentation/RCU/ |
| D | rculist_nulls.rst | 102 from a chain, and inserted into another chain. If new chain was empty
104 detect the fact that it missed following items in original chain.
148 to another chain) checking the final 'nulls' value if
149 the lookup met the end of chain. If final 'nulls' value
151 the beginning. If the object was moved to the same chain,
184 // We probably met an item that was moved to another chain.
212 * insert obj in RCU way (readers might be traversing chain)
|
| /Documentation/locking/ |
| D | rt-mutex-design.rst | 79 PI chain
80 - The PI chain is an ordered series of locks and processes that cause
128 PI chain
131 The PI chain is a list of processes and mutexes that may cause priority
132 inheritance to take place. Multiple chains may converge, but a chain
150 The chain would be::
157 The chain for F would be::
173 also call it the Top of the chain) must be equal to or higher in priority
174 than the processes to the left or below in the chain.
192 If process G has the highest priority in the chain, then all the tasks up
[all …]
|
| /Documentation/crypto/ |
| D | asymmetric-keys.rst | 362 - "key_or_keyring:<key or keyring serial number>[:chain]"
370 When the "chain" option is provided at the end of the string, the keys
376 certificate chain to be validated::
383 # Create and restrict a keyring for the certificate chain
384 chain_id=`keyctl add keyring chain "" @s`
385 keyctl restrict_keyring $chain_id asymmetric key_or_keyring:$root_id:chain
387 # Attempt to add each certificate in the chain, starting with the
393 If the final end-entity certificate is successfully added to the "chain"
394 keyring, we can be certain that it has a valid signing chain going back to
397 A single keyring can be used to verify a chain of signatures by
[all …]
|
| D | async-tx-api.rst | 31 The async_tx API provides methods for describing a chain of asynchronous
36 the API will fit the chain of operations to the available offload
53 2. cross channel dependency chains: the API allows a chain of dependent
97 operations complete. When an application needs to submit a chain of
134 async_<operation>, or when the application needs to submit a chain of
136 completion interrupt/callback at the end of the chain.
|
| /Documentation/mm/ |
| D | ksm.rst | 31 the stable tree. The tree node becomes a "chain" that links one or
35 Every "chain" and all "dups" linked into a "chain" enforce the
59 stable_node chain->hlist to check for pruning) and higher
|
| D | zsmalloc.rst | 100 The optimal zspage chain size for each size class is calculated during the
127 find that the most optimal zspage configuration for this class is a chain
142 As the zspage chain size for class #96 increases, its key characteristics
161 Increasing the size of the chain of zspages also results in a higher watermark
165 For zspage chain size of 8, huge class watermark becomes 3632 bytes:::
178 For zspage chain size of 16, huge class watermark becomes 3840 bytes:::
205 Overall the combined zspage chain size effect on zsmalloc pool configuration:::
261 memory pressure (as some zspages have larger chain sizes) in cases where there
|
| /Documentation/devicetree/bindings/ |
| D | common-properties.txt | 69 host controller, a daisy-chain appears as a single device, but the number
72 daisy-chain comprises to determine the amount of data exchanged, how many
76 - #daisy-chained-devices: Number of devices in the daisy-chain (default is 1).
|
| /Documentation/driver-api/media/drivers/ |
| D | pxa_camera.rst | 26 capture. The new buffers are "appended" at the tail of the DMA chain, and
94 starts the DMA chain.
96 The DMA chain starts transferring data into videobuffer RAM pages.
123 A typical running chain is :
134 After the chaining is finished, the chain looks like :
152 - DMA chain is Videobuffer1 + Videobuffer2
170 - Videobuffer3 capture is not scheduled on DMA chain (as it stopped !!!)
186 and Videobuffer3 is scheduled on DMA chain.
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-w1_ds28ea00 | 4 Description: Support for the DS28EA00 chain sequence function
|
| /Documentation/networking/ |
| D | nf_flowtable.rst | 85 flowtable and add one rule to your forward chain::
91 chain y {
102 nftables ingress chain (make sure the flowtable priority is smaller than the
103 nftables ingress chain hence the flowtable runs before in the pipeline).
105 The 'flow offload' action from the forward chain 'y' adds an entry to the
|
| /Documentation/admin-guide/ |
| D | sysfs-rules.rst | 163 - Position of devices along device chain can change.
165 or the chain of parent devices. The kernel is free to insert devices into
166 the chain. You must always request the parent device you are looking for
167 by its subsystem value. You need to walk up the chain until you find
170 access the chain of parents is a bug in the application.
|
| /Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 86 net eth1: Chain tail located at descr=20
87 net eth1: Chain head is at 20
146 net eth1: Chain tail located at descr=255
147 net eth1: Chain head is at 255
173 of the RX chain seems to show it is empty, then it is probable that
|
| /Documentation/bpf/ |
| D | prog_cgroup_sockopt.rst | 28 chain finish (i.e. kernel ``setsockopt`` handling will *not* be executed).
38 * ``1`` - success, continue with next BPF program in the cgroup chain.
85 then the next program in the chain (A) will see those changes,
|
| /Documentation/fault-injection/ |
| D | notifier-error-inject.rst | 5 specified notifier chain callbacks. It is useful to test the error handling of
6 notifier call chain failures which is rarely executed. There are kernel
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices | 21 chain will have emitted uevent messages, so userspace
|
| D | sysfs-bus-siox | 29 The new device is added to the end of the existing chain.
35 Write-only file. A single write removes the last device in the siox chain.
|
| /Documentation/devicetree/bindings/timer/ |
| D | ti,keystone-timer.txt | 6 timers, each half can operate in conjunction (chain mode) or independently
|
| D | ti,da830-timer.yaml | 16 in conjunction (chain mode) or independently (unchained mode) of each other.
|
| /Documentation/devicetree/bindings/net/ |
| D | allwinner,sun8i-a83t-emac.yaml | 85 External RGMII PHY TX clock delay chain value in ps.
93 External RGMII PHY TX clock delay chain value in ps.
110 External RGMII PHY TX clock delay chain value in ps.
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | brcm,bcm2836-l1-intc.yaml | 16 peripheral (GPU) events, which chain to the BCM2835-style interrupt
|
| /Documentation/iio/ |
| D | ad7944.rst | 71 Chain mode, without busy indicator
89 ``"chain"``, add the ``spi-cs-high`` flag, add the ``#daisy-chained-devices``
131 In "chain" mode, additional chips will appear as additional voltage input
147 In "chain" mode, additional chips will appear as additional voltage input
|
12345