Home
last modified time | relevance | path

Searched +full:sync +full:- +full:write (Results 1 – 25 of 107) sorted by relevance

12345

/Documentation/driver-api/memory-devices/
Dti-gpmc.rst1 .. SPDX-License-Identifier: GPL-2.0
14 * Pseudo-SRAM devices
65 2. sync common
85 4. read async non-muxed
96 5. read sync muxed
107 6. read sync non-muxed
118 7. write async muxed
131 8. write async non-muxed
144 9. write sync muxed
157 10. write sync non-muxed
/Documentation/sound/cards/
Dhdspm.rst2 Software Interface ALSA-DSP MADI Driver
5 (translated from German, so no good English ;-),
7 2004 - winfried ritsch
11 the Controls and startup-options are ALSA-Standard and only the
19 ------------------
21 * number of channels -- depends on transmission mode
29 * Single Speed -- 1..64 channels
37 * Double Speed -- 1..32 channels
40 Note: Choosing the 56-channel mode for
41 transmission/receive-mode , only 28 are transmitted/received
[all …]
/Documentation/admin-guide/cgroup-v1/
Dblkio-controller.rst22 -----------------------------
33 mount -t cgroup -o blkio none /sys/fs/cgroup/blkio
98 --------------------------------
106 see Documentation/block/bfq-iosched.rst.
110 weight. For more details, see Documentation/block/bfq-iosched.rst.
152 are further divided by the type of operation - read or write, sync
159 are further divided by the type of operation - read or write, sync
173 the type of operation - read or write, sync or async. First two fields
186 (there might be a time lag here due to re-ordering of requests by the
188 devices too. This time is further divided by the type of operation -
[all …]
/Documentation/devicetree/bindings/memory-controllers/
Dti,gpmc-child.yaml1 # 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 …]
Dmvebu-devbus.txt9 - compatible: Armada 370/XP SoC are supported using the
10 "marvell,mvebu-devbus" compatible string.
13 "marvell,orion-devbus" compatible string.
15 - reg: A resource specifier for the register space.
20 - #address-cells: Must be set to 1
21 - #size-cells: Must be set to 1
22 - ranges: Must be set up to reflect the memory layout with four
23 integer values for each chip-select line in use:
28 - devbus,keep-config This property can optionally be used to keep
37 - devbus,turn-off-ps: Defines the time during which the controller does not
[all …]
/Documentation/litmus-tests/rcu/
DRCU+sync+free.litmus1 C RCU+sync+free
6 * This litmus test demonstrates that an RCU reader can never see a write that
10 * This is a typical pattern of RCU usage, where the write before the grace
14 * This is one implication of the RCU grace-period guarantee, which says (among
15 * other things) that an RCU read-side critical section cannot span a grace period.
/Documentation/devicetree/bindings/cache/
Dl2c2x0.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
16 models (Note 1). Some of the properties that are just prefixed "cache-*" are
22 cache controllers as found in e.g. Cortex-A15/A7/A57/A53. These
28 - $ref: /schemas/cache-controller.yaml#
33 - enum:
34 - arm,pl310-cache
35 - arm,l220-cache
[all …]
/Documentation/filesystems/
Dqnx6.rst1 .. SPDX-License-Identifier: GPL-2.0
29 ------
39 ---------------
44 In write mode with reach new snapshot (after each synchronous write), the
49 are done by copying all modified blocks during that specific write request
65 Unused block pointers are always set to ~0 - regardless of root node,
79 0x1000 is the size reserved for each superblock - regardless of the
83 ------
104 -----------
125 -------------
[all …]
/Documentation/admin-guide/device-mapper/
Ddm-raid.rst2 dm-raid
5 The device-mapper RAID (dm-raid) target provides a bridge from DM to MD.
6 It allows the MD RAID drivers to be accessed using a device-mapper
11 -----------------------
26 - Transitory layout
29 - rotating parity 0 with data continuation
32 - rotating parity N with data continuation
35 - rotating parity 0 with data restart
38 - rotating parity N with data restart
41 - rotating parity zero (left-to-right) with data restart
[all …]
Ddm-io.rst2 dm-io
5 Dm-io provides synchronous and asynchronous I/O services. There are three
6 types of I/O services available, and each type has a sync and an async
10 of the I/O. Each io_region indicates a block-device along with the starting
19 Dm-io can read from one io_region or write to one or more io_regions. Writes
38 for the I/O. This service can be handy if the caller has a pre-assembled bio,
65 In the case of an write-I/O to multiple regions, this bitset allows dm-io to
68 Before using any of the dm-io services, the user should call dm_io_get()
70 Dm-io will attempt to resize its mempool to make sure enough pages are
73 When the user is finished using the dm-io services, they should call
/Documentation/litmus-tests/
DREADME9 tools/memory-model/README.
13 --------------------------
15 Atomic-RMW+mb__after_atomic-is-stronger-than-acquire.litmus
17 stronger than a normal acquire: both the read and write parts of
20 Atomic-RMW-ops-are-atomic-WRT-atomic_set.litmus
24 cmpxchg-fail-ordered-1.litmus
28 cmpxchg-fail-ordered-2.litmus
32 cmpxchg-fail-unordered-1.litmus
36 cmpxchg-fail-unordered-2.litmus
42 ----------------------------
[all …]
/Documentation/fb/
Dsh7760fb.rst6 -----------
29 - drivers/video/sh7760fb.c
30 - include/asm-sh/sh7760fb.h
31 - Documentation/fb/sh7760fb.rst
34 -----------------
37 configure the SH DMAC for DMABRG mode (write 0x94808080 to the
41 (write zeros to both).
47 --------------------
62 * NEC NL6440bc26-01 640x480 TFT
72 * panel sync timings.
[all …]
Dapi.rst9 ---------------
12 with frame buffer devices. In-kernel APIs between device drivers and the frame
22 ---------------
36 - FB_CAP_FOURCC
44 --------------------
46 Pixels are stored in memory in hardware-dependent formats. Applications need
47 to be aware of the pixel storage format in order to write image data to the
58 - FB_TYPE_PACKED_PIXELS
67 - FB_TYPE_PLANES
75 - FB_TYPE_INTERLEAVED_PLANES
[all …]
Dframebuffer.rst9 ---------------
13 software to access the graphics hardware through a well-defined interface, so
14 the software doesn't need to know anything about the low-level (hardware
22 --------------------------
39 /dev/fb0current -> fb0
40 /dev/fb1current -> fb1
45 read and write their contents. You can, for example, make a screen snapshot by::
50 graphics card in addition to the built-in hardware. The corresponding frame
69 --------------------------------
72 it has the same features. You can read it, write it, seek to some location in
[all …]
/Documentation/gpu/amdgpu/display/
Ddcn-overview.rst10 .. kernel-figure:: dc_pipeline_overview.svg
19 * **Display Pipe and Plane (DPP)**: This block provides pre-blend pixel
24 multiple planes, using global or per-pixel alpha.
35 * **Display Writeback (DWB)**: It provides the ability to write the output of
38 * **Multi-Media HUB (MMHUBBUB)**: Memory controller interface for DMCUB and DWB
43 the Display Micro-Controller Unit - version B (DMCUB), which is handled via
67 2. Global sync signals (green): It is a set of synchronization signals composed
73 the Global Sync deserves an extra level of detail described in the next
84 ----------------------
100 a one-to-one mapping of the link encoder to PHY, but we can configure the DCN
[all …]
/Documentation/block/
Dwriteback_cache_control.rst2 Explicit volatile write back cache control
6 ------------
9 write back caches. That means the devices signal I/O completion to the
10 operating system before data actually has hit the non-volatile storage. This
12 system needs to force data out to the non-volatile storage when it performs
13 a data integrity operation like fsync, sync or an unmount.
21 ----------------------
26 guarantees that previously completed write requests are on non-volatile
34 ------------------
38 signaled after the data has been committed to non-volatile storage.
[all …]
/Documentation/arch/x86/
Dpat.rst1 .. SPDX-License-Identifier: GPL-2.0
20 WB Write-back
22 WC Write-combined
23 WT Write-through
24 UC- Uncached Minus
38 +------------------------+----------+--------------+------------------+
40 +------------------------+----------+--------------+------------------+
41 | ioremap | -- | UC- | UC- |
42 +------------------------+----------+--------------+------------------+
43 | ioremap_cache | -- | WB | WB |
[all …]
/Documentation/devicetree/bindings/mtd/
Dgpio-control-nand.txt4 read/write the NAND commands and data and GPIO pins for the control
8 - compatible : "gpio-control-nand"
9 - reg : should specify localbus chip select and size used for the chip. The
12 - #address-cells, #size-cells : Must be present if the device has sub-nodes
14 - gpios : Specifies the GPIO pins to control the NAND device. The order of
18 - bank-width : Width (in bytes) of the device. If not present, the width
20 - chip-delay : chip dependent delay for transferring data from array to
22 - gpio-control-nand,io-sync-reg : A 64-bit physical address for a read
28 The device tree may optionally contain sub-nodes describing partitions of the
33 gpio-nand@1,0 {
[all …]
/Documentation/virt/kvm/devices/
Dxive.rst1 .. SPDX-License-Identifier: GPL-2.0
8 - KVM_DEV_TYPE_XIVE POWER9 XIVE Interrupt Controller generation 1
32 - Interrupt Pending Buffer (IPB)
33 - Current Processor Priority (CPPR)
34 - Notification Source Register (NSR)
49 3. Device pass-through
51 When a device is passed-through into the guest, the source
61 interrupt of the device being passed-through or the initial IPI ESB
66 helpers in KVM-PPC.
74 1.1 KVM_DEV_XIVE_RESET (write only)
[all …]
/Documentation/accounting/
Ddelay-accounting.rst9 The per-task delay accounting functionality measures
18 g) write-protect copy
40 ---------
44 generic data structure to userspace corresponding to per-pid and per-tgid
52 delay seen for cpu, sync block I/O, swapin, memory reclaim, thrash page
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
70 -----
96 getdelays [-dilv] [-t tgid] [-p pid]
[all …]
/Documentation/admin-guide/blockdev/drbd/
Ddrbd-connection-state-overview.dot39 label="new application (WRITE?) requests blocked\lwhile bitmap is exchanged"
58 // --------------------------------------
60 StandAlone -> Unconnected [ label="drbdadm connect" ]
61 Unconnected -> StandAlone [ label="drbdadm disconnect\lor serious communication trouble" ]
62 Unconnected -> WFConnection [ label="receiver thread is started" ]
63 …WFConnection -> WFReportParams [ headlabel="accept()\land/or \lconnect()\l"…
65 …WFReportParams -> StandAlone [ label="during handshake\lpeers do not agree\labout something essent…
66 WFReportParams -> Connected [ label="data identical\lno sync needed",color=green,fontcolor=green ]
68 WFReportParams -> WFBitMapS
69 WFReportParams -> WFBitMapT
[all …]
/Documentation/admin-guide/
Dmd.rst5 ---------------------------------
49 -1 linear mode
58 (raid-0 and raid-1 only)
78 --------------------------------------
87 that all auto-detected arrays are assembled as partitionable.
90 -------------------------------------------
102 mdadm --assemble --force ....
112 md-mod.start_dirty_degraded=1
116 ------------------
119 Currently, it supports superblock formats ``0.90.0`` and the ``md-1`` format
[all …]
Dsysrq.rst22 - 0 - disable sysrq completely
23 - 1 - enable all functions of sysrq
24 - >1 - bitmask of allowed sysrq functions (see below for detailed function
27 2 = 0x2 - enable control of console logging level
28 4 = 0x4 - enable control of keyboard (SAK, unraw)
29 8 = 0x8 - enable debugging dumps of processes etc.
30 16 = 0x10 - enable sync command
31 32 = 0x20 - enable remount read-only
32 64 = 0x40 - enable signalling of processes (term, kill, oom-kill)
33 128 = 0x80 - allow reboot/poweroff
[all …]
/Documentation/scsi/
DChangeLog.ips4 5.00.01 - Sarasota ( 5i ) adapters must always be scanned first
5 - Get rid on IOCTL_NEW_COMMAND code
6 - Add Extended DCDB Commands for Tape Support in 5I
8 4.90.11 - Don't actually RESET unless it's physically required
9 - Remove unused compile options
11 4.90.08 - Data Corruption if First Scatter Gather Element is > 64K
13 4.90.08 - Increase Delays in Flashing ( Trombone Only - 4H )
15 4.90.05 - Use New PCI Architecture to facilitate Hot Plug Development
17 4.90.01 - Add ServeRAID Version Checking
19 4.80.26 - Clean up potential code problems ( Arjan's recommendations )
[all …]
/Documentation/input/devices/
Dyealink.rst2 Driver documentation for yealink usb-p1k phones
10 - keyboard full support, yealink.ko / input event API
11 - LCD full support, yealink.ko / sysfs API
12 - LED full support, yealink.ko / sysfs API
13 - dialtone full support, yealink.ko / sysfs API
14 - ringtone full support, yealink.ko / sysfs API
15 - audio playback full support, snd_usb_audio.ko / alsa API
16 - audio record full support, snd_usb_audio.ko / alsa API
27 Physical USB-P1K button layout input events
93 line1 Read/Write, lcd line1
[all …]

12345