Searched refs:configurations (Results 1 – 25 of 269) sorted by relevance
1234567891011
| /linux-5.19.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 …]
|
| /linux-5.19.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
|
| /linux-5.19.10/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-magnetometer-hmc5843 | 6 Current configuration and available configurations
10 normal Normal measurement configurations (default)
|
| /linux-5.19.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
67 This will allow easy support for configurations that support multiple PHY
|
| D | apm-xgene-mdio.txt | 26 /* Board-specific peripheral configurations */
|
| /linux-5.19.10/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.
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-5.19.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::
|
| /linux-5.19.10/Documentation/devicetree/bindings/pinctrl/ |
| 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
|
| 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-5.19.10/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()
|
| /linux-5.19.10/arch/mips/generic/ |
| D | board-luton.its.S | 16 configurations {
|
| D | board-marduk.its.S | 15 configurations {
|
| D | board-serval.its.S | 16 configurations {
|
| D | board-xilfpga.its.S | 15 configurations {
|
| D | board-boston.its.S | 15 configurations {
|
| D | board-ni169445.its.S | 15 configurations {
|
| D | board-jaguar2.its.S | 26 configurations {
|
| D | board-ocelot.its.S | 27 configurations {
|
| D | vmlinux.its.S | 24 configurations {
|
| /linux-5.19.10/Documentation/devicetree/bindings/pwm/ |
| D | nvidia,tegra20-pwm.txt | 33 pinctrl-0: phandle for the default/active state of pin configurations.
34 pinctrl-1: phandle for the sleep state of pin configurations.
|
| /linux-5.19.10/Documentation/devicetree/bindings/mfd/ |
| D | brcm,iproc-cdru.txt | 4 chip specific device and resource configurations. This node allows access to
|
| /linux-5.19.10/Documentation/admin-guide/ |
| 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-5.19.10/kernel/bpf/preload/ |
| D | Kconfig | 11 # in allmodconfig or allyesconfig configurations
|
| /linux-5.19.10/drivers/gpu/drm/i915/ |
| D | Kconfig.unstable | 8 # allmodconfig or allyesconfig configurations
|
| /linux-5.19.10/Documentation/devicetree/bindings/phy/ |
| D | brcm,ns2-drd-phy.txt | 8 icfg - for DRD ICFG configurations
|
1234567891011