| /linux/Documentation/trace/coresight/ |
| H A 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/Documentation/ABI/stable/ |
| H 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/ |
| H 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.
|
| H 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 …]
|
| H 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.
|
| H 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/ |
| H A D | metafmt-rkisp1.rst | 14 The configuration of the RkISP1 ISP is performed by userspace by providing
19 configuration format and the `extensible parameters` configuration
24 Fixed parameters configuration format
27 When using the fixed configuration format, parameters are passed to the
44 Extensible parameters configuration format
47 When using the extensible configuration format, parameters are passed to the
54 populate the data buffer with only the configuration data for the ISP blocks it
56 to define new block types to support new configuration parameters, and defines a
60 For these reasons, this configuration method is preferred over the `fixed
83 The 3A statistics and configuration parameters described here are usually
|
| H A D | metafmt-pisp-be.rst | 10 Raspberry Pi PiSP Back End configuration format
14 configured by userspace by providing a buffer of configuration parameters
18 The PiSP Back End processes images in tiles, and its configuration requires
24 provide detailed description of the ISP back end configuration and programming
27 Global configuration data
30 The global configuration data describe how the pixels in a particular image are
35 Global configuration data are passed to the ISP by populating the member of
|
| H A D | metafmt-pisp-fe.rst | 10 Raspberry Pi PiSP Front End configuration format
14 userspace by providing a buffer of configuration parameters to the
20 provide detailed description of the Front End configuration and programming
39 provide detailed description of the Front End configuration and programming
|
| /linux/Documentation/devicetree/bindings/pinctrl/ |
| H 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
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 …]
|
| H 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).
|
| H 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.
|
| H 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.
|
| H 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:
|
| H 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/ |
| H A 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 …]
|
| /linux/Documentation/networking/dsa/ |
| H 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
56 single port and gateway configuration, while there is no need to add an extra
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H 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/arch/arm/boot/dts/nvidia/ |
| H A 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 …]
|
| H A 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 …]
|
| H A D | tegra30-asus-tf201.dts | 119 nvidia,emem-configuration = < 0x00020001 0x80000010
129 nvidia,emem-configuration = < 0x00010001 0x80000010
139 nvidia,emem-configuration = < 0x00000001 0x80000018
149 nvidia,emem-configuration = < 0x00000003 0x80000025
159 nvidia,emem-configuration = < 0x00000006 0x80000048
174 nvidia,emem-configuration = < 0x00020001 0x80000010
184 nvidia,emem-configuration = < 0x00010001 0x80000010
194 nvidia,emem-configuration = < 0x00000001 0x80000018
204 nvidia,emem-configuration = < 0x00000003 0x80000025
214 nvidia,emem-configuration = < 0x00000007 0x8000005a
[all …]
|
| H A 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/drivers/accessibility/speakup/ |
| H 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/Documentation/arch/arm/samsung/ |
| H 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/Documentation/userspace-api/media/drivers/ |
| H 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
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 …]
|