Searched full:front (Results 1 – 25 of 506) sorted by relevance
12345678910>>...21
| /Documentation/sound/designs/ |
| D | channel-mapping-api.rst | 18 ``{ front left, front right, rear left, rear right }.``
89 SNDRV_CHMAP_FL, /* front left */
90 SNDRV_CHMAP_FR, /* front right */
93 SNDRV_CHMAP_FC, /* front center */
99 SNDRV_CHMAP_FLC, /* front left center */
100 SNDRV_CHMAP_FRC, /* front right center */
103 SNDRV_CHMAP_FLW, /* front left wide */
104 SNDRV_CHMAP_FRW, /* front right wide */
105 SNDRV_CHMAP_FLH, /* front left high */
106 SNDRV_CHMAP_FCH, /* front center high */
[all …]
|
| D | control-names.rst | 34 Front front left/right channels
45 Front front position
|
| /Documentation/fb/ |
| D | viafb.modes | 17 # Front Porch 0.636 us 0.318 ms
42 # Front Porch 0.508 us 0.027 ms
63 # Front Porch 1.556 us 0.023 ms
84 # Front Porch 0.927 us 0.019 ms
105 # Front Porch 0.763 us 0.016 ms
126 # Front Porch 0.595 us 0.033 ms
147 # Front Porch 0.541 us 33.535 us
168 # Front Porch 0.735 us 0.027 ms
189 # Front Porch 1.000 us 0.026 ms
211 # Front Porch 0.323 us 0.021 ms
[all …]
|
| /Documentation/block/ |
| D | deadline-iosched.rst | 62 request, or it fits at the front. That is called either a back merge candidate
63 or a front merge candidate. Due to the way files are typically laid out,
64 back merges are much more common than front merges. For some work loads, you
66 front merge requests. Setting front_merges to 0 disables this functionality.
67 Front merges may still occur due to the cached last_merge hint, but since
69 rbtree front sector lookup when the io scheduler merge function is called.
|
| /Documentation/media/uapi/dvb/ |
| D | frontend_f_open.rst | 4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
67 In a system with multiple front-ends, it is usually the case that
69 long as a front-end device is opened in read/write mode, other open()
71 non-blocking or blocking mode was specified. A front-end device opened
77 powered up, and that other front-ends may have been powered down to make
|
| D | frontend_f_close.rst | 4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
43 This system call closes a previously opened front-end device. After
44 closing a front-end device, its corresponding hardware might be powered
|
| D | fe-read-snr.rst | 4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
44 currently received by the front-end. For this command, read-only access
|
| D | fe-read-ber.rst | 4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
44 received/demodulated by the front-end. For this command, read-only
|
| D | fe-read-signal-strength.rst | 4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
44 currently received by the front-end. For this command, read-only access
|
| D | fe-get-info.rst | 4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
20 about the - front-end. This call only requires read-only access to the device.
|
| D | fe-read-status.rst | 4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
19 FE_READ_STATUS - Returns status information about the front-end. This call only requires - read-onl…
|
| D | dmx-fwrite.rst | 4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
75 front- end. Make sure that these filters are stopped and that the
|
| D | frontend-header.rst | 4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
|
| D | dvb-frontend-event.rst | 4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
|
| /Documentation/media/kapi/ |
| D | dtv-demux.rst | 20 Each demux receives its TS input from a DVB front-end or from memory, as
21 set via this demux kABI. In a system with more than one front-end, the kABI
22 can be used to select one of the DVB front-ends as a TS source for a demux,
25 The demux kABI only controls front-ends regarding to their connections with
26 demuxes; the kABI used to set the other front-end parameters, such as
|
| /Documentation/sound/cards/ |
| D | audigy-mixer.rst | 47 name='PCM Front Playback Volume',index=0
49 This control is used to attenuate samples for left and right front PCM FX-bus
50 accumulators. ALSA uses accumulators 8 and 9 for left and right front PCM
51 samples for 5.1 playback. The result samples are forwarded to the front DAC PCM
77 stereo playback. The result samples are forwarded to the front DAC PCM slots
91 The result samples are forwarded to the front DAC PCM slots of the AC97 codec.
104 the front DAC PCM slots of the Philips DAC. Samples are forwarded to Mic
117 forwarded to the front DAC PCM slots of the Philips DAC.
128 digital input. The result samples are forwarded to the front DAC PCM slots
140 inputs (on the AudigyDrive). The result samples are forwarded to the front
[all …]
|
| D | cmipci.rst | 8 Front/Rear Multi-channel Playback
12 channels can be used for front/rear playbacks. Since there are two
17 card#0) for front and 4/6ch playbacks, while the second PCM device
43 front one) and was so excited. It was even with "Four Channel" bit
45 from front and rear speakers! But.. after reboot, all was gone.
56 The "Exchange DAC" switch is used to exchange front and rear playback
57 routes, i.e. the 2nd DAC is output from front output.
|
| D | sb-live-mixer.rst | 66 The result samples are forwarded to the front DAC PCM slots of the AC97 codec.
100 The result samples are forwarded to the front DAC PCM slots of the AC97 codec.
137 This control is used to attenuate samples for left and right front ADC PCM slots
138 of the AC97 codec. The result samples are forwarded to the front DAC PCM
148 This control is used to attenuate samples for left and right front ADC PCM slots
160 forwarded to the front DAC PCM slots of the AC97 codec.
172 forwarded to the front DAC PCM slots of the AC97 codec.
183 digital input. The result samples are forwarded to the front DAC PCM slots
195 digital inputs. The result samples are forwarded to the front DAC PCM slots
207 inputs (on the LiveDrive). The result samples are forwarded to the front
[all …]
|
| /Documentation/sound/hd-audio/ |
| D | models.rst | 12 5-jack in back, 2-jack in front
14 5-jack in back, 2-jack in front, a SPDIF out
16 6-jack in back, 2-jack in front
234 Front mic pin fixup on HP machines
294 Front HP fixup for Zotac Z68
348 no-front-hp
349 Disable front HP pin NID 0x1b
414 3-jack in back, 2-jack in front
416 6-jack in back, 2-jack in front
418 6-jack in back, 2-jack in front, SPDIF I/O
[all …]
|
| /Documentation/media/uapi/ |
| D | fdl-appendix.rst | 4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
68 A “Secondary Section” is a named appendix or a front-matter section of
91 Front-Cover Texts or Back-Cover Texts, in the notice that says that the
158 Front-Cover Texts on the front cover, and Back-Cover Texts on the back
160 publisher of these copies. The front cover must present the full title
292 front-matter sections or appendices that qualify as
307 :ref:`Front-Cover Text <fdl-cover-texts>`, and a passage of up to 25
311 Front-Cover Text and one of Back-Cover Text may be added by (or through
463 :ref:`Front-Cover Texts <fdl-cover-texts>` being LIST, and with
470 you have no :ref:`Front-Cover Texts <fdl-cover-texts>`, write “no
[all …]
|
| /Documentation/media/uapi/v4l/ |
| D | dev-touch.rst | 4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
28 analogue front end device which delivers touch data at high rate, and any touch
|
| D | async.rst | 4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
|
| /Documentation/gpu/ |
| D | drivers.rst | 19 xen-front
|
| /Documentation/media/uapi/rc/ |
| D | lirc-dev.rst | 4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
|
| /Documentation/devicetree/bindings/sound/ |
| D | name-prefix.txt | 17 sound-name-prefix = "FRONT";
|
12345678910>>...21