Searched full:configurations (Results 1 – 25 of 1544) sorted by relevance
12345678910>>...62
| /kernel/linux/linux-4.19/arch/arm/mach-imx/ |
| D | Kconfig | 92 configurations for the board and its peripherals.
107 configurations for the board and its peripherals.
127 configurations for the board and its peripherals.
143 This includes specific configurations for the board and its
163 includes specific configurations for the module and its peripherals.
187 configurations for the board and its peripherals.
209 specific configurations for the board and its peripherals.
225 configurations for the board and its peripherals.
242 specific configurations for the board and its peripherals.
272 configurations for the board and its peripherals.
[all …]
|
| /kernel/linux/linux-4.19/include/linux/mfd/wm8994/ |
| D | pdata.h | 41 * DRC configurations are specified with a label and a set of register
46 * Configurations may be generated by hand or by using the DRC control
56 * ReTune Mobile configurations are specified with a label, sample
59 * Configurations are expected to be generated using the ReTune Mobile
69 * Multiband compressor configurations are specified with a label and
70 * two sets of values to write. Configurations are expected to be
84 * VSS HPF configurations are specified with a label and two values to
85 * write. Configurations are expected to be generated using the
95 * VSS configurations are specified with a label and array of values
96 * to write. Configurations are expected to be generated using the
[all …]
|
| /kernel/linux/linux-5.10/include/linux/mfd/wm8994/ |
| D | pdata.h | 33 * DRC configurations are specified with a label and a set of register
38 * Configurations may be generated by hand or by using the DRC control
48 * ReTune Mobile configurations are specified with a label, sample
51 * Configurations are expected to be generated using the ReTune Mobile
61 * Multiband compressor configurations are specified with a label and
62 * two sets of values to write. Configurations are expected to be
76 * VSS HPF configurations are specified with a label and two values to
77 * write. Configurations are expected to be generated using the
87 * VSS configurations are specified with a label and array of values
88 * to write. Configurations are expected to be generated using the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/usb/ |
| D | gadget_configfs.rst | 18 A gadget is seen by its host as a set of configurations, each of which contains
24 Creating a gadget means deciding what configurations there will be
93 2. Creating the configurations
96 Each gadget will consist of a number of configurations, their corresponding
145 4. Associating the functions with their configurations
149 configurations specified and a number of functions available. What remains
151 function can be used in multiple configurations). This is achieved with
168 configurations and functions.
226 Remove functions from configurations::
239 Remove strings directories in configurations:
[all …]
|
| /kernel/linux/linux-4.19/Documentation/usb/ |
| D | gadget_configfs.txt | 20 A gadget is seen by its host as a set of configurations, each of which contains
26 Creating a gadget means deciding what configurations there will be
93 2. Creating the configurations
96 Each gadget will consist of a number of configurations, their corresponding
145 4. Associating the functions with their configurations
149 configurations specified and a number of functions available. What remains
151 function can be used in multiple configurations). This is achieved with
168 configurations and functions.
222 Remove functions from configurations:
235 Remove strings directories in configurations
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/ |
| D | snps,dwc-qos-ethernet.txt | 10 configurations.
29 In some configurations (e.g. GMII/RGMII), this clock also drives the PHY TX
30 path. In other configurations, other clocks (such as tx_125, rmii) may
34 In some configurations (e.g. GMII/RGMII), this clock is derived from the
35 PHY's RX clock output. In other configurations, other clocks (such as
47 The master bus interface clock. Only required in configurations that use a
59 Note: Support for additional IP configurations may require adding the
62 Configurations exist where multiple similar clocks are used at once, e.g. all
67 This will allow easy support for configurations that support multiple PHY
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/net/ |
| D | snps,dwc-qos-ethernet.txt | 10 configurations.
29 In some configurations (e.g. GMII/RGMII), this clock also drives the PHY TX
30 path. In other configurations, other clocks (such as tx_125, rmii) may
34 In some configurations (e.g. GMII/RGMII), this clock is derived from the
35 PHY's RX clock output. In other configurations, other clocks (such as
47 The master bus interface clock. Only required in configurations that use a
59 Note: Support for additional IP configurations may require adding the
62 Configurations exist where multiple similar clocks are used at once, e.g. all
67 This will allow easy support for configurations that support multiple PHY
|
| /kernel/linux/linux-5.10/Documentation/xtensa/ |
| D | booting.rst | 11 - For configurations without MMU, with region protection or with MPU the
13 - For configurations with region translarion MMU or with MMUv3 and CONFIG_MMU=n
16 - For configurations with MMUv2 the address must be a virtual address in the
18 - For configurations with MMUv3 and CONFIG_MMU=y the address may be either a
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | pstore-blk.rst | 20 divides all configurations into two parts, configurations for user and
21 configurations for driver.
23 Configurations for user determine how pstore/blk works, such as pmsg_size,
27 Configurations for driver are all about block device and non-block device,
30 Configurations for user
33 All of these configurations support both Kconfig and module parameters, but
40 The detail of each configurations may be of interest to you.
151 Configurations for driver
154 Only a block device driver cares about these configurations. A block device
|
| /kernel/linux/linux-4.19/Documentation/arm/pxa/ |
| D | mfp.txt | 14 out of the GPIO controller. In addition to pin-mux configurations, the MFP
93 NOTE: PXA300 and PXA310 are almost identical in pin configurations (with
97 2. prepare an array for the initial pin configurations, e.g.:
121 a) once the pin configurations are passed to pxa{2xx,3xx}_mfp_config(),
125 b) when there is only one possible pin configurations for a component,
193 configurations, these definitions are processor and platform independent, and
209 configurations
213 for PXA2xx specific definitions and PXA25x/PXA27x common pin configurations
262 Examples of pin configurations are:
|
| /kernel/linux/linux-5.10/Documentation/arm/pxa/ |
| D | mfp.rst | 16 out of the GPIO controller. In addition to pin-mux configurations, the MFP
95 NOTE: PXA300 and PXA310 are almost identical in pin configurations (with
99 2. prepare an array for the initial pin configurations, e.g.::
123 a) once the pin configurations are passed to pxa{2xx,3xx}_mfp_config(),
127 b) when there is only one possible pin configurations for a component,
195 configurations, these definitions are processor and platform independent, and
211 configurations
215 for PXA2xx specific definitions and PXA25x/PXA27x common pin configurations
264 Examples of pin configurations are::
|
| /kernel/linux/linux-5.10/tools/power/cpupower/man/ |
| D | cpupower-set.1 | 3 cpupower\-set \- Set processor power related kernel or hardware configurations
10 \fBcpupower set \fP sets kernel configurations or directly accesses hardware
14 are applied on all cores. How to modify single core configurations is
|
| D | cpupower-info.1 | 3 cpupower\-info \- Shows processor power related kernel or hardware configurations
9 \fBcpupower info \fP shows kernel configurations or processor hardware
|
| /kernel/linux/linux-4.19/tools/power/cpupower/man/ |
| D | cpupower-set.1 | 3 cpupower\-set \- Set processor power related kernel or hardware configurations
10 \fBcpupower set \fP sets kernel configurations or directly accesses hardware
14 are applied on all cores. How to modify single core configurations is
|
| D | cpupower-info.1 | 3 cpupower\-info \- Shows processor power related kernel or hardware configurations
9 \fBcpupower info \fP shows kernel configurations or processor hardware
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/pinctrl/ |
| D | fsl,mxs-pinctrl.txt | 27 configurations, and it's called group node in the binding document. The other
39 there to adjust configurations for some pins in the group.
52 since config node is only meant to set up pin configurations.
118 to function as a 8-bit mmc device, with 8mA, 3.3V and pull-up configurations
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | fsl,mxs-pinctrl.txt | 27 configurations, and it's called group node in the binding document. The other
39 there to adjust configurations for some pins in the group.
52 since config node is only meant to set up pin configurations.
118 to function as a 8-bit mmc device, with 8mA, 3.3V and pull-up configurations
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/intel/ |
| D | igbvf.rst | 13 - Additional Configurations
29 Configurations later in this document.
41 Additional Features and Configurations
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-magnetometer-hmc5843 | 6 Current configuration and available configurations
8 normal - Normal measurement configurations (default)
|
| /kernel/linux/linux-4.19/drivers/crypto/ccree/ |
| D | cc_aead.h | 72 /* buffer for internal ccm configurations */
77 /* buffer for internal gcm configurations */
79 /* buffer for internal gcm configurations */
|
| /kernel/linux/linux-4.19/Documentation/networking/ |
| D | igbvf.txt | 11 - Additional Configurations
34 Configurations" later in this document.
55 Additional Configurations
|
| /kernel/linux/linux-5.10/drivers/crypto/ccree/ |
| D | cc_aead.h | 71 /* buffer for internal ccm configurations */
76 /* buffer for internal gcm configurations */
78 /* buffer for internal gcm configurations */
|
| /kernel/linux/linux-5.10/include/sound/ |
| D | wm8904.h | 120 * DRC configurations are specified with a label and a set of register
125 * Configurations may be generated by hand or by using the DRC control
135 * ReTune Mobile configurations are specified with a label, sample
138 * Configurations are expected to be generated using the ReTune Mobile
|
| /kernel/linux/linux-4.19/include/sound/ |
| D | wm8904.h | 125 * DRC configurations are specified with a label and a set of register
130 * Configurations may be generated by hand or by using the DRC control
140 * ReTune Mobile configurations are specified with a label, sample
143 * Configurations are expected to be generated using the ReTune Mobile
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-magnetometer-hmc5843 | 6 Current configuration and available configurations
10 normal Normal measurement configurations (default)
|
12345678910>>...62