Searched full:front (Results 1 – 25 of 102) sorted by relevance
12345
/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/admin-guide/ |
D | pstore-blk.rst | 75 The chunk size in KB for oops/panic front-end. It **MUST** be a multiple of 4. 78 There are multiple chunks for oops/panic front-end depending on the remaining 79 space except other pstore front-ends. 87 The chunk size in KB for pmsg front-end. It **MUST** be a multiple of 4. 90 Unlike oops/panic front-end, there is only one chunk for pmsg front-end. 99 The chunk size in KB for console front-end. It **MUST** be a multiple of 4. 102 Similar to pmsg front-end, there is only one chunk for console front-end. 110 The chunk size in KB for ftrace front-end. It **MUST** be a multiple of 4. 113 Similar to oops front-end, there are multiple chunks for ftrace front-end 186 files is ``dmesg-pstore-blk-[N]`` for oops/panic front-end, [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/userspace-api/media/dvb/ |
D | frontend_f_open.rst | 57 In a system with multiple front-ends, it is usually the case that 59 long as a front-end device is opened in read/write mode, other open() 61 non-blocking or blocking mode was specified. A front-end device opened 67 powered up, and that other front-ends may have been powered down to make
|
D | frontend_f_close.rst | 33 This system call closes a previously opened front-end device. After 34 closing a front-end device, its corresponding hardware might be powered
|
D | fe-read-snr.rst | 37 currently received by the front-end. For this command, read-only access
|
D | fe-read-ber.rst | 37 received/demodulated by the front-end. For this command, read-only
|
D | fe-read-signal-strength.rst | 37 currently received by the front-end. For this command, read-only access
|
/Documentation/driver-api/media/ |
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 232 Front mic pin fixup on HP machines 296 Front HP fixup for Zotac Z68 352 no-front-hp 353 Disable front HP pin NID 0x1b 418 3-jack in back, 2-jack in front 420 6-jack in back, 2-jack in front 422 6-jack in back, 2-jack in front, SPDIF I/O [all …]
|
/Documentation/userspace-api/media/ |
D | fdl-appendix.rst | 61 A “Secondary Section” is a named appendix or a front-matter section of 84 Front-Cover Texts or Back-Cover Texts, in the notice that says that the 151 Front-Cover Texts on the front cover, and Back-Cover Texts on the back 153 publisher of these copies. The front cover must present the full title 285 front-matter sections or appendices that qualify as 300 :ref:`Front-Cover Text <fdl-cover-texts>`, and a passage of up to 25 304 Front-Cover Text and one of Back-Cover Text may be added by (or through 456 :ref:`Front-Cover Texts <fdl-cover-texts>` being LIST, and with 463 you have no :ref:`Front-Cover Texts <fdl-cover-texts>`, write “no 464 Front-Cover Texts” instead of “Front-Cover Texts being LIST”; likewise
|
/Documentation/devicetree/bindings/leds/ |
D | cznic,turris-omnia-leds.yaml | 13 This module adds support for the RGB LEDs found on the front panel of the 47 This property identifies one of the LEDs on the front panel of the
|
/Documentation/devicetree/bindings/iio/light/ |
D | sharp,gp2ap002.yaml | 48 of a "far away" object in front of the sensor. 55 of a "close" object in front of the sensor.
|
/Documentation/gpu/ |
D | drivers.rst | 19 xen-front
|
/Documentation/ABI/testing/ |
D | sysfs-class-led-driver-turris-omnia | 5 Description: (RW) On the front panel of the Turris Omnia router there is also
|
/Documentation/devicetree/bindings/sound/ |
D | name-prefix.txt | 17 sound-name-prefix = "FRONT";
|
/Documentation/devicetree/bindings/arm/omap/ |
D | dmm.txt | 3 The dynamic memory manager (DMM) is a module located immediately in front of the
|
/Documentation/devicetree/bindings/memory-controllers/ |
D | brcm,dpfe-cpu.txt | 1 DDR PHY Front End (DPFE) for Broadcom STB
|
/Documentation/i2c/busses/ |
D | i2c-ali15x3.rst | 52 100MHz CPU Front Side bus 54 CPU Front Side bus
|
/Documentation/networking/device_drivers/ethernet/toshiba/ |
D | spider_net.rst | 48 and everything in front of it should be "empty". If the hardware 56 all of the descrs in front of the tail pointer should be "full", and 68 is flowing RX traffic, everything in front of the head pointer should 159 that everything in front of the "empty" descr must surely also be empty,
|
12345