| /linux/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/Documentation/ABI/stable/ |
| A D | sysfs-driver-misc-cp500 | 5 Description: Version of the FPGA configuration bitstream as printable string.
13 Description: Flag which signals if FPGA shall keep or reload configuration
15 configuration bitstream and to only reset the configured logic.
17 Reloading configuration on reset enables an update of the
18 configuration bitstream with a simple reboot. Otherwise it is
20 configuration bitstream.
23 1 = keep configuration bitstream on reset, default
24 0 = reload configuration bitstream on reset
|
| /linux/Documentation/userspace-api/gpio/ |
| A D | gpio-v2-line-set-config-ioctl.rst | 12 GPIO_V2_LINE_SET_CONFIG_IOCTL - Update the configuration of previously requested lines.
29 The new :c:type:`configuration<gpio_v2_line_config>` to apply to the
35 Update the configuration of previously requested lines, without releasing the
38 The new configuration must specify a configuration for all requested lines.
42 also apply when updating the line configuration, with the additional
44 If no direction flag is set in the configuration for a given line then the
45 configuration for that line is left unchanged.
50 from one configuration state to another.
|
| A D | gpio-get-linehandle-ioctl.rst | 33 request and their configuration.
40 While multiple lines may be requested, the same configuration applies to all
44 value and write access to the line configuration.
60 The following configuration rules apply:
66 the electrical configuration.
75 If no bias flags are set then the bias configuration is not changed.
77 Requesting an invalid configuration is an error (**EINVAL**).
85 Where the requested configuration is not directly supported by the underlying
106 configuration for platforms that support internal bias as those that require
113 In all cases, the configuration reported by gpio-get-lineinfo-ioctl.rst
[all …]
|
| A D | gpio-handle-set-config-ioctl.rst | 16 GPIOHANDLE_SET_CONFIG_IOCTL - Update the configuration of previously requested lines.
33 The new :c:type:`configuration<gpiohandle_config>` to apply to the
39 Update the configuration of previously requested lines, without releasing the
42 The configuration applies to all requested lines.
46 lines also apply when updating the line configuration, with the additional
48 configuration, including without a direction flag set, is an error
53 generally to move lines seamlessly from one configuration state to another.
|
| A D | gpio-v2-get-line-ioctl.rst | 29 to request and their configuration.
35 value, write access to the line configuration, and may receive events when
58 For any given requested line, the following configuration rules apply:
64 without altering the electrical configuration.
73 If no bias flags are set then the bias configuration is not changed.
95 Requesting an invalid configuration is an error (**EINVAL**).
102 Where the requested configuration is not directly supported by the underlying
125 configuration for platforms that support internal bias as those that require
140 In all cases, the configuration reported by gpio-v2-get-lineinfo-ioctl.rst
141 is the requested configuration, not the resulting hardware configuration.
|
| /linux/Documentation/userspace-api/media/v4l/ |
| A D | metafmt-rkisp1.rst | 13 The configuration of the RkISP1 ISP is performed by userspace by providing
18 configuration format and the `extensible parameters` configuration
23 Fixed parameters configuration format
26 When using the fixed configuration format, parameters are passed to the
43 Extensible parameters configuration format
46 When using the extensible configuration format, parameters are passed to the
53 populate the data buffer with only the configuration data for the ISP blocks it
55 to define new block types to support new configuration parameters, and defines a
59 For these reasons, this configuration method is preferred over the `fixed
82 The 3A statistics and configuration parameters described here are usually
|
| A D | metafmt-pisp-be.rst | 9 Raspberry Pi PiSP Back End configuration format
13 configured by userspace by providing a buffer of configuration parameters
17 The PiSP Back End processes images in tiles, and its configuration requires
23 provide detailed description of the ISP back end configuration and programming
26 Global configuration data
29 The global configuration data describe how the pixels in a particular image are
34 Global configuration data are passed to the ISP by populating the member of
|
| /linux/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 | 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 | 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.
|
| /linux/Documentation/driver-api/tty/ |
| A D | n_gsm.rst | 51 struct termios configuration;
71 /* get n_gsm extended configuration */
77 /* get n_gsm configuration */
85 /* set the new configuration */
87 /* get DLC 1 configuration */
148 struct termios configuration;
161 /* get n_gsm extended configuration */
165 /* set the new extended configuration */
167 /* get n_gsm configuration */
175 /* set the new configuration */
[all …]
|
| /linux/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`
55 the default VLAN 1 has to be removed from the user interface configuration in
57 VLAN configuration in the bridge showcase.
[all …]
|
| /linux/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/Documentation/arch/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/drivers/accessibility/speakup/ |
| A D | Kconfig | 56 or m to build it as a module. See the configuration
65 or m to build it as a module. See the configuration
73 or m to build it as a module. See the configuration
81 build it as a module. See the configuration help on the
89 or m to build it as a module. See the configuration
98 or m to build it as a module. See the configuration
108 configuration help on the Speakup choice above for more
119 a module. See the configuration help on the Speakup
142 configuration help on the Speakup choice above for more
153 configuration help on the Speakup choice above for more
[all …]
|
| /linux/arch/arm/boot/dts/nvidia/ |
| 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-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 …]
|
| /linux/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.
87 # interface 0 of configuration 1
88 # interface 0 of configuration 2
|
| /linux/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
|