Home
last modified time | relevance | path

Searched refs:recording (Results 1 – 47 of 47) sorted by relevance

/linux-4.4.14/Documentation/isdn/
DREADME.audio48 AT+VRX Start recording. Emulator responds with
94 Audio recording.
103 recording, responding with VCON.
104 <DLE><DC4> Abort recording, (send by appl.) Emulator
105 stops recording, sends DLE,ETX.
119 start of recording.
134 When _both_ commands for recording and playback are given in _one_
136 In this mode, the only way to stop recording is sending <DLE><DC4>
/linux-4.4.14/tools/testing/selftests/ftrace/test.d/
Dfunctions6 disable_tracing() { # stop trace recording
10 enable_tracing() { # start trace recording
/linux-4.4.14/Documentation/sound/alsa/
DBt87x.txt15 driver which can be used for recording sound (and _only_ recording, no
22 video data, so it's quite possible that audio recording may not work
Demu10k1-jack.txt2 latency, multichannel recording functionality. All of my recent work to allow
46 still see 16 capture channels, but only 14 are available for recording inputs.
49 ports to FXBUS2 (multitrack recording input) and EXTOUT (physical output)
DVIA82xx-mixer.txt6 Setting it to 'Input2' on such boards will cause recording to hang, or fail
DAudiophile-Usb.txt58 * Apart from recording an audio digital stream, enabling the Di port is a way
90 by the applications: for instance if the user is recording in a
120 * recording a S24_3BE encoded raw file from the Ai port
DHD-Audio.txt277 recording from CD input won't work in many cases although the driver
/linux-4.4.14/Documentation/sound/oss/
DESS9 All ESS chips now have a recording level setting. This is a need-to-have for
10 people who want to use their ESS for recording sound.
DSoundPro36 recording. I don't know if this works, b/c I haven't tested it. Anyway, if
98 - recording
99 - recording device selection
104 - come up with a scheme which allows recording volumes for each subdevice.
Dbtaudio21 driver which can be used for recording sound (and _only_ recording, no
Dultrasound28 If you have problems in recording with GUS MAX, you could try to use
DALS51 - 8 and 16 bit audio recording
DREADME.OSS69 Megens SA MIDI recording for SB and SB Pro (initial version).
453 GUS ACE (No MIDI port and audio recording)
831 audio (at least recording) from working.
953 simultaneously. Using the MSS mode provides 16 bit recording and playback.
979 mixer volume of the channel level below 10%. For recording you have
980 to select the channel as a recording source and to use volume above 10%.
1002 simultaneous recording and playback. Use /dev/dsp (the daughtercard) for
1003 recording and /dev/dsp1 (GUS GF1) for playback.
1014 If you have problems in recording with GUS MAX, you could try to use
1020 only recording level. Mixer control "speaker" is used to control volume of
[all …]
DOpti171 (eg., recording from /dev/audio). When any companded capture is
/linux-4.4.14/sound/pci/hda/
Dpatch_conexant.c51 bool recording; member
403 update_mic_pin(codec, 0x1a, spec->recording ? in olpc_xo_update_mic_pins()
405 update_mic_pin(codec, 0x1b, spec->recording ? in olpc_xo_update_mic_pins()
422 if (spec->recording) in olpc_xo_update_mic_pins()
429 update_mic_pin(codec, 0x1e, spec->recording ? PIN_IN : 0); in olpc_xo_update_mic_pins()
461 spec->recording = 1; in olpc_xo_capture_hook()
465 spec->recording = 0; in olpc_xo_capture_hook()
/linux-4.4.14/tools/perf/Documentation/
Dintel-bts.txt10 consequence the present implementation is limited to per-thread recording.
17 recording must also be stipulated i.e. the --per-thread option for
Dperf-top.txt161 Enables call-graph (stack chain/backtrace) recording.
164 Setup and enable call-graph (stack chain/backtrace) recording,
Dperf-record.txt143 Enables call-graph (stack chain/backtrace) recording.
146 Setup and enable call-graph (stack chain/backtrace) recording,
164 When "dwarf" recording is used, perf also records (user) stack dump
Dperf-timechart.txt94 Do call-graph (stack chain/backtrace) recording
Dperf-probe.txt201 Add a probe on schedule() function 12th line with recording cpu local variable:
Dperf-script-python.txt349 scripts, one for recording and one for 'reporting'.
/linux-4.4.14/sound/oss/
DCHANGELOG126 - Fixed crash after recording with ESS688. It's generally a good
153 - Temporarily disabled recording with ESS1688/688 since it causes crash.
156 of the driver and makes recording to disk to work better. Unfortunately
229 the recording. Calling write() kills recording immediately so
311 - MIDI recording for SB and SB Pro. (Untested).
344 - Stereo recording for SB Pro. Somehow it was missing and nobody
Dsound_calls.h39 void reorganize_buffers (int dev, struct dma_buffparms *dmap, int recording);
Daudio.c538 void reorganize_buffers(int dev, struct dma_buffparms *dmap, int recording) in reorganize_buffers() argument
DKconfig237 recording and playing in the MultiSound drivers (both the Classic
/linux-4.4.14/drivers/media/dvb-core/
Ddvb_demux.h125 int recording; member
Ddvb_demux.c1288 dvbdemux->recording = 0; in dvb_dmx_init()
/linux-4.4.14/drivers/s390/char/
DKconfig165 prompt "Support for the z/VM recording system services (VM only)"
169 by the z/VM recording system services, eg. from *LOGREC, *ACCOUNT or
Dvmlogrdr.c643 static DEVICE_ATTR(recording, 0200, NULL, vmlogrdr_recording_store);
/linux-4.4.14/Documentation/video4linux/
DREADME.cx8824 - audio data dma (i.e. recording without loopback cable to the
DREADME.ivtv174 device. So while playing back a recording on /dev/video16, you can
DZoran460 if recording fails after a period of time.
/linux-4.4.14/Documentation/trace/
Dkprobetrace.txt102 This sets a kprobe on the top of do_sys_open() function with recording
112 recording return value as "myretprobe" event.
Dftrace.txt981 between the time of recording the max latency and the time of
982 recording the function that had that latency.
2147 One special side-effect to the recording of the functions being
/linux-4.4.14/Documentation/sound/alsa/soc/
Doverview.txt21 recording) audio. This is fine for a PC, but tends to waste a lot of
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Dfsl,ssi.txt27 capture (recording) of audio. This is typically dictated
/linux-4.4.14/Documentation/input/
Dyealink.txt203 Example - recording test:
/linux-4.4.14/arch/blackfin/
DKconfig.debug120 The trace buffer can be configured to omit recording of changes in
/linux-4.4.14/kernel/trace/
DKconfig266 trace recording, as it needs to add some checks to synchronize
267 recording with swaps. But this does not affect the performance
/linux-4.4.14/Documentation/dvb/
DREADME.dvb-usb179 but watching a channel while recording another channel on the same
/linux-4.4.14/tools/perf/
Ddesign.txt225 The 'mmap' and 'munmap' bits allow recording of PROT_EXEC mmap/munmap
/linux-4.4.14/Documentation/device-mapper/
Dthin-provisioning.txt79 snapshots which are recording large amounts of change, you may find you
/linux-4.4.14/drivers/media/pci/ttpci/
Dav7110.c408 if (av7110->demux.recording) in debiirq()
949 dvbdmx->recording = 0; in dvb_feed_stop_pid()
Dav7110_av.c130 dvbdmx->recording = 1; in av7110_av_start_record()
/linux-4.4.14/Documentation/laptops/
Dlaptop-mode.txt162 access time recording.
/linux-4.4.14/Documentation/
Dmd.txt360 A file recording the current state of the device in the array
/linux-4.4.14/Documentation/filesystems/
Dxfs-delayed-logging-design.txt20 recording a new change to the object. XFS does this via a method called