Searched full:using (Results 1 – 25 of 7623) sorted by relevance
12345678910>>...305
| /Linux-v5.4/sound/soc/atmel/ |
| D | Kconfig | 24 tristate "SoC PCM DAI support for AT91 SSC controller using PDC"
30 in PDC mode configured using audio-graph-card in device-tree.
33 tristate "SoC PCM DAI support for AT91 SSC controller using DMA"
39 in DMA mode configured using audio-graph-card in device-tree.
52 tristate "Atmel ASoC driver for boards using WM8904 codec"
58 Say Y if you want to add support for Atmel ASoC driver for boards using
69 at91sam9x5 based board that is using WM8731 codec.
72 tristate "Atmel ASoC driver for boards using CLASSD"
77 Say Y if you want to add support for Atmel ASoC driver for boards using
81 tristate "Atmel ASoC driver for boards using PDMIC"
[all …]
|
| /Linux-v5.4/sound/soc/tegra/ |
| D | Kconfig | 66 tristate "SoC Audio support for Tegra boards using an RT5640 codec"
71 boards using the RT5640 codec, such as Dalmore.
74 tristate "SoC Audio support for Tegra boards using a WM8753 codec"
79 boards using the WM8753 codec, such as Whistler.
82 tristate "SoC Audio support for Tegra boards using a WM8903 codec"
87 boards using the WM8093 codec. Currently, the supported boards are
91 tristate "SoC Audio support for Tegra boards using a WM9712 codec"
97 boards using the WM9712 (or compatible) codec.
108 tristate "SoC Audio support for Tegra boards using an ALC5632 codec"
116 tristate "SoC Audio support for Tegra boards using a MAX98090 codec"
[all …]
|
| /Linux-v5.4/Documentation/filesystems/nfs/ |
| D | nfsroot.txt | 43 This can be established using the following kernel command line parameters:
93 this means that the kernel tries to configure everything using
104 Default: Determined using autoconfiguration.
117 Default: Determined using autoconfiguration.
122 Default: Determined using autoconfiguration.
128 Default: Determined using autoconfiguration.
143 Otherwise the device is determined using
146 and using the device that received the first reply.
150 requests are sent using all protocols, and the first one
176 Default: None if not using autoconfiguration; determined
[all …]
|
| /Linux-v5.4/arch/arm64/crypto/ |
| D | Kconfig | 8 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"
109 tristate "NHPoly1305 hash function using NEON instructions (for Adiantum)"
[all …]
|
| /Linux-v5.4/arch/arm/mach-s3c24xx/ |
| D | Kconfig | 191 Say Y here if you are using the American Microsystems M5900 Series
207 Say Y here if you are using the Simtec Electronics EB2410ITX
225 Say Y here if you are using the HP IPAQ H1940
248 Say Y here if you are using the Nex Vision OTOM board
255 Say Y here if you are using the Armzone QT2410
262 Say Y here if you are using the SMDK2410 or the derived module A9M2410
269 Say Y here if you are using the TinCanTools Hammer Board
281 Say Y here if you are using the Thorcom VR1000 board.
319 Say Y here if you are using the Logitech Jive.
336 Say Y here if you are using an SMDK2412
[all …]
|
| /Linux-v5.4/Documentation/driver-api/dmaengine/ |
| D | dmatest.rst | 7 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.4/drivers/ptp/ |
| D | Kconfig | 36 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.
65 This driver adds support for using the IXP46X as a PTP
68 using the SO_TIMESTAMPING API.
84 This driver adds support for using the DP83640 as a PTP
87 using the SO_TIMESTAMPING API.
98 This driver adds support for using the PCH EG20T as a PTP
100 when using the end-to-end delay (E2E) mechanism. The peer
104 hardware time stamps on the PTP Ethernet packets using the
[all …]
|
| /Linux-v5.4/arch/arm/crypto/ |
| D | Kconfig | 8 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.4/drivers/pinctrl/intel/ |
| D | Kconfig | 32 allows configuring of SoC pins and using them as GPIOs.
42 interface that allows configuring of SoC pins and using them as
59 configuring of SoC pins and using them as GPIOs.
67 of Intel Cannon Lake PCH pins and using them as GPIOs.
75 of Intel Cedar Fork PCH pins and using them as GPIOs.
83 of Intel Denverton SoC pins and using them as GPIOs.
91 of Intel Gemini Lake SoC pins and using them as GPIOs.
99 of Intel Ice Lake PCH pins and using them as GPIOs.
107 of Intel Lewisburg pins and using them as GPIOs.
116 using them as GPIOs.
|
| /Linux-v5.4/Documentation/devicetree/bindings/sound/ |
| D | rt5659.txt | 25 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
|
| D | rt5645.txt | 24 1: using IN2P pin as dmic1 data pin
25 2: using GPIO6 pin as dmic1 data pin
26 3: using GPIO10 pin as dmic1 data pin
27 4: using GPIO12 pin as dmic1 data pin
31 1: using IN2N pin as dmic2 data pin
32 2: using GPIO5 pin as dmic2 data pin
33 3: using GPIO11 pin as dmic2 data pin
|
| D | rt5668.txt | 17 1: using GPIO2 pin as dmic1 data pin
18 2: using GPIO5 pin as dmic1 data pin
21 0: using GPIO1 pin as dmic1 clock pin
22 1: using GPIO3 pin as dmic1 clock pin
26 1: using JD1 as JD source
|
| D | rt5682.txt | 17 1: using GPIO2 pin as dmic1 data pin
18 2: using GPIO5 pin as dmic1 data pin
21 0: using GPIO1 pin as dmic1 clock pin
22 1: using GPIO3 pin as dmic1 clock pin
26 1: using JD1 as JD source
|
| /Linux-v5.4/sound/soc/sof/intel/ |
| D | Kconfig | 66 using the Baytrail, Braswell or Cherrytrail processors.
81 using the Broadwell processors.
101 using the Tangier/Merrifield processors.
116 using the Apollolake processors.
131 using the Geminilake processors.
146 using the Cannonlake processors.
161 using the Coffeelake processors.
176 using the Icelake processors.
198 using the Cometlake-LP processors.
213 using the Cometlake-H processors.
[all …]
|
| /Linux-v5.4/include/linux/regulator/ |
| D | driver.h | 79 * @set_voltage_sel: Set the voltage for the regulator using the specified
279 * @vsel_range_reg: Register for range selector when using pickable ranges
282 * @vsel_reg: Register for selector when using regulator_regmap_X_voltage_
289 * @csel_reg: Register for current limit selector using regmap set_current_limit
292 * using regulator_set_voltage_sel_regmap
294 * output when using regulator_set_voltage_sel_regmap
295 * @enable_reg: Register for control when using regmap enable/disable ops
296 * @enable_mask: Mask for control when using regmap enable/disable ops
297 * @enable_val: Enabling value for control when using regmap enable/disable ops
298 * @disable_val: Disabling value for control when using regmap enable/disable ops
[all …]
|
| /Linux-v5.4/Documentation/core-api/ |
| D | xarray.rst | 22 clustered; hashing the object and using the hash as the index will not
39 You must first convert it into an entry using xa_mk_value().
44 Some users want to store tagged pointers instead of using the marks
72 You can then set entries using xa_store() and get entries
73 using xa_load(). xa_store will overwrite any entry with the
80 You can conditionally replace an entry at an index by using
90 You can enquire whether a mark is set on an entry by using
92 on it by using xa_set_mark() and remove the mark from an entry by
117 Using xa_insert() on a reserved entry will fail.
125 entries in the XArray using the xa_for_each() iterator.
[all …]
|
| /Linux-v5.4/Documentation/dev-tools/ |
| D | kgdb.rst | 2 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.4/include/linux/ |
| D | cfag12864b.h | 40 * 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.4/lib/zstd/ |
| D | fse.h | 81 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.4/Documentation/driver-api/gpio/ |
| D | drivers-on-gpio.rst | 2 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 to emulate MCTRL (modem control) signals CTS/RTS by using two GPIO lines. The
98 Use those instead of talking directly to the GPIOs using sysfs; they integrate
100 just using the appropriate kernel drivers will simplify and speed up your
|
| /Linux-v5.4/net/netlabel/ |
| D | netlabel_mgmt.h | 43 * 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.4/drivers/nvme/host/ |
| D | Kconfig | 36 This provides support for the NVMe over Fabrics protocol using
38 to use remote block devices exported using the NVMe protocol set.
53 This provides support for the NVMe over Fabrics protocol using
55 exported using the NVMe protocol set.
69 This provides support for the NVMe over Fabrics protocol using
71 exported using the NVMe protocol set.
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | selection-api-configuration.rst | 26 control the rounding behaviour using
57 coordinates are obtained using ``V4L2_SEL_TGT_COMPOSE_BOUNDS``. All
69 control rounding behaviour using
72 For capture devices the default composing rectangle is queried using
77 ``V4L2_SEL_TGT_COMPOSE_PADDED``. It contains all pixels defined using
97 cropping coordinates are obtained using ``V4L2_SEL_TGT_CROP_BOUNDS``.
100 specified using :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
110 For output devices the default cropping rectangle is queried using
141 and the height of rectangles obtained using ``V4L2_SEL_TGT_CROP`` and
143 scaling is applied. The application can compute the scaling ratios using
|
| /Linux-v5.4/Documentation/PCI/endpoint/ |
| D | pci-endpoint.rst | 6 endpoint controller driver, endpoint function driver, and using configfs
63 devm_pci_epc_create() or pci_epc_create() using devm_pci_epc_destroy() or
97 using this API.
118 free the memory space allocated using pci_epc_mem_alloc_addr().
125 using these APIs.
134 Release the reference to the PCI endpoint controller obtained using
178 The PCI Function driver can then register the PCI EPF driver by using
183 The PCI Function driver can unregister the PCI EPF driver by using
188 The PCI Function driver can allocate space for a particular BAR using
194 (using pci_epf_alloc_space) by invoking pci_epf_free_space().
[all …]
|
| /Linux-v5.4/arch/arm/mach-at91/ |
| D | Kconfig | 17 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:
|
12345678910>>...305
