| /linux/drivers/pinctrl/intel/ |
| H A D | Kconfig | 22 allows configuring of SoC pins and using them as GPIOs.
30 using them as GPIOs.
46 of Intel PCH pins and using them as GPIOs. Currently the following
56 of Intel Alder Lake PCH pins and using them as GPIOs.
63 configuring of SoC pins and using them as GPIOs.
70 of Intel Cannon Lake PCH pins and using them as GPIOs.
77 of Intel Cedar Fork PCH pins and using them as GPIOs.
84 of Intel Denverton SoC pins and using them as GPIOs.
91 of Intel Elkhart Lake SoC pins and using them as GPIOs.
98 of Intel Emmitsburg pins and using them as GPIOs.
[all …]
|
| /linux/sound/soc/atmel/ |
| H A D | Kconfig | 25 tristate "SoC PCM DAI support for AT91 SSC controller using PDC"
31 in PDC mode configured using audio-graph-card in device-tree.
34 tristate "SoC PCM DAI support for AT91 SSC controller using DMA"
40 in DMA mode configured using audio-graph-card in device-tree.
53 tristate "Atmel ASoC driver for boards using WM8904 codec"
59 Say Y if you want to add support for Atmel ASoC driver for boards using
70 at91sam9x5 based board that is using WM8731 codec.
73 tristate "Atmel ASoC driver for boards using CLASSD"
78 Say Y if you want to add support for Atmel ASoC driver for boards using
82 tristate "Atmel ASoC driver for boards using PDMIC"
[all …]
|
| /linux/arch/x86/crypto/ |
| H A D | Kconfig | 13 Architecture: x86_64 using:
30 Architecture: x86 (32-bit and 64-bit) using:
70 Architecture: x86_64 using:
81 Architecture: x86_64 using:
97 Architecture: x86_64 using:
115 Architecture: x86_64 using:
145 Architecture: x86_64 using:
161 Architecture: x86 (32-bit) using:
178 Architecture: x86_64 using:
191 Architecture: x86_64 using:
[all …]
|
| /linux/tools/testing/kunit/test_data/ |
| H A D | test_is_test_passed-no_tests_run_no_header.log | 24 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 …]
|
| H A D | test_output_isolated_correctly.log | 12 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/Documentation/admin-guide/nfs/ |
| H A D | nfsroot.rst | 50 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/arch/arm64/crypto/ |
| H A D | Kconfig | 15 Architecture: arm64 using:
25 Architecture: arm64 using:
36 Architecture: arm64 using:
47 Architecture: arm64 using:
66 Architecture: arm64 using:
85 Architecture: arm64 using:
96 Architecture: arm64 using:
107 Architecture: arm64 using:
118 Architecture: arm64 using:
128 Architecture: arm64 using:
[all …]
|
| /linux/Documentation/driver-api/dmaengine/ |
| H A D | dmatest.rst | 7 This small document introduces how to test DMA drivers using dmatest module.
9 The dmatest module tests DMA memcpy, memset, XOR and RAID6 P+Q operations using
82 Once started a message like " dmatest: Added 1 threads using dma0chan0" is
165 Channels are registered using the "channel" parameter. Channels can be requested by their
171 dmatest: Added 1 threads using dma0chan2
179 dmatest: Added 1 threads using dma0chan1
181 dmatest: Added 1 threads using dma0chan2
191 dmatest: Added 1 threads using dma0chan0
192 dmatest: Added 1 threads using dma0chan3
193 dmatest: Added 1 threads using dma0chan4
[all …]
|
| /linux/sound/soc/sof/intel/ |
| H A D | Kconfig | 50 using the Baytrail, Braswell or Cherrytrail processors.
70 using the Broadwell processors.
94 using the Tangier/Merrifield processors.
108 This adds support for the Intel(R) platforms using the SkyLake processors.
118 This adds support for the Intel(R) platforms using the KabyLake processors.
135 using the Apollolake processors.
145 using the Geminilake processors.
162 using the Cannonlake processors.
172 using the Coffeelake processors.
182 using the Cometlake processors.
[all …]
|
| /linux/sound/soc/tegra/ |
| H A D | Kconfig | 194 tristate "SoC Audio support for Tegra boards using an RT5631 codec"
200 boards using the RT5631 codec, such as Transformer.
203 tristate "SoC Audio support for Tegra boards using an RT5640 codec"
209 boards using the RT5640 codec, such as Dalmore.
212 tristate "SoC Audio support for Tegra boards using a WM8753 codec"
218 boards using the WM8753 codec, such as Whistler.
221 tristate "SoC Audio support for Tegra boards using a WM8903 codec"
227 boards using the WM8093 codec. Currently, the supported boards are
231 tristate "SoC Audio support for Tegra boards using a WM9712 codec"
238 boards using the WM9712 (or compatible) codec.
[all …]
|
| /linux/Documentation/devicetree/bindings/sound/ |
| H A D | realtek,rt5659.yaml | 64 - 1 # using IN2N pin as dmic1 data pin
65 - 2 # using GPIO5 pin as dmic1 data pin
66 - 3 # using GPIO9 pin as dmic1 data pin
67 - 4 # using GPIO11 pin as dmic1 data pin
75 - 1 # using IN2P pin as dmic2 data pin
76 - 2 # using GPIO6 pin as dmic2 data pin
77 - 3 # using GPIO10 pin as dmic2 data pin
78 - 4 # using GPIO12 pin as dmic2 data pin
86 - 1 # using JD3 as JD source
|
| /linux/Documentation/core-api/ |
| H A D | xarray.rst | 22 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().
55 entries can be explicitly split into smaller entries. Unsetting (using
67 You can then set entries using xa_store() and get entries using
70 using xa_erase() or by setting the entry to ``NULL`` using xa_store().
76 You can conditionally replace an entry at an index by using
107 Using xa_insert() on a reserved entry will fail.
115 entries in the XArray using th
[all...] |
| /linux/arch/arm/crypto/ |
| H A D | Kconfig | 27 Architecture: arm using
44 Architecture: arm using:
54 Architecture: arm optionally using
77 Architecture: arm using
104 Architecture: arm using
115 Architecture: arm using ARMv8 Crypto Extensions
125 Architecture: arm using
135 Architecture: arm using
145 Architecture: arm using
211 Architecture: arm using:
[all …]
|
| /linux/Documentation/dev-tools/ |
| H A D | autofdo.rst | 4 Using AutoFDO with the Linux kernel
7 This enables AutoFDO build support for the kernel when using
11 frequency of execution of various code paths within a binary using
20 AutoFDO profiles are created by converting hardware sampling using
30 instance, using the profile generated on Intel architecture to build
34 (1) Sample real workloads using a production environment.
35 (2) Generate the profile using a representative load test.
43 One can collect profiles using AutoFDO build for the previous kernel.
56 collected using hardware sampling, via perf. AutoFDO is most
121 event period. We suggest using a suitable prime number, like 500009,
[all …]
|
| /linux/tools/perf/pmu-events/arch/s390/cf_z16/ |
| H A D | pai_crypto.json | 727 "BriefDescription": "PCC COMPUTE LAST BLOCK CMAC USING DEA",
728 "PublicDescription": "PCC-Compute-Last-Block-CMAC-Using-DEA function ending with CC=0"
734 "BriefDescription": "PCC COMPUTE LAST BLOCK CMAC USING TDEA 128",
735 "PublicDescription": "PCC-Compute-Last-Block-CMAC-Using-TDEA-128 function ending with CC=0"
741 "BriefDescription": "PCC COMPUTE LAST BLOCK CMAC USING TDEA 192",
742 "PublicDescription": "PCC-Compute-Last-Block-CMAC-Using-TDEA-192 function ending with CC=0"
748 "BriefDescription": "PCC COMPUTE LAST BLOCK CMAC USING ENCRYPTED DEA",
749 "PublicDescription": "PCC-Compute-Last-Block-CMAC-Using-Encrypted-DEA function ending with CC=0"
755 "BriefDescription": "PCC COMPUTE LAST BLOCK CMAC USING ENCRYPTED TDEA 128",
756 …"PublicDescription": "PCC-Compute-Last-Block-CMAC-Using-Encrypted-TDEA- 128 function ending with C…
[all …]
|
| /linux/net/dsa/ |
| H A D | Kconfig | 38 tristate "Tag driver for Broadcom switches using in-frame headers"
45 tristate "Tag driver for Broadcom legacy switches using in-frame headers"
53 tristate "Tag driver for Broadcom switches using prepended headers"
76 tristate "Tag driver for Marvell switches using DSA headers"
83 tristate "Tag driver for Marvell switches using EtherType DSA headers"
102 tristate "Tag driver for Ocelot family of switches, using NPI port"
113 tristate "Tag driver for Ocelot family of switches, using VLAN"
118 Flow control over the CPU port is functional in this mode. When using
164 tristate "Tag driver for switches using a trailer tag"
170 tristate "Tag driver for Microchip/Vitesse VSC73xx family of switches, using VLAN"
|
| /linux/arch/riscv/crypto/ |
| H A D | Kconfig | 15 Architecture: riscv64 using:
29 Architecture: riscv64 using:
39 Architecture: riscv64 using:
49 Architecture: riscv64 using:
60 Architecture: riscv64 using:
72 Architecture: riscv64 using:
89 Architecture: riscv64 using:
|
| /linux/Documentation/hid/ |
| H A D | hidraw.rst | 19 communication with these non-conformant devices is impossible using hiddev.
45 devices, the reports read using read() are the reports sent from the device
48 the O_NONBLOCK flag to open(), or by setting the O_NONBLOCK flag using
61 using a SET_REPORT transfer.
79 This ioctl returns the device's report descriptor using a
115 specification, feature reports are always sent using the control endpoint.
124 This ioctl will request a feature report from the device using the control
135 This ioctl will send an input report to the device, using the control endpoint.
144 This ioctl will request an input report from the device using the control
155 This ioctl will send an output report to the device, using the control endpoint.
[all …]
|
| /linux/lib/zstd/common/ |
| H A D | fse.h | 62 … if FSE_isError(return), compression failed (more details using FSE_getErrorName())
71 or an error code, which can be tested using FSE_isError() .
112 3. save normalized counters to memory buffer using writeNCount()
114 5. encode the data stream using encoding table 'CTable'
119 3. decode the data stream using decoding table 'DTable'
122 For example, it's possible to compress several blocks using the same 'CTable',
123 or to save and provide normalized distribution using external method.
130 … It saves CPU time, by using smaller tables, while preserving or even improving compression ratio.
144 or an errorCode, which can be tested using FSE_isError() */
156 or an errorCode, which can be tested using FSE_isError(). */
[all …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | selection-api-configuration.rst | 19 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/Documentation/driver-api/gpio/ |
| H A 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
59 of wires, at least SCK and optionally MISO, MOSI and chip select lines) using
63 to this SPI by using the mmc_spi host from the MMC/SD card subsystem.
65 - w1-gpio: drivers/w1/masters/w1-gpio.c is used to drive a one-wire bus using
94 Consumer Electronics Control bus using only GPIO. It is used to communicate
99 AC charger or more complex tasks such as indicating charging status using
104 - gpio-mux: drivers/mux/gpio.c is used for controlling a multiplexer using
112 to emulate MCTRL (modem control) signals CTS/RTS by using two GPIO lines. The
[all …]
|
| /linux/Documentation/misc-devices/ |
| H A D | xilinx_sdfec.rst | 128 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/net/netlabel/ |
| H A 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/Documentation/networking/ |
| H A D | iso15765-2.rst | 17 CAN network using SAE J1939 as data link layer (however, this is not a
53 When transmitting data using the ISO-TP protocol, the payload can either fit
56 is transmitted at once using a so-called Single Frame (SF). In the second case,
78 socket can then be created using the ``PF_CAN`` protocol family, the
95 Once bound to an interface, the socket can be read from and written to using
99 is sent and received by the userspace application using these calls. The address
101 stack using the configuration supplied during socket creation. In the same way,
136 General socket options can be passed using the ``CAN_ISOTP_OPTS`` optname:
167 * ``CAN_ISOTP_TX_PADDING``: enable padding for transmitted frames, using
170 * ``CAN_ISOTP_RX_PADDING``: enable padding for the received frames, using
[all …]
|
| /linux/tools/perf/pmu-events/arch/powerpc/power9/ |
| H A D | pipeline.json | 35 …different Node or Group (Distant) due to a marked data side request. When using Radix Page Transla…
40 …LB from local core's L2 without conflict due to a data side request. When using Radix Page Transla…
80 …nother core's L2 on the same chip due to a marked data side request. When using Radix Page Transla…
95 … from another core's L2 on the same chip due to a data side request. When using Radix Page Transla…
115 …atch conflicts hit on Mepf state. due to a marked data side request. When using Radix Page Transla…
160 …ifferent chip (remote or distant) due to a marked data side request. When using Radix Page Transla…
175 …m local core's L3 with dispatch conflict due to a data side request. When using Radix Page Transla…
180 … local core's L2 without conflict due to a marked data side request. When using Radix Page Transla…
225 … local core's L3 without conflict due to a marked data side request. When using Radix Page Transla…
250 …ame Node or Group (Remote), as this chip due to a data side request. When using Radix Page Transla…
[all …]
|