/Linux-v6.1/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 …]
|
/Linux-v6.1/Documentation/trace/coresight/ |
D | coresight-config.rst | 14 programming of the CoreSight system with pre-defined configurations that 20 be defined and enabled as named configurations. 73 Configurations section in Basic Concepts 133 Viewing Configurations and Features 136 The set of configurations and features that are currently loaded into the 148 configurations features 153 $ cd configurations/ 209 Using Configurations in perf 212 The configurations loaded into the CoreSight configuration management are 240 When configurations are selected in this way, then the trace sink used is [all …]
|
/Linux-v6.1/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 …]
|
/Linux-v6.1/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
|
/Linux-v6.1/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
|
/Linux-v6.1/drivers/hwtracing/coresight/ |
D | coresight-syscfg.h | 18 * When unloading configurations cannot be activated. 29 * Contains lists of the loaded configurations and features, plus a list of CoreSight devices 39 * @load_order_list: Ordered list of owners for dynamically loaded configurations. 41 * @cfgfs_subsys: configfs subsystem used to manage configurations. 86 * unload of configurations and features. Caller loading a config
|
D | coresight-syscfg.c | 16 * cscfg_ API manages configurations and features for the entire coresight 19 * It allows the loading of configurations and features, and loads these into 502 /* next any configurations to check feature dependencies */ in cscfg_load_owned_cfgs_feats() 518 /* set configurations as available to activate at the end of the load process */ 532 * Create and register each of the configurations and features with configfs. 564 * To facilitate dynamic loading and unloading, features and configurations 567 * As later loaded configurations can use earlier loaded features, creating load 642 * cscfg_unload_config_sets - unload a set of configurations by owner. 645 * the load owner of that set. Later loaded configurations can depend on 649 * 1) no configurations are active. [all …]
|
/Linux-v6.1/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. 154 Configurations for driver
|
/Linux-v6.1/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::
|
/Linux-v6.1/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
|
/Linux-v6.1/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
|
/Linux-v6.1/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.
|
/Linux-v6.1/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 */
|
/Linux-v6.1/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
|
/Linux-v6.1/arch/xtensa/ |
D | Kconfig | 59 architecture supports all processor configurations and extensions, 191 Handle protection faults. MMU configurations must enable it. 192 noMMU configurations may disable it if used memory map never 569 Linux configurations it seems reasonable to just assume they exist 660 It is virtual address for MMUv2 configurations and physical address 661 for all other configurations. 671 configurations without VECBASE register where vectors are always 680 This is a safe choice for most configurations. 719 in noMMU configurations.
|
/Linux-v6.1/Documentation/ABI/testing/ |
D | sysfs-bus-iio-magnetometer-hmc5843 | 6 Current configuration and available configurations 10 normal Normal measurement configurations (default)
|
/Linux-v6.1/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
|
/Linux-v6.1/arch/arm/mach-omap2/ |
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.
|
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.
|
/Linux-v6.1/arch/arm/mach-s3c/ |
D | Kconfig.s3c64xx | 97 Common setup code for S3C64XX KEYPAD GPIO configurations 102 Common setup code for S3C64XX SDHCI GPIO configurations 107 Common setup code for SPI GPIO configurations
|
/Linux-v6.1/drivers/usb/typec/altmodes/ |
D | displayport.c | 330 static const char * const configurations[] = { variable 346 con = sysfs_match_string(configurations, buf); in configuration_store() 398 for (i = 1; i < ARRAY_SIZE(configurations); i++) { in configuration_show() 400 len += sprintf(buf + len, "[%s] ", configurations[i]); in configuration_show() 403 len += sprintf(buf + len, "%s ", configurations[i]); in configuration_show() 531 /* Make sure we have compatiple pin configurations */ in dp_altmode_probe()
|
/Linux-v6.1/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
|