Searched refs:configurations (Results 1 – 25 of 282) sorted by relevance
12345678910>>...12
/linux-6.3-rc2/Documentation/xtensa/ |
A 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-6.3-rc2/Documentation/usb/ |
A D | gadget_configfs.rst | 24 Creating a gadget means deciding what configurations there will be 103 2. Creating the configurations 155 4. Associating the functions with their configurations 161 function can be used in multiple configurations). This is achieved with 178 configurations and functions. 236 Remove functions from configurations:: 249 Remove strings directories in configurations: 261 and remove the configurations:: 378 2. The user creates configurations and functions, in the configurations 382 all configurations, and in each configuration it iterates over all [all …]
|
/linux-6.3-rc2/Documentation/ABI/testing/ |
A D | sysfs-bus-iio-magnetometer-hmc5843 | 6 Current configuration and available configurations 10 normal Normal measurement configurations (default)
|
A D | sysfs-bus-coresight-devices-tpdm | 8 sure that the trace path is enabled and the link configurations
|
A D | sysfs-platform-intel-pmc | 10 is required in order for manufacturing configurations
|
/linux-6.3-rc2/Documentation/devicetree/bindings/net/ |
A 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 67 This will allow easy support for configurations that support multiple PHY
|
/linux-6.3-rc2/Documentation/arm/pxa/ |
A 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-6.3-rc2/Documentation/trace/coresight/ |
A D | coresight-config.rst | 14 programming of the CoreSight system with pre-defined configurations that 20 be defined and enabled as named configurations. 136 The set of configurations and features that are currently loaded into the 148 configurations features 153 $ cd configurations/ 212 The configurations loaded into the CoreSight configuration management are 240 When configurations are selected in this way, then the trace sink used is 253 $ cd configurations/autofdo 280 Custom configurations and / or features can be dynamically loaded into the
|
/linux-6.3-rc2/arch/arm/mach-s3c/ |
A D | Kconfig.s3c64xx | 85 Common setup code for S3C64XX KEYPAD GPIO configurations 90 Common setup code for S3C64XX SDHCI GPIO configurations 95 Common setup code for SPI GPIO configurations
|
/linux-6.3-rc2/Documentation/devicetree/bindings/pinctrl/ |
A 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-6.3-rc2/arch/mips/generic/ |
A D | board-luton.its.S | 16 configurations {
|
A D | board-boston.its.S | 15 configurations {
|
A D | board-marduk.its.S | 15 configurations {
|
A D | board-ni169445.its.S | 15 configurations {
|
A D | board-serval.its.S | 16 configurations {
|
A D | board-xilfpga.its.S | 15 configurations {
|
A D | board-jaguar2.its.S | 26 configurations {
|
A D | board-ocelot.its.S | 27 configurations {
|
A D | vmlinux.its.S | 24 configurations {
|
/linux-6.3-rc2/drivers/usb/typec/altmodes/ |
A D | displayport.c | 333 static const char * const configurations[] = { variable 349 con = sysfs_match_string(configurations, buf); in configuration_store() 401 for (i = 1; i < ARRAY_SIZE(configurations); i++) { in configuration_show() 403 len += sprintf(buf + len, "[%s] ", configurations[i]); in configuration_show() 406 len += sprintf(buf + len, "%s ", configurations[i]); in configuration_show()
|
/linux-6.3-rc2/Documentation/devicetree/bindings/mfd/ |
A D | brcm,iproc-cdru.txt | 4 chip specific device and resource configurations. This node allows access to
|
/linux-6.3-rc2/Documentation/admin-guide/ |
A D | pstore-blk.rst | 20 divides all configurations into two parts, configurations for user and 21 configurations for driver. 33 All of these configurations support both Kconfig and module parameters, but 40 The detail of each configurations may be of interest to you.
|
/linux-6.3-rc2/Documentation/devicetree/bindings/arm/ |
A D | arm,coresight-tmc.yaml | 24 FIFO(ETF) and Embedded Trace Router(ETR) configurations. The configuration 101 and ETF configurations.
|
/linux-6.3-rc2/kernel/bpf/preload/ |
A D | Kconfig | 11 # in allmodconfig or allyesconfig configurations
|
/linux-6.3-rc2/drivers/gpu/drm/i915/ |
A D | Kconfig.unstable | 8 # allmodconfig or allyesconfig configurations
|
Completed in 26 milliseconds
12345678910>>...12