Home
last modified time | relevance | path

Searched full:using (Results 1 – 25 of 7431) sorted by relevance

12345678910>>...298

/Linux-v5.10/sound/soc/atmel/
DKconfig26 tristate "SoC PCM DAI support for AT91 SSC controller using PDC"
32 in PDC mode configured using audio-graph-card in device-tree.
35 tristate "SoC PCM DAI support for AT91 SSC controller using DMA"
41 in DMA mode configured using audio-graph-card in device-tree.
54 tristate "Atmel ASoC driver for boards using WM8904 codec"
60 Say Y if you want to add support for Atmel ASoC driver for boards using
71 at91sam9x5 based board that is using WM8731 codec.
74 tristate "Atmel ASoC driver for boards using CLASSD"
79 Say Y if you want to add support for Atmel ASoC driver for boards using
83 tristate "Atmel ASoC driver for boards using PDMIC"
[all …]
/Linux-v5.10/tools/testing/kunit/test_data/
Dtest_is_test_passed-no_tests_run.log24 Using 2.6 host AIO
39 Using a channel type which is configured out of UML
41 Using a channel type which is configured out of UML
43 Using a channel type which is configured out of UML
45 Using a channel type which is configured out of UML
47 Using a channel type which is configured out of UML
49 Using a channel type which is configured out of UML
51 Using a channel type which is configured out of UML
53 Using a channel type which is configured out of UML
55 Using a channel type which is configured out of UML
[all …]
Dtest_output_isolated_correctly.log12 posix-timer cpumask == cpu_all_mask, using cpu_possible_mask instead
61 Using a channel type which is configured out of UML
63 Using a channel type which is configured out of UML
65 Using a channel type which is configured out of UML
67 Using a channel type which is configured out of UML
69 Using a channel type which is configured out of UML
71 Using a channel type which is configured out of UML
73 Using a channel type which is configured out of UML
75 Using a channel type which is configured out of UML
77 Using a channel type which is configured out of UML
[all …]
/Linux-v5.10/drivers/pinctrl/intel/
DKconfig24 allows configuring of SoC pins and using them as GPIOs.
37 using them as GPIOs.
47 interface that allows configuring of SoC pins and using them as
64 configuring of SoC pins and using them as GPIOs.
72 of Intel Cannon Lake PCH pins and using them as GPIOs.
80 of Intel Cedar Fork PCH pins and using them as GPIOs.
88 of Intel Denverton SoC pins and using them as GPIOs.
96 of Intel Emmitsburg pins and using them as GPIOs.
104 of Intel Gemini Lake SoC pins and using them as GPIOs.
112 of Intel Ice Lake PCH pins and using them as GPIOs.
[all …]
/Linux-v5.10/arch/arm64/crypto/
DKconfig8 implemented using ARM64 specific CPU features or instructions.
57 tristate "GHASH/AES-GCM using ARMv8 Crypto Extensions"
64 tristate "CRCT10DIF digest algorithm using PMULL instructions"
69 tristate "AES core cipher using scalar instructions"
73 tristate "AES core cipher using ARMv8 Crypto Extensions"
79 tristate "AES in CCM mode using ARMv8 Crypto Extensions"
87 tristate "AES in ECB/CBC/CTR/XTS modes using ARMv8 Crypto Extensions"
95 tristate "AES in ECB/CBC/CTR/XTS modes using NEON instructions"
103 tristate "ChaCha20, XChaCha20, and XChaCha12 stream ciphers using NEON instructions"
110 tristate "Poly1305 hash function using scalar or NEON instructions"
[all …]
/Linux-v5.10/Documentation/admin-guide/nfs/
Dnfsroot.rst50 This can be established using the following kernel command line parameters:
97 this means that the kernel tries to configure everything using
107 Default: Determined using autoconfiguration.
121 Default: Determined using autoconfiguration.
125 Default: Determined using autoconfiguration.
131 Default: Determined using autoconfiguration.
146 Otherwise the device is determined using
149 and using the device that received the first reply.
154 requests are sent using all protocols, and the first one
180 Default: None if not using autoconfiguration; determined
[all …]
/Linux-v5.10/arch/arm/mach-s3c/
DKconfig.s3c24xx179 Say Y here if you are using the American Microsystems M5900 Series
195 Say Y here if you are using the Simtec Electronics EB2410ITX
213 Say Y here if you are using the HP IPAQ H1940
236 Say Y here if you are using the Nex Vision OTOM board
243 Say Y here if you are using the Armzone QT2410
250 Say Y here if you are using the SMDK2410 or the derived module A9M2410
257 Say Y here if you are using the TinCanTools Hammer Board
269 Say Y here if you are using the Thorcom VR1000 board.
307 Say Y here if you are using the Logitech Jive.
324 Say Y here if you are using an SMDK2412
[all …]
/Linux-v5.10/drivers/ptp/
DKconfig36 This driver adds support for using the Digital timing engine
51 This driver adds support for using the Freescale QorIQ 1588
54 packets using the SO_TIMESTAMPING API.
70 This driver adds support for using the DP83640 as a PTP
73 using the SO_TIMESTAMPING API.
84 This driver adds support for using the ZHAW InES 1588 IP
94 This driver adds support for using the PCH EG20T as a PTP
96 when using the end-to-end delay (E2E) mechanism. The peer
100 hardware time stamps on the PTP Ethernet packets using the
112 This driver adds support for using kvm infrastructure as a PTP
[all …]
/Linux-v5.10/Documentation/driver-api/dmaengine/
Ddmatest.rst7 This small document introduces how to test DMA drivers using dmatest module.
72 Once started a message like " dmatest: Added 1 threads using dma0chan0" is
154 Channels are registered using the "channel" parameter. Channels can be requested by their
160 dmatest: Added 1 threads using dma0chan2
168 dmatest: Added 1 threads using dma0chan1
170 dmatest: Added 1 threads using dma0chan2
180 dmatest: Added 1 threads using dma0chan0
181 dmatest: Added 1 threads using dma0chan3
182 dmatest: Added 1 threads using dma0chan4
183 dmatest: Added 1 threads using dma0chan5
[all …]
/Linux-v5.10/arch/arm/crypto/
DKconfig8 implemented using ARM specific CPU features or instructions.
18 using optimized ARM assembler.
28 using optimized ARM NEON assembly, when NEON instructions are
38 using special ARMv8 Crypto Extensions.
47 using special ARMv8 Crypto Extensions.
55 using optimized ARM assembler and NEON, when available.
63 using optimized ARM assembler and NEON, when available.
82 tristate "Bit sliced AES using NEON instructions"
98 tristate "Accelerated AES using ARMv8 Crypto Extensions"
108 tristate "PMULL-accelerated GHASH using NEON/ARMv8 Crypto Extensions"
[all …]
/Linux-v5.10/sound/soc/tegra/
DKconfig122 tristate "SoC Audio support for Tegra boards using an RT5640 codec"
127 boards using the RT5640 codec, such as Dalmore.
130 tristate "SoC Audio support for Tegra boards using a WM8753 codec"
135 boards using the WM8753 codec, such as Whistler.
138 tristate "SoC Audio support for Tegra boards using a WM8903 codec"
143 boards using the WM8093 codec. Currently, the supported boards are
147 tristate "SoC Audio support for Tegra boards using a WM9712 codec"
153 boards using the WM9712 (or compatible) codec.
164 tristate "SoC Audio support for Tegra boards using an ALC5632 codec"
172 tristate "SoC Audio support for Tegra boards using a MAX98090 codec"
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/sound/
Drt5659.txt25 1: using IN2N pin as dmic1 data pin
26 2: using GPIO5 pin as dmic1 data pin
27 3: using GPIO9 pin as dmic1 data pin
28 4: using GPIO11 pin as dmic1 data pin
32 1: using IN2P pin as dmic2 data pin
33 2: using GPIO6 pin as dmic2 data pin
34 3: using GPIO10 pin as dmic2 data pin
35 4: using GPIO12 pin as dmic2 data pin
39 1: using JD3 as JD source
Drt5645.txt28 1: using IN2P pin as dmic1 data pin
29 2: using GPIO6 pin as dmic1 data pin
30 3: using GPIO10 pin as dmic1 data pin
31 4: using GPIO12 pin as dmic1 data pin
35 1: using IN2N pin as dmic2 data pin
36 2: using GPIO5 pin as dmic2 data pin
37 3: using GPIO11 pin as dmic2 data pin
/Linux-v5.10/include/linux/regulator/
Ddriver.h62 * @set_voltage_sel: Set the voltage for the regulator using the specified
262 * @vsel_range_reg: Register for range selector when using pickable ranges
265 * @vsel_reg: Register for selector when using ``regulator_map_*_voltage_*``
272 * @csel_reg: Register for current limit selector using regmap set_current_limit
275 * using regulator_set_voltage_sel_regmap
277 * output when using regulator_set_voltage_sel_regmap
278 * @enable_reg: Register for control when using regmap enable/disable ops
279 * @enable_mask: Mask for control when using regmap enable/disable ops
280 * @enable_val: Enabling value for control when using regmap enable/disable ops
281 * @disable_val: Disabling value for control when using regmap enable/disable ops
[all …]
/Linux-v5.10/Documentation/core-api/
Dxarray.rst22 clustered; hashing the object and using the hash as the index will not
35 You must first convert it into an entry using xa_mk_value().
66 You can then set entries using xa_store() and get entries
67 using xa_load(). xa_store will overwrite any entry with the
74 You can conditionally replace an entry at an index by using
105 Using xa_insert() on a reserved entry will fail.
113 entries in the XArray using the xa_for_each() iterator.
120 iterate over marked entries by using the xa_for_each_marked() iterator.
122 You can enquire whether a mark is set on an entry by using
124 by using xa_set_mark() and remove the mark from an entry by calling
[all …]
/Linux-v5.10/Documentation/dev-tools/
Dkgdb.rst2 Using kgdb, kdb and the kernel debugger internals
33 Two machines are required for using kgdb. One of these machines is a
71 If the architecture that you are using supports the kernel option
75 supports it for the architecture you are using, you can use hardware
106 ``CONFIG_KGDB_SERIAL_CONSOLE`` interface if you plan on using kdb on a
129 using kdb and kgdb as well as providing some examples of the
142 console as your primary console as well as using it to perform kernel
174 depending on if you are using kdb and/or kgdb, in one of the following
176 optional configurations together. Using kms + only gdb is generally not
179 Using loadable module or built-in
[all …]
/Linux-v5.10/include/linux/
Dcfag12864b.h40 * Returns 0 if successful (anyone was using it),
41 * or != 0 if failed (someone is using it).
48 * You should call this only when you finish using the LCD.
53 * Is enabled refreshing? (is anyone using the module?)
55 * Returns 0 if refreshing is not enabled (anyone is using it),
56 * or != 0 if refreshing is enabled (someone is using it).
/Linux-v5.10/lib/zstd/
Dfse.h81 3. save normalized counters to memory buffer using writeNCount()
83 5. encode the data stream using encoding table 'CTable'
88 3. decode the data stream using decoding table 'DTable'
91 For example, it's possible to compress several blocks using the same 'CTable',
92 or to save and provide normalized distribution using external method.
98 It saves CPU time, by using smaller tables, while preserving or even improving compression ratio.
106 or an errorCode, which can be tested using FSE_isError() */
117 or an errorCode, which can be tested using FSE_isError(). */
125 Compress `src` using `ct` into `dst` which must be already allocated.
128 or an errorCode, which can be tested using FSE_isError() */
[all …]
/Linux-v5.10/arch/arm/mach-at91/
DKconfig17 Select this if you are using an SoC from Microchip's SAME7, SAMS7 or SAMV7
33 Select this if ou are using one of Microchip's SAMA5D2 family SoC.
44 Select this if you are using one of Microchip's SAMA5D3 family SoC.
58 Select this if you are using one of Microchip's SAMA5D4 family SoC.
72 Select this if you are using Microchip's AT91RM9200 SoC.
90 Select this if you are using one of those Microchip SoC:
123 Select this if you are using Microchip's SAM9X60 SoC
/Linux-v5.10/sound/soc/sof/intel/
DKconfig67 using the Baytrail, Braswell or Cherrytrail processors.
90 using the Broadwell processors.
117 using the Tangier/Merrifield processors.
132 using the Apollolake processors.
147 using the Geminilake processors.
162 using the Cannonlake processors.
178 using the Coffeelake processors.
194 using the Icelake processors.
222 using the Cometlake processors.
229 using the Tigerlake processors.
[all …]
/Linux-v5.10/Documentation/userspace-api/media/v4l/
Dselection-api-configuration.rst19 control the rounding behaviour using
50 coordinates are obtained using ``V4L2_SEL_TGT_COMPOSE_BOUNDS``. All
62 control rounding behaviour using
65 For capture devices the default composing rectangle is queried using
70 ``V4L2_SEL_TGT_COMPOSE_PADDED``. It contains all pixels defined using
90 cropping coordinates are obtained using ``V4L2_SEL_TGT_CROP_BOUNDS``.
93 specified using :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
103 For output devices the default cropping rectangle is queried using
134 and the height of rectangles obtained using ``V4L2_SEL_TGT_CROP`` and
136 scaling is applied. The application can compute the scaling ratios using
/Linux-v5.10/fs/nilfs2/
Dalloc.c23 * @inode: inode of metadata file using this allocator
34 * @inode: inode of metadata file using this allocator
44 * @inode: inode of metadata file using this allocator
78 * @inode: inode of metadata file using this allocator
93 * @inode: inode of metadata file using this allocator
109 * @inode: inode of metadata file using this allocator
162 * @inode: inode of metadata file using this allocator
234 * @inode: inode of metadata file using this allocator
254 * @inode: inode of metadata file using this allocator
273 * @inode: inode of metadata file using this allocator
[all …]
/Linux-v5.10/net/netlabel/
Dnetlabel_mgmt.h43 * If using NETLBL_NLTYPE_CIPSOV4 the following attributes are required:
47 * If using NETLBL_NLTYPE_UNLABELED no other attributes are required,
81 * If the mapping is using the NETLBL_NLTYPE_CIPSOV4 type then the following
86 * If the mapping is using the NETLBL_NLTYPE_UNLABELED type no other
97 * If using NETLBL_NLTYPE_CIPSOV4 the following attributes are required:
101 * If using NETLBL_NLTYPE_UNLABELED no other attributes are required,
117 * On success the kernel should send a response using the following format:
130 * If the mapping is using the NETLBL_NLTYPE_CIPSOV4 type then the following
135 * If the mapping is using the NETLBL_NLTYPE_UNLABELED type no other
/Linux-v5.10/Documentation/misc-devices/
Dxilinx_sdfec.rst128 Determine the configuration of the SD-FEC core by using the ioctl
136 Setting the order is done by using the ioctl :c:macro:`XSDFEC_SET_ORDER`
151 - Add the LPDC Code Parameters using the ioctl :c:macro:`XSDFEC_ADD_LDPC_CODE_PARAMS`
164 Configuring the Turbo decode parameters is done by using the ioctl :c:macro:`XSDFEC_SET_TURBO` usin…
174 Enabling or disabling interrupts is done by using the ioctl :c:macro:`XSDFEC_SET_IRQ`. The members …
184 Bypassing the SD-FEC is done by using the ioctl :c:macro:`XSDFEC_SET_BYPASS`
193 Start the SD-FEC core by using the ioctl :c:macro:`XSDFEC_START_DEV`
198 Get the SD-FEC status of the device by using the ioctl :c:macro:`XSDFEC_GET_STATUS`, which will fil…
207 - Get stats by using the ioctl :c:macro:`XSDFEC_GET_STATS`
210 - Get state by using the ioctl :c:macro:`XSDFEC_GET_STATUS`
[all …]
/Linux-v5.10/Documentation/driver-api/gpio/
Ddrivers-on-gpio.rst2 Subsystem drivers using GPIO
7 drivers can quite easily interconnect with other kernel subsystems using
25 up to three buttons by simply using GPIOs and no mouse port. You can cut the
54 of wires, at least SCK and optionally MISO, MOSI and chip select lines) using
58 to this SPI by using the mmc_spi host from the MMC/SD card subsystem.
60 - w1-gpio: drivers/w1/masters/w1-gpio.c is used to drive a one-wire bus using
89 Consumer Electronics Control bus using only GPIO. It is used to communicate
94 AC charger or more complex tasks such as indicating charging status using
101 to emulate MCTRL (modem control) signals CTS/RTS by using two GPIO lines. The
107 Needless to say, just using the appropriate kernel drivers will simplify and

12345678910>>...298