Searched +full:sync +full:- +full:read (Results 1 – 25 of 113) sorted by relevance
12345
| /Documentation/sound/cards/ |
| D | hdspm.rst | 2 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/driver-api/memory-devices/ |
| D | ti-gpmc.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 * Pseudo-SRAM devices
65 2. sync common
74 3. read async muxed
85 4. read async non-muxed
96 5. read sync muxed
107 6. read sync non-muxed
131 8. write async non-muxed
144 9. write sync muxed
157 10. write sync non-muxed
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | blkio-controller.rst | 22 -----------------------------
33 mount -t cgroup -o blkio none /sys/fs/cgroup/blkio
43 Run dd to read a file and see if rate is throttled to 1MB/s or not::
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
[all …]
|
| /Documentation/litmus-tests/rcu/ |
| D | RCU+sync+read.litmus | 1 C RCU+sync+read
7 * sees all stores done in prior RCU read-side critical sections. Such
8 * read-side critical sections would have ended before the grace period ended.
10 * This is one implication of the RCU grace-period guarantee, which says (among
11 * other things) that an RCU read-side critical section cannot span a grace period.
|
| D | RCU+sync+free.litmus | 1 C RCU+sync+free
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/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 | mvebu-devbus.txt | 9 - 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
35 Read parameters:
[all …]
|
| /Documentation/litmus-tests/ |
| D | README | 9 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/userspace-api/media/v4l/ |
| D | vidioc-g-dv-timings.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_G_DV_TIMINGS - VIDIOC_S_DV_TIMINGS - VIDIOC_SUBDEV_G_DV_TIMINGS - VIDIOC_SUBDEV_S_DV_TIMINGS…
56 registered in read-only mode is not allowed. An error is returned and the errno
57 variable is set to ``-EPERM``.
59 The ``linux/v4l2-dv-timings.h`` header can be used to get the timings of
68 On success 0 is returned, on error -1 and the ``errno`` variable is set
70 :ref:`Generic Error Codes <gen-errors>` chapter.
83 ``VIDIOC_SUBDEV_S_DV_TIMINGS`` has been called on a read-only subdevice.
91 .. flat-table:: struct v4l2_bt_timings
92 :header-rows: 0
[all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | gpio-control-nand.txt | 4 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
21 read registers (tR). If not present then a default of 20us is used.
22 - gpio-control-nand,io-sync-reg : A 64-bit physical address for a read
26 read to ensure that the GPIO accesses have completed.
[all …]
|
| /Documentation/devicetree/bindings/cache/ |
| D | l2c2x0.yaml | 1 # 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/fb/ |
| D | api.rst | 9 ---------------
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
58 - FB_TYPE_PACKED_PIXELS
67 - FB_TYPE_PLANES
75 - FB_TYPE_INTERLEAVED_PLANES
86 - FB_TYPE_FOURCC
[all …]
|
| D | framebuffer.rst | 9 ---------------
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/devicetree/bindings/net/ |
| D | broadcom-bcm87xx.txt | 5 "ethernet-phy-ieee802.3-c45"
9 - broadcom,c45-reg-init : one of more sets of 4 cells. The first cell
14 value of zero, no read of the existing value is performed.
18 ethernet-phy@5 {
20 compatible = "broadcom,bcm8706", "ethernet-phy-ieee802.3-c45";
21 interrupt-parent = <&gpio>;
26 * GPIO[0] R64 Sync Acquired
28 broadcom,c45-reg-init = <1 0xc808 0xff8f 0x70>;
|
| /Documentation/gpu/amdgpu/display/ |
| D | dcn-overview.rst | 10 .. 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.
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
79 that HUBP accesses a surface using a specific format read from memory, and our
84 ----------------------
100 a one-to-one mapping of the link encoder to PHY, but we can configure the DCN
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-raid.rst | 2 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 …]
|
| D | dm-io.rst | 2 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/driver-api/ |
| D | rfkill.rst | 2 rfkill - RF kill switch support
25 - hard block
26 read-only radio block that cannot be overridden by software
28 - soft block
34 admin-guide/kernel-parameters.rst.
43 * the deprecated rfkill-input module (an input layer handler, being
49 the system know about hardware-disabled states that may be implemented on
56 When the device is hard-blocked (either by a call to rfkill_set_hw_state()
59 value of the function rfkill_set_hw_state() to sync the software state
83 to ensure the driver cannot be built-in when rfkill is modular. The !RFKILL
[all …]
|
| /Documentation/gpu/rfc/ |
| D | i915_vm_bind.rst | 18 User has to opt-in for VM_BIND mode of binding for an address space (VM)
34 ------------------------
42 -------------------------------
48 execlist. Hence, no support for implicit sync. It is expected that the below
52 "dma-buf: Add an API for exporting sync files"
68 be using the i915_vma active reference tracking. It will instead use dma-resv
72 evictions, vma lookup table, implicit sync, vma active reference tracking etc.,
78 -------------------
79 By default, BOs can be mapped on multiple VMs and can also be dma-buf
82 dma-resv fence list of all shared BOs mapped on the VM.
[all …]
|
| /Documentation/admin-guide/ |
| D | sysrq.rst | 22 - 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/filesystems/ext4/ |
| D | allocators.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ---------------------------------
17 The first tool that ext4 uses to combat fragmentation is the multi-block
23 files) then the file data gets written out in a single multi-block
29 is hit, or sync() is called, or the kernel runs out of memory), the hope
34 on the seek penalty when the filesystem first has to read a file's inode
44 groups; these mini-containers are used as outlined above to try to
45 maintain data locality. However, there is a deliberate quirk -- when a
49 over a disk; as the top-level directory/file blobs fill up one block
53 the end of a spinning drive get a raw deal performance-wise.
|
| /Documentation/scsi/ |
| D | ChangeLog.ips | 4 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/bpf/libbpf/ |
| D | libbpf_overview.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 libbpf is a C-based library containing a BPF loader that takes compiled BPF
13 The following are the high-level features supported by libbpf:
15 * Provides high-level and low-level APIs for user space programs to interact
16 with BPF programs. The low-level APIs wrap all the bpf system call
17 functionality, which is useful when users need more fine-grained control
22 * Provides BPF-side APIS, including BPF helper definitions, BPF maps support,
24 * Supports BPF CO-RE mechanism, enabling BPF developers to write portable
48 (setting BPF program types, if necessary; pre-setting initial values for
62 packets, or updating BPF maps and global variables that can be read from user
[all …]
|
| /Documentation/input/devices/ |
| D | cma3000_d0x.rst | 1 CMA3000-D0x Accelerometer
5 * VTI CMA3000-D0x
8 CMA3000-D0X Product Family Specification 8281000A.02.pdf
15 -----------
17 CMA3000 Tri-axis accelerometer supports Motion detect, Measurement and
25 This mode is used to read the acceleration data on X,Y,Z
47 -------------
74 ---------------
78 Input device name: "cma3000-accelerometer"
82 Event type 0 (Sync)
[all …]
|
| /Documentation/networking/ |
| D | tls-offload.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
13 For details regarding the user-facing interface refer to the TLS
18 * Software crypto mode (``TLS_SW``) - CPU handles the cryptography.
22 latency on socket reads (decryption only starts when a read syscall
24 * Packet-based NIC offload mode (``TLS_HW``) - the NIC handles crypto
28 (``ethtool`` flags ``tls-hw-tx-offload`` and ``tls-hw-rx-offload``).
29 * Full TCP NIC offload mode (``TLS_HW_RECORD``) - mode of operation where
33 abilities or QoS and packet scheduling (``ethtool`` flag ``tls-hw-record``).
36 offload opt-in or opt-out on per-connection basis is not currently supported.
39 --
[all …]
|
12345