Searched full:configuration (Results 1 – 25 of 1425) sorted by relevance
12345678910>>...57
| /Documentation/trace/coresight/ |
| D | coresight-config.rst | 4 CoreSight System Configuration Manager
13 The CoreSight System Configuration manager is an API that allows the
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.
[all …]
|
| /Documentation/ABI/stable/ |
| 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
|
| /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 | 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 | 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 | 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 | 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 …]
|
| /Documentation/userspace-api/gpio/ |
| 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.
|
| 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.
57 Configuration Rules
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**).
82 Configuration Support
85 Where the requested configuration is not directly supported by the underlying
[all …]
|
| 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.
|
| 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
55 Configuration Rules
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**).
99 Configuration Support
102 Where the requested configuration is not directly supported by the underlying
125 configuration for platforms that support internal bias as those that require
[all …]
|
| D | gpio-get-lineevent-ioctl.rst | 33 to request and its configuration.
55 bias configuration is best effort.
59 Configuration Rules
62 The following configuration rules apply:
69 If no bias flags are set then the bias configuration is not changed.
75 Requesting an invalid configuration is an error (**EINVAL**).
|
| /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`.
32 Configuration with tagging support
35 The tagging based configuration is desired. It is not specific to the b53
38 See :ref:`dsa-tagged-configuration`.
40 Configuration without tagging support
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`
[all …]
|
| /Documentation/hwmon/ |
| D | smsc47b397.rst | 104 Configuration Sequence
107 To program the configuration registers, the following sequence must be followed:
108 1. Enter Configuration Mode
109 2. Configure the Configuration Registers
110 3. Exit Configuration Mode.
112 Enter Configuration Mode
115 To place the chip into the Configuration State The config key (0x55) is written
118 Configuration Mode
121 In configuration mode, the INDEX PORT is located at the CONFIG PORT address and
124 The desired configuration registers are accessed in two steps:
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | metafmt-rkisp1.rst | 10 Configuration parameters
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
[all …]
|
| 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
|
| /Documentation/driver-api/tty/ |
| D | n_gsm.rst | 51 struct termios configuration;
71 /* get n_gsm extended configuration */
75 /* set the new extended configuration */
77 /* get n_gsm configuration */
85 /* set the new configuration */
87 /* get DLC 1 configuration */
92 /* set the new DLC 1 specific configuration */
148 struct termios configuration;
161 /* get n_gsm extended configuration */
165 /* set the new extended configuration */
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-net-grcan | 7 Hardware configuration of physical interface 0. This file reads
8 and writes the "Enable 0" bit of the configuration register.
19 Hardware configuration of physical interface 1. This file reads
20 and writes the "Enable 1" bit of the configuration register.
31 Configuration of which physical interface to be used. Possible
|
| 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
|
| /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 …]
|
| /Documentation/arch/arm/samsung/ |
| 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.
|
| /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
|
12345678910>>...57