Home
last modified time | relevance | path

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

123456

/Documentation/devicetree/bindings/power/reset/
Dgpio-restart.txt6 handler. If the optional properties 'open-source' is not found, the GPIO line
7 will be driven in the inactive state. Otherwise its not driven until
13 inactive->active edge condition, triggering positive edge triggered
14 reset. After a delay specified by active-delay, the GPIO is set to
15 inactive, thus causing an active->inactive edge, triggering negative edge
16 triggered reset. After a delay specified by inactive-delay, the GPIO
17 is driven active again. After a delay specified by wait-delay, the
21 - compatible : should be "gpio-restart".
22 - gpios : The GPIO to set high/low, see "gpios property" in
28 - open-source : Treat the GPIO as being open source and defer driving
[all …]
Dgpio-poweroff.txt7 state. Otherwise its configured as an input.
9 When the power-off handler is called, the gpio is configured as an
11 condition. This will also cause an inactive->active edge condition, so
13 the GPIO is set to inactive, thus causing an active->inactive edge,
19 - compatible : should be "gpio-poweroff".
20 - gpios : The GPIO to set high/low, see "gpios property" in
26 - input : Initially configure the GPIO line as an input. Only reconfigure
27 it to an output when the power-off handler is called. If this optional
29 inactive state.
30 - active-delay-ms: Delay (default 100) to wait after driving gpio active
[all …]
/Documentation/devicetree/bindings/arm/msm/
Dqcom,idle-state.txt3 ARM provides idle-state node to define the cpuidle states, as defined in [1].
4 cpuidle-qcom is the cpuidle driver for Qualcomm SoCs and uses these idle
6 The idle states supported by the QCOM SoC are defined as -
16 trigger to execute the SPM state machine. The SPM state machine waits for the
19 the SPM state machine out of its wait, the next step is to ensure that the
21 execution. This state is defined as a generic ARM WFI state by the ARM cpuidle
22 driver and is not defined in the DT. The SPM state machine should be
23 configured to execute this state by default and after executing every other
24 state below.
26 Retention: Retention is a low power state where the core is clock gated and
[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/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/devicetree/bindings/spi/
Dspi-pl022.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/spi/spi-pl022.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
13 - $ref: "spi-controller.yaml#"
22 - compatible
27 - const: arm,pl022
28 - const: arm,primecell
39 clock-names:
[all …]
/Documentation/locking/
Dww-mutex-design.rst2 Wound/Wait Deadlock-Proof Mutex Design
5 Please read mutex-design.txt 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 at 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
55 already-queued I/O request.
[all …]
/Documentation/media/uapi/mediactl/
Drequest-api.rst1 .. This file is dual-licensed: you can use it either under the terms
21 .. Foundation, with no Invariant Sections, no Front-Cover Texts
22 .. and no Back-Cover Texts. A copy of the license is included at
23 .. Documentation/media/uapi/fdl-appendix.rst.
25 .. TODO: replace it to GPL-2.0 OR GFDL-1.1-or-later WITH no-invariant-sections
27 .. _media-request-api:
35 the same pipeline to reconfigure and collaborate closely on a per-frame basis.
37 to specific frames (aka 'per-frame controls') in order to be used efficiently.
39 While the initial use-case was V4L2, it can be extended to other subsystems
43 it is, it is terribly inefficient: user-space would have to flush all activity
[all …]
Dmedia-request-ioc-queue.rst1 .. This file is dual-licensed: you can use it either under the terms
21 .. Foundation, with no Invariant Sections, no Front-Cover Texts
22 .. and no Back-Cover Texts. A copy of the license is included at
23 .. Documentation/media/uapi/fdl-appendix.rst.
25 .. TODO: replace it to GPL-2.0 OR GFDL-1.1-or-later WITH no-invariant-sections
36 MEDIA_REQUEST_IOC_QUEUE - Queue a request
56 If the media device supports :ref:`requests <media-request-api>`, then
60 :ref:`polled <request-func-poll>` to wait for the request to complete.
65 common error codes. On error both the request and driver state are unchanged.
70 the application to stop streaming to reset the hardware state.
[all …]
/Documentation/RCU/Design/Expedited-Grace-Periods/
DExpedited-Grace-Periods.html1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
5 <meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
15 There are two flavors of RCU (RCU-preempt and RCU-sched), with an earlier
16 third RCU-bh flavor having been implemented in terms of the other two.
22 <li> <a href="#RCU-preempt Expedited Grace Periods">
23 RCU-preempt Expedited Grace Periods</a>
24 <li> <a href="#RCU-sched Expedited Grace Periods">
25 RCU-sched Expedited Grace Periods</a>
38 has not yet provided a quiescent state for the current expedited
44 The corresponding handler function checks the CPU's state, motivating
[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/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/devicetree/bindings/regulator/
Dqcom,rpmh-regulator.txt3 rpmh-regulator devices support PMIC regulator management via the Voltage
5 processor communicates with these hardware blocks via a Resource State
7 parameters for a given regulator: enable state, output voltage, and operating
9 its enable state. Despite its name, the XOB is capable of controlling the
10 enable state of any PMIC peripheral. It is used for clock buffers, low-voltage
25 PM8005: smps1 - smps4
26 PM8009: smps1 - smps2, ldo1 - ldo7
27 PM8150: smps1 - smps10, ldo1 - ldo18
28 PM8150L: smps1 - smps8, ldo1 - ldo11, bob, flash, rgb
29 PM8998: smps1 - smps13, ldo1 - ldo28, lvs1 - lvs2
[all …]
/Documentation/virt/kvm/
Dvcpu-requests.rst44 ----------
49 time of the kick. Therefore, depending on the mode and state of the VCPU
55 mode that wait on waitqueues. Waking them removes the threads from
62 ---------
64 VCPUs have a mode state, ``vcpu->mode``, that is used to track whether the
66 outside guest mode states. The architecture may use ``vcpu->mode`` to
88 certain VCPU requests, namely KVM_REQ_TLB_FLUSH, to wait until the VCPU
94 VCPU requests are simply bit indices of the ``vcpu->requests`` bitmap.
95 This means general bitops, like those documented in [atomic-ops]_ could
98 clear_bit(KVM_REQ_UNHALT & KVM_REQUEST_MASK, &vcpu->requests);
[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 conerter control source selection.
39 0x00 - Control Port Value
[all …]
/Documentation/networking/
Doperstates.txt4 Linux distinguishes between administrative and operational state of an
5 interface. Administrative state is the result of "ip link set dev
10 - ethernet requires to be plugged into the switch and, depending on
12 to be performed before user data can be transferred. Operational state
16 influence operational state. To accommodate this, operational state is
18 a RFC2863 compatible state that is derived from these flags, a policy,
24 Both admin and operational state can be queried via the netlink
29 These values contain interface state:
34 Interface is in RFC2863 operational state UP or UNKNOWN. This is for
44 contains RFC2863 state of the interface in numeric representation:
[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/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/filesystems/caching/
Dobject.txt2 IN-KERNEL CACHE OBJECT REPRESENTATION AND MANAGEMENT
11 (*) Object management state machine.
13 - Provision of cpu time.
14 - Locking simplification.
25 FS-Cache maintains an in-kernel representation of each object that a netfs is
29 FS-Cache also maintains a separate in-kernel representation of the objects that
36 represented by multiple objects - an index may exist in more than one cache -
45 : +-----------+ :
46 +----------->| IObject | :
47 +-----------+ | : +-----------+ :
[all …]
/Documentation/driver-api/dmaengine/
Ddmatest.rst11 capability of the following: DMA_MEMCPY (memory-to-memory), DMA_MEMSET
12 (const-to-memory or memory-to-memory, when emulated), DMA_XOR, DMA_PQ.
18 Part 1 - How to build the test module
23 Device Drivers -> DMA Engine support -> DMA Test client
28 Part 2 - When dmatest is built as a module
47 Example of multi-channel test usage (new in the 5.0 kernel)::
58 For all tests, starting in the 5.0 kernel, either single- or multi-channel,
70 % ls -1 /sys/class/dma/
78 The following command returns the state of the test. ::
82 To wait for test completion userpace can poll 'run' until it is false, or use
[all …]
/Documentation/media/uapi/dvb/
Ddmx-set-filter.rst4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
5 .. and no Back-Cover Texts. A copy of the license is included at
6 .. Documentation/media/uapi/fdl-appendix.rst.
8 .. TODO: replace it to GFDL-1.1-or-later WITH no-invariant-sections
17 ----
23 --------
29 ---------
32 File descriptor returned by :c:func:`open() <dvb-dmx-open>`.
40 -----------
44 to wait for a section to be loaded. A value of 0 means that no timeout
[all …]
/Documentation/media/uapi/
Dgen-errors.rst4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
5 .. and no Back-Cover Texts. A copy of the license is included at
6 .. Documentation/media/uapi/fdl-appendix.rst.
8 .. TODO: replace it to GFDL-1.1-or-later WITH no-invariant-sections
17 .. _gen-errors:
21 .. flat-table:: Generic error codes
22 :header-rows: 0
23 :stub-columns: 0
27 - - ``EAGAIN`` (aka ``EWOULDBLOCK``)
29 - The ioctl can't be handled because the device is in state where it
[all …]
/Documentation/devicetree/bindings/memory-controllers/
Darm,pl172.txt5 - compatible: Must be "arm,primecell" and exactly one from
8 - reg: Must contains offset/length value for controller.
10 - #address-cells: Must be 2. The partition number has to be encoded in the
11 first address cell and it may accept values 0..N-1
12 (N - total number of partitions). The second cell is the
15 - #size-cells: Must be set to 1.
17 - ranges: Must contain one or more chip select memory regions.
19 - clocks: Must contain references to controller clocks.
21 - clock-names: Must contain "mpmcclk" and "apb_pclk".
23 - clock-ranges: Empty property indicating that child nodes can inherit
[all …]

123456