/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-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-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-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-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
|
D | nvidia,tegra124-dpaux-padctl.txt | 17 Child nodes contain the pinmux configurations following the conventions 20 Since only three configurations are possible, only three child nodes are
|
/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
|
D | fm10k.rst | 13 - Additional Configurations 57 Additional Features and Configurations 95 other protocols besides TCP. It's also safe to use with configurations that 103 Retrieves the receive network flow classification 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
|
D | wm8996.h | 19 * ReTune Mobile configurations are specified with a label, sample 22 * 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)
|
/kernel/linux/linux-5.10/drivers/dma/ti/ |
D | k3-psil-priv.h | 19 * @src: Array of source PSI-L thread configurations 21 * @dst: Array of destination PSI-L thread configurations
|
/kernel/linux/linux-5.10/arch/arm/mach-omap2/ |
D | opp2430_data.c | 10 * The OMAP2 processor can be run at several discrete 'PRCM configurations'. 11 * These configurations are characterized by voltage and speed for clocks. 15 * setting. All configurations can be described by a DPLL setting and a ratio.
|
D | opp2420_data.c | 10 * The OMAP2 processor can be run at several discrete 'PRCM configurations'. 11 * These configurations are characterized by voltage and speed for clocks. 15 * setting. All configurations can be described by a DPLL setting and a ratio.
|
/kernel/linux/linux-5.10/arch/xtensa/ |
D | Kconfig | 50 architecture supports all processor configurations and extensions, 481 Linux configurations it seems reasonable to just assume they exist 572 It is virtual address for MMUv2 configurations and physical address 573 for all other configurations. 583 configurations without VECBASE register where vectors are always 592 This is a safe choice for most configurations. 631 in noMMU configurations.
|
/kernel/linux/linux-5.10/arch/arm/mach-s3c/ |
D | Kconfig.s3c64xx | 93 Common setup code for S3C64XX KEYPAD GPIO configurations 98 Common setup code for S3C64XX SDHCI GPIO configurations 103 Common setup code for SPI GPIO configurations
|
/kernel/linux/linux-5.10/drivers/usb/typec/altmodes/ |
D | displayport.c | 320 static const char * const configurations[] = { variable 336 con = sysfs_match_string(configurations, buf); in configuration_store() 388 for (i = 1; i < ARRAY_SIZE(configurations); i++) { in configuration_show() 390 len += sprintf(buf + len, "[%s] ", configurations[i]); in configuration_show() 393 len += sprintf(buf + len, "%s ", configurations[i]); in configuration_show() 526 /* Make sure we have compatiple pin configurations */ in dp_altmode_probe()
|
/kernel/linux/linux-5.10/Documentation/mhi/ |
D | mhi.rst | 32 MHI control registers: Access to MHI configurations registers 55 Channel context array: All channel configurations are organized in channel 61 Event context array: All event configurations are organized in the event context 67 Command context array: All command configurations are organized in command
|
/kernel/linux/linux-5.10/include/linux/mfd/ |
D | rohm-bd718x7.h | 29 /* Common voltage configurations */ 39 /* BD71837 specific voltage configurations */ 46 /* BD71847 specific voltage configurations */
|
/kernel/liteos_m/arch/risc-v/nuclei/gcc/nmsis/Core/Include/ |
D | core_feature_pmp.h | 158 * pmpcfg0 and pmpcfg2 hold the configurations 160 * - For RV32, pmpcfg0–pmpcfg3, hold the configurations 181 * pmpcfg0 and pmpcfg2 hold the configurations 183 * - For RV32, pmpcfg0–pmpcfg3, hold the configurations
|