Home
last modified time | relevance | path

Searched full:acquisition (Results 1 – 25 of 239) sorted by relevance

12345678910

/linux-6.12.1/include/linux/comedi/
Dcomedidev.h41 * asynchronous acquisition commands. (Optionally initialized by the
49 * asynchronous acquisition commands. (Allocated and initialized during
54 * acquisition command on the subdevice. (Initially NULL.)
56 * an asynchronous acquisition command is running.
92 * @do_cmd: If the subdevice supports asynchronous acquisition commands, this
95 * @do_cmdtest: If the subdevice supports asynchronous acquisition commands,
97 * acquisition command without setting it up in hardware. (Initialized by
99 * @poll: If the subdevice supports asynchronous acquisition commands, this
103 * @cancel: If the subdevice supports asynchronous acquisition commands, this
106 * @buf_change: If the subdevice supports asynchronous acquisition commands,
[all …]
/linux-6.12.1/Documentation/devicetree/bindings/iio/adc/
Dti,adc12138.yaml43 ti,acquisition-time:
47 The number of conversion clock periods for the S/H's acquisition time.
83 ti,acquisition-time = <6>;
Dadi,ad7280a.yaml40 adi,acquisition-time-ns:
74 adi,acquisition-time-ns = <800>;
Dti,ads1015.yaml87 Data acquisition rate in samples per second for ADS1015, TLA2024
97 Data acquisition rate in samples per second for ADS1115
/linux-6.12.1/drivers/comedi/
Dcomedi_buf.c333 * Reserve up to @nbytes bytes of space to be written in the COMEDI acquisition
420 * COMEDI acquisition data buffer associated with the subdevice. The amount of
452 * Determine the amount of readable buffer space in the COMEDI acquisition data
485 * for reading in the COMEDI acquisition data buffer associated with the
527 * the COMEDI acquisition data buffer associated with the subdevice. The
610 * Write up to @nsamples samples to the COMEDI acquisition data buffer
612 * acquisition scan progress. If there is not enough room for the specified
615 * acquisition to terminate with an overrun error. Set the %COMEDI_CB_BLOCK
659 * Read up to @nsamples samples from the COMEDI acquisition data buffer
660 * associated with the subdevice, mark it as read and update the acquisition
DKconfig3 tristate "Data acquisition support (comedi)"
5 Enable support for a wide range of data acquisition devices
62 generate sample waveforms on systems that don't have data acquisition
454 tristate "MicroAxial ADQ12-B data acquisition and control card support"
917 This driver supports both Humusoft MF634 and MF624 Data acquisition
1017 Enable support for Meilhaus PCI data acquisition cards
1026 Enable support for Meilhaus PCI data acquisition cards
/linux-6.12.1/drivers/gpu/drm/
Ddrm_modeset_lock.c136 * This function is deprecated. It allocates a lock acquisition context and
139 * acquisition context, but it is also brittle because the context is global
174 * We hold the locks now, so it is safe to stash the acquisition in drm_modeset_lock_all()
190 * This function is deprecated. It uses the lock acquisition context stored
192 * code because it removes the need to manually deal with the acquisition
194 * be taken not to nest calls. New code should pass the acquisition context
432 * @ctx: lock acquisition context
/linux-6.12.1/Documentation/devicetree/bindings/input/touchscreen/
Dadi,ad7879.yaml51 adi,acquisition-time:
121 adi,acquisition-time = /bits/ 8 <1>;
145 adi,acquisition-time = /bits/ 8 <1>;
/linux-6.12.1/drivers/comedi/drivers/
Dadq12b.c4 * Driver for MicroAxial ADQ12-B data acquisition and control card
17 * Description: Driver for MicroAxial ADQ12-B data acquisition and control card
41 * Driver for the acquisition card ADQ12-B (without any add-on).
/linux-6.12.1/Documentation/locking/
Dww-mutex-design.rst65 acquired when starting the lock acquisition. This ticket is stored in the
76 * Normal lock acquisition with a context, using ww_mutex_lock.
78 * Slowpath lock acquisition on the contending lock, used by the task that just
240 - They can handle lock-acquisition in any order which allows us to start walking
265 Also, method 3 can't fail the lock acquisition step since it doesn't return
/linux-6.12.1/drivers/misc/
Ddw-xdata-pcie.c169 /* First acquisition of current count frames */ in dw_xdata_perf()
176 * Wait 100ms between the 1st count frame acquisition and the 2nd in dw_xdata_perf()
177 * count frame acquisition, in order to calculate the speed later in dw_xdata_perf()
181 /* Second acquisition of current count frames */ in dw_xdata_perf()
/linux-6.12.1/kernel/locking/
Drtmutex_api.c274 * __rt_mutex_start_proxy_lock() - Start lock acquisition for another task
321 * rt_mutex_start_proxy_lock() - Start lock acquisition for another task
355 * rt_mutex_wait_proxy_lock() - Wait for lock acquisition
361 * Wait for the lock acquisition started on our behalf by
392 * rt_mutex_cleanup_proxy_lock() - Cleanup failed lock acquisition
/linux-6.12.1/tools/memory-model/
DREADME171 lock acquisition/release, and RCU operations.
212 Provides a front-end analysis of lock acquisition and release,
213 for example, associating a lock acquisition with the preceding
/linux-6.12.1/drivers/media/dvb-frontends/
Dstb0899_algo.c514 /* Carrier loop optimization versus symbol rate for acquisition*/ in stb0899_dvbs_algo()
541 dprintk(state->verbose, FE_DEBUG, 1, "Set the timing loop to acquisition"); in stb0899_dvbs_algo()
542 /* Set the timing loop to acquisition */ in stb0899_dvbs_algo()
547 * Do not read any status variables while acquisition, in stb0899_dvbs_algo()
548 * If any needed, read before the acquisition starts in stb0899_dvbs_algo()
550 * acquisition to go bad and hence no locks. in stb0899_dvbs_algo()
568 * 1/2 and 7/8 for acquisition in stb0899_dvbs_algo()
664 stb0899_write_reg(state, STB0899_VITSYNC, 0x39); /* SN to b'11 for acquisition */ in stb0899_dvbs_algo()
1034 * trigger a DVB-S2 acquisition
1059 /* start acquisition process */ in stb0899_dvbs2_reacquire()
[all …]
/linux-6.12.1/drivers/comedi/drivers/ni_routing/
DREADME41 of signal routing capabilities of National Instruments data-acquisition and
162 Comedi already provides such a common interface for data-acquisition and control
191 acquisition---not
/linux-6.12.1/drivers/acpi/acpica/
Dutlock.c62 * DESCRIPTION: Reader interfaces for reader/writer locks. On acquisition,
123 * release the writer mutex associated with the lock. Acquisition
/linux-6.12.1/Documentation/devicetree/bindings/misc/
Dlwn-bk4.txt3 A device which handles data acquisition from compatible industrial
/linux-6.12.1/drivers/media/i2c/
Dsaa711x_regs.h88 /* Basic settings and acquisition window definition */
135 /* Basic settings and acquisition window definition */
384 /* Task A: Basic settings and acquisition window definition */
460 /* Task B: Basic settings and acquisition window definition */
/linux-6.12.1/drivers/iio/adc/
Dti-ads7924.c108 * Acquisition Time according to ACQTIME[4:0] register bits.
109 * The Acquisition Time is given by:
111 * Using default value of 0 for ACQTIME[4:0] results in a minimum acquisition
Dmax1118.c86 * The acquisition interval begins with the falling edge of in max1118_read()
87 * CNVST. The total acquisition and conversion process takes in max1118_read()
Dad7944.c165 /* Then we can read the data during the acquisition phase */ in ad7944_3wire_cs_mode_init_msg()
240 * ad7944_convert_and_acquire - Perform a single conversion and acquisition
244 * Perform a conversion and acquisition of a single sample using the
256 * and acquisition process. In other modes adc->cnv is NULL and is in ad7944_convert_and_acquire()
/linux-6.12.1/drivers/iio/common/ssp_sensors/
Dssp_dev.c198 * ssp_get_sensor_delay() - gets sensor data acquisition period
202 * Returns acquisition period in ms
211 * ssp_enable_sensor() - enables data acquisition for sensor
273 * ssp_change_delay() - changes data acquisition for sensor
/linux-6.12.1/Documentation/RCU/Design/Memory-Ordering/
DTree-RCU-Memory-Ordering.rst52 acquisition, including ``raw_spin_lock_rcu_node()``,
58 The key point is that the lock-acquisition functions, including
60 immediately after successful acquisition of the lock.
65 one of the above lock-acquisition functions.
69 of the above lock-acquisition functions executing on that same CPU,
70 even if the lock-release and lock-acquisition functions are operating
78 lock-acquisition and lock-release functions::
110 acquisition functions, this ``WARN_ON()`` could trigger, for example
/linux-6.12.1/Documentation/devicetree/bindings/rng/
Dsparc_sun_oracle_rng.txt10 more recent systems (after Oracle acquisition of SUN)
/linux-6.12.1/arch/sparc/prom/
Dbootstr_64.c3 * bootstr.c: Boot string/argument acquisition from the PROM.

12345678910