Home
last modified time | relevance | path

Searched +full:wait +full:- +full:state (Results 1 – 25 of 183) sorted by relevance

12345678

/Documentation/devicetree/bindings/power/reset/
Dgpio-restart.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/reset/gpio-restart.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Reichel <sre@kernel.org>
17 'open-source' is not found, the GPIO line will be driven in the inactive state. Otherwise its
22 This will also cause an inactive->active edge condition, triggering positive edge triggered
23 reset. After a delay specified by active-delay, the GPIO is set to inactive, thus causing an
24 active->inactive edge, triggering negative edge triggered reset. After a delay specified by
25 inactive-delay, the GPIO is driven active again. After a delay specified by wait-delay, the
[all …]
Dgpio-poweroff.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/reset/gpio-poweroff.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Reichel <sre@kernel.org>
15 from inactive to active. After a delay (active-delay-ms) it
17 delay (inactive-delay-ms) it is configured as active again.
19 the system is still running after waiting some time (timeout-ms).
22 - $ref: restart-handler.yaml#
26 const: gpio-poweroff
[all …]
/Documentation/devicetree/bindings/interconnect/
Dqcom,bcm-voter.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interconnect/qcom,bcm-voter.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm BCM-Voter Interconnect
10 - Georgi Djakov <georgi.djakov@linaro.org>
14 shared system resources by aggregating requests from multiple Resource State
22 - qcom,bcm-voter
24 qcom,tcs-wait:
26 Optional mask of which TCSs (Triggered Command Sets) wait for completion
[all …]
/Documentation/devicetree/bindings/spi/
Darm,pl022-peripheral-props.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/spi/arm,pl022-peripheral-props.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Peripheral-specific properties for Arm PL022 SPI controller
10 - Linus Walleij <linus.walleij@linaro.org>
19 - 0 # SPI
20 - 1 # Texas Instruments Synchronous Serial Frame Format
21 - 2 # Microwire (Half Duplex)
23 pl022,com-mode:
[all …]
/Documentation/ABI/stable/
Dsysfs-transport-srp1 What: /sys/class/srp_remote_ports/port-<h>:<n>/delete
4 Contact: linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org
8 What: /sys/class/srp_remote_ports/port-<h>:<n>/dev_loss_tmo
11 Contact: linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org
12 Description: Number of seconds the SCSI layer will wait after a transport
17 What: /sys/class/srp_remote_ports/port-<h>:<n>/fast_io_fail_tmo
20 Contact: linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org
21 Description: Number of seconds the SCSI layer will wait after a transport
26 What: /sys/class/srp_remote_ports/port-<h>:<n>/port_id
29 Contact: linux-scsi@vger.kernel.org
[all …]
/Documentation/scheduler/
Dcompletion.rst2 Completions - "wait for completion" barrier APIs
6 -------------
8 If you have one or more threads that must wait for some kernel activity
9 to have reached a point or a specific state, completions can provide a
10 race-free solution to this problem. Semantically they are somewhat like a
11 pthread_barrier() and have similar use-cases.
14 misuse of locks/semaphores and busy-loops. Any time you think of using
34 ------
38 - the initialization of the 'struct completion' synchronization object
39 - the waiting part through a call to one of the variants of wait_for_completion(),
[all …]
/Documentation/locking/
Dww-mutex-design.rst2 Wound/Wait Deadlock-Proof Mutex Design
5 Please read mutex-design.rst first, as it applies to wait/wound mutexes too.
7 Motivation for WW-Mutexes
8 -------------------------
14 a handful of situations where the driver needs to wait for buffers to
37 and the deadlock handling approach is called Wait-Die. The name is based on
41 and dies. Hence Wait-Die.
42 There is also another algorithm called Wound-Wait:
46 transaction. Hence Wound-Wait.
48 However, the Wound-Wait algorithm is typically stated to generate fewer backoffs
[all …]
Dmutex-design.rst10 -----------------
24 --------------
28 (->owner) to keep track of the lock state during its lifetime. Field owner
31 to at least L1_CACHE_BYTES, low bits (3) are used to store extra state (e.g.,
32 if waiter list is non-empty). In its most basic form it also includes a
33 wait-queue and a spinlock that serializes access to it. Furthermore,
34 CONFIG_MUTEX_SPIN_ON_OWNER=y systems use a spinner MCS lock (->osq), described
38 taken, depending on the state of the lock:
42 against 0UL, so all 3 state bits above have to be 0). If the lock is
52 The MCS lock (proposed by Mellor-Crummey and Scott) is a simple spinlock
[all …]
/Documentation/block/
Dstat.rst7 The stat file provides several statistics about the state of block
16 represent a consistent snapshot of the state of the device. If the
30 read merges requests number of read I/Os merged with in-queue I/O
32 read ticks milliseconds total wait time for read requests
34 write merges requests number of write I/Os merged with in-queue I/O
36 write ticks milliseconds total wait time for write requests
39 time_in_queue milliseconds total wait time for all requests
41 discard merges requests number of discard I/Os merged with in-queue I/O
43 discard ticks milliseconds total wait time for discard requests
45 flush ticks milliseconds total wait time for flush requests
[all …]
/Documentation/userspace-api/media/mediactl/
Drequest-api.rst1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
4 .. _media-request-api:
12 the same pipeline to reconfigure and collaborate closely on a per-frame basis.
14 to specific frames (aka 'per-frame controls') in order to be used efficiently.
16 While the initial use-case was V4L2, it can be extended to other subsystems
20 it is, it is terribly inefficient: user-space would have to flush all activity
22 be processed with that configuration, and wait until they are all available for
28 specific buffers. This allows user-space to schedule several tasks ("requests")
34 -------------
37 subsystem-specific APIs to support request usage. At the Media Controller
[all …]
Dmedia-request-ioc-queue.rst1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
13 MEDIA_REQUEST_IOC_QUEUE - Queue a request
31 If the media device supports :ref:`requests <media-request-api>`, then
35 :ref:`polled <request-func-poll>` to wait for the request to complete.
40 common error codes. On error both the request and driver state are unchanged.
45 the application to stop streaming to reset the hardware state.
57 On success 0 is returned, on error -1 and the ``errno`` variable is set
59 :ref:`Generic Error Codes <gen-errors>` chapter.
75 The hardware is in a bad state. To recover, the application needs to
76 stop streaming to reset the hardware state and then try to restart
/Documentation/devicetree/bindings/memory-controllers/
Dst,stm32-fmc2-ebi-props.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/st,stm32-fmc2-ebi-props.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Christophe Kerello <christophe.kerello@foss.st.com>
11 - Marek Vasut <marex@denx.de>
14 st,fmc2-ebi-cs-transaction-type:
33 st,fmc2-ebi-cs-cclk-enable:
40 st,fmc2-ebi-cs-mux-enable:
46 st,fmc2-ebi-cs-buswidth:
[all …]
/Documentation/i2c/
Dgpio-fault-injection.rst12 'i2c-fault-injector' subdirectory in the Kernel debugfs filesystem, usually
15 injection. They will be described now along with their intended use-cases.
21 -----
23 By reading this file, you get the current state of SCL. By writing, you can
24 change its state to either force it low or to release it again. So, by using
31 -----
33 By reading this file, you get the current state of SDA. By writing, you can
34 change its state to either force it low or to release it again. So, by using
56 --------------------------
68 -----------------------
[all …]
/Documentation/virt/kvm/
Dvcpu-requests.rst1 .. SPDX-License-Identifier: GPL-2.0
46 ----------
51 time of the kick. Therefore, depending on the mode and state of the VCPU
57 mode that wait on waitqueues. Waking them removes the threads from
64 ---------
66 VCPUs have a mode state, ``vcpu->mode``, that is used to track whether the
68 outside guest mode states. The architecture may use ``vcpu->mode`` to
90 certain VCPU requests, namely KVM_REQ_TLB_FLUSH, to wait until the VCPU
96 VCPU requests are simply bit indices of the ``vcpu->requests`` bitmap.
97 This means general bitops, like those documented in [atomic-ops]_ could
[all …]
/Documentation/arch/arm/
Dcluster-pm-race-avoidance.rst2 Cluster-wide Power-up/power-down race avoidance algorithm
16 ---------
29 cluster-level operations are only performed when it is truly safe to do
35 disabling those mechanisms may itself be a non-atomic operation (such as
38 power-down and power-up at the cluster level.
46 -----------
48 Each cluster and CPU is assigned a state, as follows:
50 - DOWN
51 - COMING_UP
52 - UP
[all …]
/Documentation/maintainer/
Dmaintainer-entry-profile.rst6 The Maintainer Entry Profile supplements the top-level process documents
7 (submitting-patches, submitting drivers...) with
8 subsystem/device-driver-local customs as well as details about the patch
9 submission life-cycle. A contributor uses this document to level set
16 --------
19 convey other subsystem-local infrastructure and mechanisms that aid
24 - Are there notifications when patches are applied to the local tree, or
26 - Does the subsystem have a patchwork instance? Are patchwork state
28 - Any bots or CI infrastructure that watches the list, or automated
30 - Git branches that are pulled into -next?
[all …]
/Documentation/RCU/Design/Expedited-Grace-Periods/
DExpedited-Grace-Periods.rst13 There are two flavors of RCU (RCU-preempt and RCU-sched), with an earlier
14 third RCU-bh flavor having been implemented in terms of the other two.
22 has not yet provided a quiescent state for the current expedited
28 The corresponding handler function checks the CPU's state, motivating
29 a faster quiescent state where possible, and triggering a report
30 of that quiescent state.
32 state, the expedited grace period has completed.
38 RCU-preempt Expedited Grace Periods
41 ``CONFIG_PREEMPTION=y`` kernels implement RCU-preempt.
42 The overall flow of the handling of a given CPU by an RCU-preempt
[all …]
/Documentation/devicetree/bindings/sound/
Dcs35l36.txt5 - compatible : "cirrus,cs35l36"
7 - reg : the I2C address of the device for I2C
9 - VA-supply, VP-supply : power supplies for the device,
13 - cirrus,boost-ctl-millivolt : Boost Voltage Value. Configures the boost
18 - cirrus,boost-peak-milliamp : Boost-converter peak current limit in mA.
24 - cirrus,boost-ind-nanohenry : Inductor estimation LBST reference value.
32 - cirrus,multi-amp-mode : Boolean to determine if there are more than
33 one amplifier in the system. If more than one it is best to Hi-Z the ASP
36 - cirrus,boost-ctl-select : Boost converter control source selection.
39 0x00 - Control Port Value
[all …]
/Documentation/input/joydev/
Djoystick-api.rst1 .. _joystick-api:
7 :Author: Ragnar Hojland Espinosa <ragnar@macula.net> - 7 Aug 1998
18 driver now reports only any changes of its state. See joystick-api.txt,
35 (JS_EVENT_INIT) that you can read to obtain the initial state of the
65 -------------
71 #define JS_EVENT_INIT 0x80 /* initial state of device */
86 ---------------
108 --------------
110 For an axis, ``value`` is a signed integer between -32767 and +32767
141 -------------
[all …]
/Documentation/userspace-api/media/dvb/
Ddmx-set-filter.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
11 ----
16 --------
23 ---------
33 -----------
37 to wait for a section to be loaded. A value of 0 means that no timeout
39 state whether a section should be CRC-checked, whether the filter should
40 be a "one-shot" filter, i.e. if the filtering operation should be
43 :ref:`DMX_START` ioctl call). If a filter was previously set-up, this
47 ------------
[all …]
/Documentation/crypto/
Dapi-samples.rst5 -----------------------------------------------
7 This code encrypts some data with AES-256-XTS. For sake of example,
8 all inputs are random bytes, the encryption is done in-place, and it's
20 DECLARE_CRYPTO_WAIT(wait);
21 u8 iv[16]; /* AES-256-XTS takes a 16-byte IV */
22 u8 key[64]; /* AES-256-XTS takes a 64-byte key */
28 * In real-world use, a tfm and key are typically used for many
49 err = -ENOMEM;
56 err = -ENOMEM;
65 * Encrypt the data in-place.
[all …]
/Documentation/userspace-api/media/
Dgen-errors.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
10 .. _gen-errors:
14 .. flat-table:: Generic error codes
15 :header-rows: 0
16 :stub-columns: 0
20 - - ``EAGAIN`` (aka ``EWOULDBLOCK``)
22 - The ioctl can't be handled because the device is in state where it
25 is also returned when the ioctl would need to wait for an event,
26 but the device was opened in non-blocking mode.
28 - - ``EBADF``
[all …]
/Documentation/driver-api/dmaengine/
Ddmatest.rst21 capability of the following: DMA_MEMCPY (memory-to-memory), DMA_MEMSET
22 (const-to-memory or memory-to-memory, when emulated), DMA_XOR, DMA_PQ.
28 Part 1 - How to build the test module
33 Device Drivers -> DMA Engine support -> DMA Test client
38 Part 2 - When dmatest is built as a module
57 Example of multi-channel test usage (new in the 5.0 kernel)::
68 For all tests, starting in the 5.0 kernel, either single- or multi-channel,
80 % ls -1 /sys/class/dma/
88 The following command returns the state of the test. ::
92 To wait for test completion userspace can poll 'run' until it is false, or use
[all …]
/Documentation/networking/
Doperstates.rst1 .. SPDX-License-Identifier: GPL-2.0
11 Linux distinguishes between administrative and operational state of an
12 interface. Administrative state is the result of "ip link set dev
17 - ethernet requires to be plugged into the switch and, depending on
19 to be performed before user data can be transferred. Operational state
23 influence operational state. To accommodate this, operational state is
25 a RFC2863 compatible state that is derived from these flags, a policy,
32 Both admin and operational state can be queried via the netlink
37 These values contain interface state:
43 Interface is in RFC2863 operational state UP or UNKNOWN. This is for
[all …]
/Documentation/devicetree/bindings/i2c/
Di2c-mux-gpio.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/i2c/i2c-mux-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: GPIO-based I2C Bus Mux
10 - Wolfram Sang <wsa@kernel.org>
15 +-----+ +-----+
17 +------------+ +-----+ +-----+
19 | | /--------+--------+
20 | +------+ | +------+ child bus A, on GPIO value set to 0
[all …]

12345678