Searched full:volume (Results 1 – 25 of 155) sorted by relevance
1234567
| /Documentation/ABI/testing/ |
| D | configfs-usb-gadget-uac1 | 12 c_volume_present capture volume control enable
13 c_volume_min capture volume control min value
15 c_volume_max capture volume control max value
17 c_volume_res capture volume control resolution
23 p_volume_present playback volume control enable
24 p_volume_min playback volume control min value
26 p_volume_max playback volume control max value
28 p_volume_res playback volume control resolution
36 p_fu_vol_name playback mute/volume functional unit name
40 c_fu_vol_name capture mute/volume functional unit name
|
| D | configfs-usb-gadget-uac2 | 15 c_volume_present capture volume control enable
16 c_volume_min capture volume control min value
18 c_volume_max capture volume control max value
20 c_volume_res capture volume control resolution
28 p_volume_present playback volume control enable
29 p_volume_min playback volume control min value
31 p_volume_max playback volume control max value
33 p_volume_res playback volume control resolution
44 p_fu_vol_name playback mute/volume function unit name
48 c_fu_vol_name capture mute/volume functional unit name
|
| D | sysfs-fs-nilfs2 | 20 Show NILFS file system revision on volume.
22 revision on mounted volume.
28 Show volume's block size in bytes.
34 Show volume size in bytes.
40 Show count of free blocks on volume.
46 Show volume's UUID (Universally Unique Identifier).
52 Show volume's label.
187 Show number of segments on a volume.
218 Show number of checkpoints on volume.
224 Show number of snapshots on volume.
|
| /Documentation/ABI/stable/ |
| D | sysfs-class-ubi | 8 and per-UBI volume information.
30 device information and per UBI volume information (each UBI
39 create a new UBI volume which has this amount of logical
148 Volume alignment - the value the logical eraseblock size of
149 this volume has to be aligned on. For example, 2048 means that
151 volume logical eraseblock size is UBI device logical eraseblock
159 Contains ASCII "0\n" if the UBI volume is OK, and ASCII "1\n"
160 if it is corrupted (e.g., due to an interrupted volume update).
167 The amount of data this volume contains. This value makes sense
168 only for static volumes, and for dynamic volume it equivalent
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | vdo.rst | 17 Formatting a vdo volume requires the use of the 'vdoformat' tool, available
40 Each vdo volume reserves 3GB of space for metadata, or more depending on
64 The offset, in sectors, at which the vdo volume's logical
68 The size of the device which the vdo volume will service,
70 volume.
73 The device holding the vdo volume's data and metadata.
76 The size of the device holding the vdo volume, as a number
78 volume.
81 The minimum I/O size for this vdo volume to accept, in
115 outside the vdo volume, threads of this type allow the vdo
[all …]
|
| D | thin-provisioning.rst | 13 be stored on the same data volume. This simplifies administration and
27 - Improve metadata resilience by storing metadata on a mirrored volume
37 to fragmentation of the data volume.
53 directly. End users will be advised to use a higher-level volume
59 The pool device ties together the metadata volume and the data volume.
60 It maps I/O linearly to the data volume and updates the metadata via
160 i) Creating a new thinly-provisioned volume.
162 To create a new thinly- provisioned volume you must send a message to an
167 Here '0' is an identifier for the volume, a 24-bit number. It's up
171 ii) Using a thinly-provisioned volume.
[all …]
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | ubi-volume.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/ubi-volume.yaml#
7 title: UBI volume
10 This binding describes a single UBI volume. Volumes can be matches either
20 Match UBI volume ID
25 Match UBI volume ID
|
| D | linux,ubi.yaml | 10 UBI ("Unsorted Block Images") is a volume management system for raw
30 "^ubi-volume-.*$":
31 $ref: /schemas/mtd/partitions/ubi-volume.yaml#
59 ubi-volume-caldata {
|
| /Documentation/filesystems/caching/ |
| D | netfs-api.rst | 30 (2) Volume registration
48 cookie, hereafter referred to as "volume cookies" and "cookies".
50 A network filesystem acquires a volume cookie for a volume using a volume key,
51 which represents all the information that defines that volume (e.g. cell name
52 or server address, volume ID or share name). This must be rendered as a
58 A filesystem would typically have a volume cookie for each superblock.
60 The filesystem then acquires a cookie for each file within that volume using an
62 their parent volume. The cache backend is responsible for rendering the binary
91 Volume Registration
94 The first step for a network filesystem is to acquire a volume cookie for the
[all …]
|
| D | backend-api.rst | 17 Interaction with the API is handled on three levels: cache, volume and data
24 Volume cookie struct fscache_volume
35 and if they ask for one of the same name, they'll get the same cookie. Volume
103 volume-level accesses from starting and then waits for outstanding cache-level
120 void fscache_withdraw_volume(struct fscache_volume *volume);
122 to tell fscache that a volume has been withdrawn. This waits for all
123 outstanding accesses on the volume to complete before returning.
133 Volume Cookies
159 the index key for the volume. The key is NUL-terminated and padded out to
166 volume is bound to in the cache.
[all …]
|
| D | fscache.rst | 104 * There are three types of cookie: cache, volume and data file cookies.
106 to the netfs; the netfs gets a volume cookie to represent a collection of
114 cell name or server address, volume name or share path. It must be a
118 represent the object within a volume (so the volume key need not form
172 | |v=N |Number of volume index cookies allocated |
174 | |vcol=N |Number of volume index key collisions |
176 | |voom=N |Number of OOM events when allocating volume cookies |
253 Volume List
256 FS-Cache provides a list of volume cookies:
262 VOLUME REF nCOOK ACC FL CACHE KEY
[all …]
|
| /Documentation/admin-guide/ |
| D | jfs.rst | 19 Resize the volume to <value> blocks. JFS only supports
20 growing a volume, not shrinking it. This option is only
21 valid during a remount, when the volume is mounted
23 the volume to the full size of the partition.
27 is to allow for higher performance when restoring a volume
28 from backup media. The integrity of the volume is not
33 remount a volume where the nointegrity option was
|
| /Documentation/sound/cards/ |
| D | audigy-mixer.rst | 47 name='PCM Front Playback Volume',index=0
53 name='PCM Surround Playback Volume',index=0
60 name='PCM Side Playback Volume',index=0
66 name='PCM Center Playback Volume',index=0
72 name='PCM LFE Playback Volume',index=0
78 name='PCM Playback Volume',index=0
84 name='PCM Capture Volume',index=0
90 name='Music Playback Volume',index=0
96 name='Music Capture Volume',index=0
102 name='Mic Playback Volume',index=0
[all …]
|
| D | sb-live-mixer.rst | 62 ``name='Wave Playback Volume',index=0``
68 ``name='Wave Surround Playback Volume',index=0``
75 ``name='Wave Center Playback Volume',index=0``
82 ``name='Wave LFE Playback Volume',index=0``
89 ``name='Wave Capture Volume',index=0``, ``name='Wave Capture Switch',index=0``
96 ``name='Synth Playback Volume',index=0``
102 ``name='Synth Capture Volume',index=0``, ``name='Synth Capture Switch',index=0``
109 ``name='Surround Playback Volume',index=0``
116 ``name='Surround Capture Volume',index=0``, ``name='Surround Capture Switch',index=0``
123 ``name='Center Playback Volume',index=0``
[all …]
|
| D | emu-mixer.rst | 98 name='PCM Front Playback Volume',index=0
105 name='PCM Surround Playback Volume',index=0
112 name='PCM Side Playback Volume',index=0
119 name='PCM Center Playback Volume',index=0
125 name='PCM LFE Playback Volume',index=0
131 name='PCM Playback Volume',index=0
137 name='PCM Capture Volume',index=0
143 name='Music Playback Volume',index=0
149 name='Music Capture Volume',index=0
155 name='Front Playback Volume',index=0
[all …]
|
| D | mixart.rst | 55 analog volume control of playback and capture PCM.
57 digital volume control of each analog substream.
59 digital volume control of each AES/EBU substream.
61 Loopback from 'pcm0c' to 'pcm0p' with digital volume
65 and AES volume controls which is set by 219 in the range from 0 to 255
|
| /Documentation/filesystems/ |
| D | afs.rst | 65 list of volume location server IP addresses::
84 volume location servers within that cell, with the latter separated by colons.
94 whether you definitely want a R/W volume (percent) or whether you'd prefer a
95 R/O volume, but are willing to use a R/W volume instead (hash).
97 The name of the volume can be suffixes with ".backup" or ".readonly" to
101 named volume will be looked up in the cell specified during modprobe.
113 automatically cause the target volume to be mounted (if possible) on that site.
119 Manually unmounting an AFS volume will cause any idle submounts upon it to be
120 culled first. If all are culled, then the requested volume will also be
156 (*) A directory per cell that contains files that list volume location
[all …]
|
| D | ubifs.rst | 42 found in drivers/mtd/ubi. UBI is basically a volume management and
114 The UBI volume to mount is specified using "ubiX_Y" or "ubiX:NAME" syntax,
115 where "X" is UBI device number, "Y" is UBI volume number, and "NAME" is
116 UBI volume name.
118 Mount volume 0 on UBI device 0 to /mnt/ubifs::
122 Mount "rootfs" volume of UBI device 0 to /mnt/ubifs ("rootfs" is volume
128 to UBI and mount volume "rootfs":
|
| /Documentation/sound/designs/ |
| D | oss-emulation.rst | 227 string. For example, the volume element SOUND_MIXER_PCM is composed
228 from "PCM Playback Volume" and "PCM Playback Switch" controls for the
229 playback direction and from "PCM Capture Volume" and "PCM Capture
230 Switch" for the capture directory (if exists). When the PCM volume of
231 OSS is changed, all the volume and switch controls above are adjusted
237 OSS volume ALSA control Index
268 [Volume|Switch]`` will be checked in addition.
274 VOLUME "Master" 0
281 where the first column is the OSS volume element, the second column
287 proc file. For example, to map "Wave Playback" to the PCM volume,
[all …]
|
| D | control-names.rst | 26 Volume amplifier
103 [Analogue|Digital] Capture Volume aka input gain volume
105 [Analogue|Digital] Playback Volume aka output gain volume
133 IEC958 [...] [Playback|Capture] Volume digital volume control
|
| /Documentation/devicetree/bindings/sound/ |
| D | rt5663.txt | 31 minimum, impedance maximum, volume, DC offset w/o and w/ mic of each L and
36 detected impedance value is in the range, then the volume value of the
37 third column will be set to codec. In our codec design, each volume value
|
| D | nvidia,tegra210-mvc.yaml | 10 The Master Volume Control (MVC) provides gain or attenuation to a digital
12 volume control or it can be used as master volume control. The MVC block
|
| /Documentation/driver-api/media/drivers/ |
| D | radiotrack.rst | 79 0 1 volume + (some delay required)
80 1 0 volume - (some delay required)
81 1 1 stay at present volume
129 Default: BASE <-- 0xc8 (current volume, no stereo detect,
138 Volume Down: BASE <-- 0x48 (volume down, no stereo detect,
143 Volume Up: BASE <-- 0x88 (volume up, no stereo detect,
148 Check Stereo: BASE <-- 0xd8 (current volume, stereo detect,
|
| /Documentation/arch/riscv/ |
| D | hwprobe.rst | 128 defined in version 1.0 of the RISC-V Cryptography Extensions Volume II.
131 defined in version 1.0 of the RISC-V Cryptography Extensions Volume II.
134 defined in version 1.0 of the RISC-V Cryptography Extensions Volume II.
137 defined in version 1.0 of the RISC-V Cryptography Extensions Volume II.
140 defined in version 1.0 of the RISC-V Cryptography Extensions Volume II.
143 defined in version 1.0 of the RISC-V Cryptography Extensions Volume II.
146 defined in version 1.0 of the RISC-V Cryptography Extensions Volume II.
149 defined in version 1.0 of the RISC-V Cryptography Extensions Volume II.
152 defined in version 1.0 of the RISC-V Cryptography Extensions Volume II.
155 defined in version 1.0 of the RISC-V Cryptography Extensions Volume II.
|
| /Documentation/userspace-api/media/rc/ |
| D | rc-tables.rst | 337 - Decrease volume
339 - VOLUME- / VOLUME DOWN
345 - Increase volume
347 - VOLUME+ / VOLUME UP
753 - On simpler IR's, without separate volume keys, you need to map
758 - On simpler IR's, without separate volume keys, you need to map
|
1234567