| /linux-6.3-rc2/Documentation/trace/coresight/ |
| A D | coresight-config.rst | 38 CoreSight device is registered with the configuration manager.
78 configuration may be selected.
81 to support system configuration. A configuration may select features to be
112 1) In this example, the configuration is 'autofdo', which has an
116 configuration as part of its command line::
120 which will enable the 'autofdo' configuration.
222 a hash of the configuration name.
249 In a configuration there are 'enable' and 'preset' files.
251 To enable a configuration for use with sysfs::
263 This will select preset3 for the configuration.
[all …]
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/pinctrl/ |
| A 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
22 configuration used by those states.
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
55 pin configuration nodes.
65 pinctrl-1: List of phandles, each pointing at a pin configuration
68 pinctrl-n: List of phandles, each pointing at a pin configuration
90 * For an IP block whose binding supports pin configuration,
[all …]
|
| A 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
|
| A 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:
|
| A 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).
|
| A 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:
|
| A 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:
|
| A 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:
|
| A 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.
|
| A 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.
|
| A 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:
|
| A D | nvidia,tegra-pinmux-common.yaml | 16 the phrase "pin configuration node".
18 Tegra's pin configuration nodes act as a container for an arbitrary number
19 of subnodes. Each of these subnodes represents some desired configuration
20 for a pin, a group, or a list of pins or groups. This configuration can
22 pin configuration parameters, such as pull-up, tristate, drive strength,
29 other words, a subnode that lists a mux function but no pin configuration
30 parameters implies no information about any pin configuration parameters.
121 description: Open-drain configuration for the pin.
130 description: Lock the pin configuration against further changes until
134 - description: disable pin configuration lock
[all …]
|
| A 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.
|
| A D | brcm,bcm2835-gpio.txt | 37 phrase "pin configuration node".
39 Each pin configuration node lists the pin(s) to which it applies, and one or
41 configuration. Each subnode only affects those parameters that are explicitly
43 information about any pull configuration. Similarly, a subnode that lists only
46 The BCM2835 pin configuration and multiplexing supports the generic bindings.
60 Legacy pin configuration and multiplexing binding:
61 *** (Its use is deprecated, use generic multiplexing and configuration
|
| /linux-6.3-rc2/Documentation/networking/dsa/ |
| A 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`
56 single port and gateway configuration, while there is no need to add an extra
57 VLAN configuration in the bridge showcase.
[all …]
|
| /linux-6.3-rc2/Documentation/ABI/testing/ |
| A 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
|
| /linux-6.3-rc2/Documentation/arm/samsung/ |
| A D | gpio.rst | 22 PIN configuration
25 Pin configuration is specific to the Samsung architecture, with each SoC
26 registering the necessary information for the core gpio configuration
30 driver or machine to change gpio configuration.
|
| /linux-6.3-rc2/Documentation/driver-api/tty/ |
| A D | n_gsm.rst | 48 struct termios configuration;
68 /* get n_gsm extended configuration */
72 /* set the new extended configuration */
74 /* get n_gsm configuration */
82 /* set the new configuration */
135 struct termios configuration;
148 /* get n_gsm extended configuration */
152 /* set the new extended configuration */
154 /* get n_gsm configuration */
162 /* set the new configuration */
|
| /linux-6.3-rc2/drivers/accessibility/speakup/ |
| A 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-6.3-rc2/arch/arm/boot/dts/ |
| A D | tegra30-asus-tf300t.dts | 358 nvidia,emc-configuration = < 0x00000001
394 nvidia,emc-configuration = < 0x00000002
430 nvidia,emc-configuration = < 0x00000004
466 nvidia,emc-configuration = < 0x0000000a
500 nvidia,emc-configuration = < 0x0000000f
535 nvidia,emc-configuration = < 0x0000001f
576 nvidia,emc-configuration = < 0x00000001
612 nvidia,emc-configuration = < 0x00000002
648 nvidia,emc-configuration = < 0x00000005
684 nvidia,emc-configuration = < 0x0000000a
[all …]
|
| A D | tegra30-asus-tf300tg.dts | 432 nvidia,emc-configuration = < 0x00000001
468 nvidia,emc-configuration = < 0x00000002
504 nvidia,emc-configuration = < 0x00000005
540 nvidia,emc-configuration = < 0x0000000a
574 nvidia,emc-configuration = < 0x0000000f
609 nvidia,emc-configuration = < 0x0000001f
650 nvidia,emc-configuration = < 0x00000001
686 nvidia,emc-configuration = < 0x00000002
722 nvidia,emc-configuration = < 0x00000005
758 nvidia,emc-configuration = < 0x0000000a
[all …]
|
| A D | tegra30-asus-tf700t.dts | 288 nvidia,emc-configuration = < 0x00000001
324 nvidia,emc-configuration = < 0x00000002
360 nvidia,emc-configuration = < 0x00000004
396 nvidia,emc-configuration = < 0x00000009
430 nvidia,emc-configuration = < 0x00000012
465 nvidia,emc-configuration = < 0x00000025
506 nvidia,emc-configuration = < 0x00000001
542 nvidia,emc-configuration = < 0x00000002
578 nvidia,emc-configuration = < 0x00000004
614 nvidia,emc-configuration = < 0x00000009
[all …]
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/powerpc/fsl/ |
| A 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-6.3-rc2/Documentation/devicetree/bindings/usb/ |
| A D | usb-device.yaml | 23 for devices of class 0 or 9 (hub) with a single configuration and a single
57 The configuration component is not included in the textual
58 representation of an interface-node unit address for configuration 1.
65 the product id, CN is the configuration value and IN is the interface
75 configuration value.
88 # interface 0 of configuration 1
89 # interface 0 of configuration 2
|
| /linux-6.3-rc2/Documentation/userspace-api/media/drivers/ |
| A 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
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
189 As the configuration doesn't take effect synchronously to the request, the
[all …]
|