Searched +full:wait +full:- +full:on +full:- +full:write (Results 1 – 25 of 156) sorted by relevance
1234567
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | ti,gpmc-child.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/memory-controllers/ti,gpmc-child.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Tony Lindgren <tony@atomide.com> 11 - Roger Quadros <rogerq@kernel.org> 24 gpmc,sync-clk-ps: 28 # Chip-select signal timings corresponding to GPMC_CONFIG2: 29 gpmc,cs-on-ns: 33 gpmc,cs-rd-off-ns: [all …]
|
| D | st,stm32-fmc2-ebi-props.yaml | 1 # 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: 25 8: Synchronous read synchronous write PSRAM. 26 9: Synchronous read asynchronous write PSRAM. 27 10: Synchronous read synchronous write NOR. [all …]
|
| D | arm,pl172.txt | 5 - 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 …]
|
| D | ti-aemif.txt | 4 provide a glue-less interface to a variety of asynchronous memory devices like 11 Davinci DM646x - http://www.ti.com/lit/ug/sprueq7c/sprueq7c.pdf 12 OMAP-L138 (DA850) - http://www.ti.com/lit/ug/spruh77a/spruh77a.pdf 13 Kestone - http://www.ti.com/lit/ug/sprugz3a/sprugz3a.pdf 17 - compatible: "ti,davinci-aemif" 18 "ti,keystone-aemif" 19 "ti,da850-aemif" 21 - reg: contains offset/length value for AEMIF control registers 24 - #address-cells: Must be 2. The partition number has to be encoded in the 25 first address cell and it may accept values 0..N-1 [all …]
|
| /Documentation/devicetree/bindings/bus/ |
| D | qcom,ebi2.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 external memory (such as NAND or other memory-mapped peripherals) whereas 16 data lines (16 bits), OE (output enable), ADV (address valid, used on some 17 NOR flash memories), WE (write enable). This on top of 6 different chip selects 20 Apparently this bus is clocked at 64MHz. It has dedicated pins on the package 21 and the bus can only come out on these pins, however if some of the pins are 25 Also CS1 and CS2 has -A and -B signals. Why they have that is unclear to me. 31 CS0 GPIO134 0x1a800000-0x1b000000 (8MB) [all …]
|
| /Documentation/block/ |
| D | stat.rst | 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 33 write I/Os requests number of write I/Os processed 34 write merges requests number of write I/Os merged with in-queue I/O 35 write sectors sectors number of sectors written 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/misc-devices/ |
| D | spear-pcie-gadget.rst | 1 .. SPDX-License-Identifier: GPL-2.0 37 ----------------------- 52 write behavior of nodes: 53 ------------------------ 56 link write UP to enable ltsmm DOWN to disable 57 int_type write interrupt type to be configured and (int_type could be 61 inta write 1 to assert INTA and 0 to de-assert. 62 send_msi write MSI vector to be sent. 63 vendor_id write vendor id(hex) to be programmed. 64 device_id write device id(hex) to be programmed. [all …]
|
| /Documentation/hwmon/ |
| D | abituguru-datasheet.rst | 5 First of all, what I know about uGuru is no fact based on any help, hints or 6 datasheet from Abit. The data I have got on uGuru have I assembled through 14 Olle Sandberg <ollebull@gmail.com>, 2005-05-25 19 and extended with write support and info on more databanks, the write support 27 Hans de Goede <j.w.r.degoede@hhs.nl>, 28-01-2006 33 As far as known the uGuru is always placed at and using the (ISA) I/O-ports 34 0xE0 and 0xE4, so we don't have to scan any port-range, just check what the two 35 ports are holding for detection. We will refer to 0xE0 as CMD (command-port) 39 present. We have to check for two different values at data-port, because 41 later on attached again data-port will hold 0x08, more about this later. [all …]
|
| /Documentation/i2c/ |
| D | gpio-fault-injection.rst | 8 injection driver can create special states on the bus which the other I2C bus 12 'i2c-fault-injector' subdirectory in the Kernel debugfs filesystem, usually 15 injection. They will be described now along with their intended use-cases. 21 ----- 31 ----- 48 there are I2C client devices which detect a stuck SDA on their side and release 49 it on their own after a few milliseconds. Also, there might be an external 51 and will init a bus recovery on its own. If you want to implement bus recovery 56 -------------------------- 58 This file is write only and you need to write the address of an existing I2C [all …]
|
| /Documentation/driver-api/mmc/ |
| D | mmc-dev-attrs.rst | 8 The following attributes are read/write. 11 force_ro Enforce read-only access even if write protect switch is off. 17 All attributes are read-only. 37 rel_sectors Reliable write sector count 45 Note on Erase Size and Preferred Erase Size: 52 if the card is block-addressed, 0 otherwise. 58 1. A single erase command will make all other I/O on 59 the card wait. This is not a problem if the whole card 61 I/O for another partition on the same card wait for the 62 duration of the erase - which could be a several [all …]
|
| /Documentation/accounting/ |
| D | delay-accounting.rst | 5 Tasks encounter delays in execution when they wait 7 runnable task may wait for a free CPU to run on. 9 The per-task delay accounting functionality measures 18 g) write-protect copy 35 statistics of a task are available both during its lifetime as well as on its 40 --------- 44 generic data structure to userspace corresponding to per-pid and per-tgid 53 cache, direct compact, write-protect copy, IRQ/SOFTIRQ etc. 60 When a task exits, records containing the per-task statistics 62 task of a thread group, the per-tgid statistics are also sent. More details [all …]
|
| /Documentation/filesystems/spufs/ |
| D | spufs.rst | 1 .. SPDX-License-Identifier: GPL-2.0 10 spufs - the SPU file system 16 The SPU file system is used on PowerPC machines that implement the Cell 21 message queues. Users that have write permissions on the file system 26 logical SPU. Users can change permissions on those files, but not actu- 43 The files in spufs mostly follow the standard behavior for regular sys- 44 tem calls like read(2) or write(2), but often support only a subset of 45 the operations supported on regular file systems. This list details the 50 all files that support the write(2) operation also support writev(2). 55 All files support the chmod(2)/fchmod(2) and chown(2)/fchown(2) opera- [all …]
|
| /Documentation/RCU/ |
| D | rcu.rst | 6 The basic idea behind RCU (read-copy update) is to split destructive 11 since dropped their references. For example, an RCU-protected deletion 12 from a linked list would first remove the item from the list, wait for 14 information on using RCU with linked lists. 17 -------------------------- 19 - Why would anyone want to use RCU? 21 The advantage of RCU's two-part approach is that RCU readers need 22 not acquire any locks, perform any atomic instructions, write to 23 shared memory, or (on CPUs other than Alpha) execute any memory 25 on modern CPUs is what gives RCU its performance advantages [all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | func-select.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 4 .. _func-select: 13 v4l2-select - Synchronous I/O multiplexing 18 .. code-block:: c 30 The highest-numbered file descriptor in any of the three sets, plus 1. 36 File descriptions to be watched if a write() won't block. 42 Maximum time to wait. 56 On success :c:func:`select()` returns the total number of bits set in 58 a value of zero. On failure it returns -1 and the ``errno`` variable is 75 When use of the :c:func:`write()` function has been negotiated the [all …]
|
| D | func-poll.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 4 .. _func-poll: 13 v4l2-poll - Wait for some event on a file descriptor 18 .. code-block:: c 44 On success :c:func:`poll()` returns the number of file descriptors 47 is non-zero). Capture devices set the ``POLLIN`` and ``POLLRDNORM`` 50 zero, on failure it returns -1 and the ``errno`` variable is set 73 When use of the :c:func:`write()` function has been negotiated and the 76 it waits until the driver is ready for a non-blocking 77 :c:func:`write()` call. [all …]
|
| /Documentation/filesystems/xfs/ |
| D | xfs-delayed-logging-design.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 subsystem is based on. This document describes the design and algorithms that 12 the XFS journalling subsystem is based on so that readers may familiarize 26 XFS uses Write Ahead Logging for ensuring changes to the filesystem metadata 33 details logged are made up of the changes to in-core structures rather than 34 on-disk structures. Other objects - typically buffers - have their physical 49 together are different and are dependent on the object and/or modification being 64 place. This means that permanent transactions can be used for one-shot 65 modifications, but one-shot reservations cannot be used for permanent 68 In the code, a one-shot transaction pattern looks somewhat like this:: [all …]
|
| /Documentation/usb/ |
| D | raw-gadget.rst | 5 USB Raw Gadget is a gadget driver that gives userspace low-level control over 24 GadgetFS responds to some USB requests internally based on the provided 25 descriptors. Note that the UDC driver might respond to some requests on 29 while GadgetFS performs sanity checks on the provided USB descriptors. 38 capabilities. This allows the user to write UDC-agnostic gadgets. 40 5. Raw Gadget has an ioctl-based interface instead of a filesystem-based 46 The user can interact with Raw Gadget by opening ``/dev/raw-gadget`` and 53 1. Create a Raw Gadget instance by opening ``/dev/raw-gadget``. 57 Raw Gadget and react to those depending on what kind of USB gadget must 62 Nevertheless, Raw Gadget provides a UDC-agnostic way to write USB gadgets. [all …]
|
| /Documentation/admin-guide/ |
| D | ext4.rst | 1 .. SPDX-License-Identifier: GPL-2.0 9 (64 bit) in keeping with increasing disk capacities and state-of-the-art 12 Mailing list: linux-ext4@vger.kernel.org 23 - The latest version of e2fsprogs can be found at: 35 - Create a new filesystem using the ext4 filesystem type: 37 # mke2fs -t ext4 /dev/hda1 41 # tune2fs -O extents /dev/hda1 46 # tune2fs -I 256 /dev/hda1 48 - Mounting: 50 # mount -t ext4 /dev/hda1 /wherever [all …]
|
| /Documentation/driver-api/media/drivers/ |
| D | radiotrack.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 ---------------- 13 This document was made based on 'C' code for Linux from Gideon le Grange 16 experiments that the author performed on his own setup, so your mileage may 18 validity of this information. No other documentation on the AIMS 24 ------------------ 26 I have a RadioTrack card from back when I ran an MS-Windows platform. After 27 converting to Linux, I found Gideon le Grange's command-line software for 29 comfortable X-windows interface, and added a scanning feature. For hack 32 broadcast TV channels, situated just below and above the 87.0-109.0 MHz range. [all …]
|
| /Documentation/ABI/testing/ |
| D | debugfs-hisi-hpre | 1 What: /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/regs 3 Contact: linux-crypto@vger.kernel.org 7 What: /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/cluster_ctrl 9 Contact: linux-crypto@vger.kernel.org 10 Description: Write the HPRE core selection in the cluster into this file, 16 Contact: linux-crypto@vger.kernel.org 25 Contact: linux-crypto@vger.kernel.org 32 Contact: linux-crypto@vger.kernel.org 35 supports to write <bdf> value to alg_qos in the host. Such as 42 Contact: linux-crypto@vger.kernel.org [all …]
|
| D | sysfs-driver-w1_therm | 5 (RW) read or write TH and TL (Temperature High an Low) alarms. 7 (typical -55 degC to 125 degC), if not values will be trimmed 11 master level, refer to Documentation/w1/w1-generic.rst for 41 * '-xx': xx is kernel error when reading power status 51 (RW) get or set the device resolution (on supported devices, 55 values after power-on. Read or write are : 59 * '-xx': xx is kernel error when reading the resolution 62 Some DS18B20 clones are fixed in 12-bit resolution, so the 79 should retry later on. 82 conversion duration depend on the resolution (if [all …]
|
| /Documentation/iio/ |
| D | iio_devbuf.rst | 1 .. SPDX-License-Identifier: GPL-2.0 10 The Industrial I/O core offers a way for continuous data capture based on a 14 Devices with buffer support feature an additional sub-directory in the 25 ---------- 27 Read / Write attribute which states the total number of data samples (capacity) 31 ---------- 33 Read / Write attribute which starts / stops the buffer capture. This file should 34 be written last, after length and selection of scan elements. Writing a non-zero 39 ------------- 41 Read / Write positive integer attribute specifying the maximum number of scan [all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | vdo-design.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only 4 Design of dm-vdo 7 The dm-vdo (virtual data optimizer) target provides inline deduplication, 8 compression, zero-block elimination, and thin provisioning. A dm-vdo target 12 production environments ever since. It was made open-source in 2017 after 14 dm-vdo. For usage, see vdo.rst in the same directory as this file. 25 The design of dm-vdo is based on the idea that deduplication is a two-part 27 storing multiple copies of those duplicates. Therefore, dm-vdo has two main 34 ------------------- 37 structures involved in a single write operation to a vdo target is larger [all …]
|
| /Documentation/networking/ |
| D | iso15765-2.rst | 1 .. SPDX-License-Identifier: (GPL-2.0 OR BSD-3-Clause) 4 ISO 15765-2 (ISO-TP) 10 ISO 15765-2, also known as ISO-TP, is a transport protocol specifically defined 11 for diagnostic communication on CAN. It is widely used in the automotive 12 industry, for example as the transport protocol for UDSonCAN (ISO 14229-3) or 13 emission-related diagnostic services (ISO 15031-5). 15 ISO-TP can be used both on CAN CC (aka Classical CAN) and CAN FD (CAN with 21 ------------------- 23 * ISO 15765-2:2024 : Road vehicles - Diagnostic communication over Controller 27 ---------- [all …]
|
| /Documentation/locking/ |
| D | lockstat.rst | 8 As the name suggests, it provides statistics on locks. 20 lock classes. We build on that (see Documentation/locking/lockdep-design.rst). 30 | <wait> 44 lock, unlock - the regular lock functions 45 __* - the hooks 46 <> - states 50 con-bounces 51 - number of lock contention that involved x-cpu data 53 - number of lock acquisitions that had to wait 54 wait time [all …]
|
1234567