Searched refs:configuration (Results 1 – 25 of 1514) sorted by relevance
12345678910>>...61
| /Linux-v6.1/Documentation/trace/coresight/ |
| D | coresight-config.rst | 26 This section introduces the basic concepts of a CoreSight system configuration.
38 CoreSight device is registered with the configuration manager.
49 A feature is enabled as part of a configuration being enabled on the system.
76 A configuration defines a set of features that are to be used in a trace
77 session where the configuration is selected. For any trace session only one
78 configuration may be selected.
81 to support system configuration. A configuration may select features to be
85 As with the feature, a descriptor is used to define the configuration.
86 This will define the features that must be enabled as part of the configuration
95 that the configuration uses. The number of values in a single preset set, equals
[all …]
|
| /Linux-v6.1/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-bindings.txt | 3 Hardware modules that control pin multiplexing or configuration parameters
8 Hardware modules whose signals are affected by pin configuration are
14 single static pin configuration, e.g. set up during initialization. Others
22 configuration used by those states.
26 driver loads. This would allow representing a board's static pin configuration
31 they require certain specific named states for dynamic pin configuration.
37 property exists to define the pin configuration. Each state may also be
47 pinctrl-0: List of phandles, each pointing at a pin configuration
48 node. These referenced pin configuration nodes must be child
53 contributing part of the overall configuration. See the next
[all …]
|
| D | sprd,pinctrl.txt | 7 to configure for some global common configuration, such as domain
15 There are too much various configuration that we can not list all
16 of them, so we can not make every Spreadtrum-special configuration
17 as one generic configuration, and maybe it will add more strange
18 global configuration in future. Then we add one "sprd,control" to
19 set these various global control configuration, and we need use
30 configuration.
34 related configuration are:
43 configuration, to set the pin sleep related configuration automatically
46 and set the pin sleep related configuration as "input-enable", which
|
| D | qcom,apq8064-pinctrl.txt | 24 phrase "pin configuration node".
26 Qualcomm's pin configuration nodes act as a container for an arbitrary number of
27 subnodes. Each of these subnodes represents some desired configuration for a
28 pin, a group, or a list of pins or groups. This configuration can include the
29 mux function to select on those pin(s)/group(s), and various pin configuration
36 other words, a subnode that lists a mux function but no pin configuration
37 parameters implies no information about any pin configuration parameters.
43 to specify in a pin configuration subnode:
|
| D | ste,nomadik.txt | 12 phrase "pin configuration node".
14 ST Ericsson's pin configuration nodes act as a container for an arbitrary number of
15 subnodes. Each of these subnodes represents some desired configuration for a
16 pin, a group, or a list of pins or groups. This configuration can include the
17 mux function to select on those pin(s)/group(s), and various pin configuration
32 Required pin configuration subnode properties:
33 - pins: A string array describing the pins affected by the configuration
35 - ste,config: Handle of pin configuration node
56 3: sleep input and keep last input configuration (no pull, pull up or pull down).
|
| D | oxnas,pinctrl.txt | 7 OXNAS 'pin configuration node' is a node of a group of pins which can be
9 pins, optional function, and optional mux related configuration.
15 Required properties for pin configuration sub-nodes:
16 - pins: List of pins to which the configuration applies.
18 Optional properties for pin configuration sub-nodes:
|
| D | qcom,ipq4019-pinctrl.txt | 27 phrase "pin configuration node".
29 The pin configuration nodes act as a container for an arbitrary number of
30 subnodes. Each of these subnodes represents some desired configuration for a
31 pin, a group, or a list of pins or groups. This configuration can include the
32 mux function to select on those pin(s)/group(s), and various pin configuration
39 other words, a subnode that lists a mux function but no pin configuration
40 parameters implies no information about any pin configuration parameters.
46 to specify in a pin configuration subnode:
|
| D | qcom,msm8660-pinctrl.txt | 24 phrase "pin configuration node".
26 Qualcomm's pin configuration nodes act as a container for an arbitrary number of
27 subnodes. Each of these subnodes represents some desired configuration for a
28 pin, a group, or a list of pins or groups. This configuration can include the
29 mux function to select on those pin(s)/group(s), and various pin configuration
36 other words, a subnode that lists a mux function but no pin configuration
37 parameters implies no information about any pin configuration parameters.
43 to specify in a pin configuration subnode:
|
| D | qcom,ipq8064-pinctrl.txt | 24 phrase "pin configuration node".
26 Qualcomm's pin configuration nodes act as a container for an arbitrary number of
27 subnodes. Each of these subnodes represents some desired configuration for a
28 pin, a group, or a list of pins or groups. This configuration can include the
29 mux function to select on those pin(s)/group(s), and various pin configuration
36 other words, a subnode that lists a mux function but no pin configuration
37 parameters implies no information about any pin configuration parameters.
43 to specify in a pin configuration subnode:
|
| D | fsl,imx-pinctrl.txt | 12 phrase "pin configuration node".
14 Freescale IMX pin configuration node is a node of a group of pins which can be
24 Required properties for pin configuration node:
48 2. The pin configuration node intends to work on a specific function should
51 this group of pins in this pin configuration node are working on.
52 3. The driver can use the function node's name and pin configuration node's
55 as the function name and pin configuration node's name as group name to
57 4. Each pin configuration node should have a phandle, devices can set pins
58 configurations by referring to the phandle of that pin configuration node.
|
| D | lantiq,pinctrl-falcon.txt | 10 phrase "pin configuration node".
12 Lantiq's pin configuration nodes act as a container for an arbitrary number of
13 subnodes. Each of these subnodes represents some desired configuration for a
14 pin, a group, or a list of pins or groups. This configuration can include the
15 mux function to select on those group(s), and two pin configuration parameters:
22 other words, a subnode that lists a mux function but no pin configuration
23 parameters implies no information about any pin configuration parameters.
|
| D | microchip,pic32-pinctrl.txt | 7 PIC32 'pin configuration node' is a node of a group of pins which can be
9 pins, optional function, and optional mux related configuration.
16 Required properties for pin configuration sub-nodes:
17 - pins: List of pins to which the configuration applies.
19 Optional properties for pin configuration sub-nodes:
|
| D | qcom,msm8974-pinctrl.txt | 24 phrase "pin configuration node".
26 Qualcomm's pin configuration nodes act as a container for an arbitrary number of
27 subnodes. Each of these subnodes represents some desired configuration for a
28 pin, a group, or a list of pins or groups. This configuration can include the
29 mux function to select on those pin(s)/group(s), and various pin configuration
36 other words, a subnode that lists a mux function but no pin configuration
37 parameters implies no information about any pin configuration parameters.
43 to specify in a pin configuration subnode:
|
| D | pinctrl-palmas.txt | 4 the configuration for Pull UP/DOWN, open drain etc.
14 phrase "pin configuration node".
16 Palmas's pin configuration nodes act as a container for an arbitrary number of
17 subnodes. Each of these subnodes represents some desired configuration for a
18 list of pins. This configuration can include the mux function to select on
19 those pin(s), and various pin configuration parameters, such as pull-up,
26 other words, a subnode that lists a mux function but no pin configuration
27 parameters implies no information about any pin configuration parameters.
|
| D | qcom,mdm9615-pinctrl.txt | 56 phrase "pin configuration node".
58 The pin configuration nodes act as a container for an arbitrary number of
59 subnodes. Each of these subnodes represents some desired configuration for a
60 pin, a group, or a list of pins or groups. This configuration can include the
61 mux function to select on those pin(s)/group(s), and various pin configuration
71 other words, a subnode that lists a mux function but no pin configuration
72 parameters implies no information about any pin configuration parameters.
78 to specify in a pin configuration subnode:
|
| /Linux-v6.1/Documentation/networking/dsa/ |
| D | b53.rst | 26 The configuration of the device depends on whether or not tagging is
29 The interface names and example network configuration are used according the
30 configuration described in the :ref:`dsa-config-showcases`.
35 The tagging based configuration is desired. It is not specific to the b53
38 See :ref:`dsa-tagged-configuration`.
46 switch need a different configuration.
48 The configuration slightly differ from the :ref:`dsa-vlan-configuration`.
54 In difference to the configuration described in :ref:`dsa-vlan-configuration`
55 the default VLAN 1 has to be removed from the slave interface configuration in
56 single port and gateway configuration, while there is no need to add an extra
[all …]
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-magnetometer-hmc5843 | 6 Current configuration and available configurations
11 positivebias Positive bias configuration
12 negativebias Negative bias configuration
18 The effect of this configuration may vary
|
| D | sysfs-driver-typec-displayport | 1 What: /sys/bus/typec/devices/.../displayport/configuration
5 Shows the current DisplayPort configuration for the connector.
16 The configuration can be changed by writing to the file
18 Note. USB configuration does not equal to Exit Mode. It is
19 separate configuration defined in VESA DisplayPort Alt Mode on
40 possible to set pin assignment before configuration has been
|
| /Linux-v6.1/drivers/accessibility/speakup/ |
| D | Kconfig | 55 or m to build it as a module. See the configuration
64 or m to build it as a module. See the configuration
72 or m to build it as a module. See the configuration
80 build it as a module. See the configuration help on the
88 or m to build it as a module. See the configuration
97 or m to build it as a module. See the configuration
107 configuration help on the Speakup choice above for more
118 a module. See the configuration help on the Speakup
141 configuration help on the Speakup choice above for more
152 configuration help on the Speakup choice above for more
[all …]
|
| /Linux-v6.1/arch/arm/boot/dts/ |
| D | tegra30-asus-tf300t.dts | 153 nvidia,emem-configuration = < 0x00030003 0xc0000020
163 nvidia,emem-configuration = < 0x00010003 0xc0000020
173 nvidia,emem-configuration = < 0x00000003 0xc0000030
183 nvidia,emem-configuration = < 0x00000006 0xc0000025
193 nvidia,emem-configuration = < 0x0000000a 0xc000003d
203 nvidia,emem-configuration = < 0x00000014 0xc0000079
218 nvidia,emem-configuration = < 0x00030003 0xc0000020
228 nvidia,emem-configuration = < 0x00010003 0xc0000020
238 nvidia,emem-configuration = < 0x00000003 0xc0000030
248 nvidia,emem-configuration = < 0x00000006 0xc0000025
[all …]
|
| D | tegra30-asus-tf300tg.dts | 227 nvidia,emem-configuration = < 0x00020001 0xc0000020
237 nvidia,emem-configuration = < 0x00010001 0xc0000020
247 nvidia,emem-configuration = < 0x00000001 0xc0000030
257 nvidia,emem-configuration = < 0x00000003 0xc0000025
267 nvidia,emem-configuration = < 0x00000005 0xc000003d
277 nvidia,emem-configuration = < 0x0000000a 0xc0000079
292 nvidia,emem-configuration = < 0x00020001 0xc0000020
302 nvidia,emem-configuration = < 0x00010001 0xc0000020
312 nvidia,emem-configuration = < 0x00000001 0xc0000030
322 nvidia,emem-configuration = < 0x00000003 0xc0000025
[all …]
|
| D | tegra30-asus-tf700t.dts | 148 nvidia,emem-configuration = < 0x00020001 0xc0000020
158 nvidia,emem-configuration = < 0x00010001 0xc0000020
168 nvidia,emem-configuration = < 0x00000001 0xc0000030
178 nvidia,emem-configuration = < 0x00000003 0xc0000025
188 nvidia,emem-configuration = < 0x00000006 0xc0000048
198 nvidia,emem-configuration = < 0x0000000c 0xc0000090
213 nvidia,emem-configuration = < 0x00020001 0xc0000020
223 nvidia,emem-configuration = < 0x00010001 0xc0000020
233 nvidia,emem-configuration = < 0x00000001 0xc0000030
243 nvidia,emem-configuration = < 0x00000003 0xc0000025
[all …]
|
| /Linux-v6.1/Documentation/arm/samsung/ |
| D | gpio.rst | 30 PIN configuration
33 Pin configuration is specific to the Samsung architecture, with each SoC
34 registering the necessary information for the core gpio configuration
38 driver or machine to change gpio configuration.
|
| /Linux-v6.1/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | scfg.txt | 1 Freescale Supplement configuration unit (SCFG)
3 SCFG is the supplemental configuration unit, that provides SoC specific
4 configuration and status registers for the chip. Such as getting PEX port
|
| /Linux-v6.1/Documentation/userspace-api/media/drivers/ |
| D | omap3isp-uapi.rst | 28 (When using parallel interface one must pay account to correct configuration
52 does not fall under the standard IOCTLs --- gamma tables and configuration of
90 The update field in the structures tells whether to update the configuration
97 configuration data for the function.
132 The associated configuration pointer for the function may not be NULL when
133 enabling the function. When disabling a function the configuration pointer is
140 The statistics subdevs do offer more dynamic configuration options than the
173 module's data output depends on the requested configuration. Although the
178 module or request the necessary buffer size during the first configuration
181 The internal buffer size allocation considers the requested configuration's
[all …]
|
12345678910>>...61
