| /f-stack/freebsd/contrib/device-tree/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
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 …]
|
| H 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
|
| H 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:
|
| H 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:
|
| 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 | xlnx,zynq-pinctrl.txt | 10 phrase "pin configuration node".
12 Zynq'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 pin(s)/group(s), and various pin configuration
18 Each configuration node can consist of multiple nodes describing the pinmux and
29 Required properties for configuration nodes:
69 a pin configuration subnode:
|
| H A D | qcom,ipq4019-pinctrl.txt | 27 phrase "pin configuration node".
29 The pin configuration nodes act as a container for an abitrary 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:
|
| H A 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:
|
| H 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:
|
| 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 | renesas,pfc-pinctrl.txt | 55 The PFC node also acts as a container for pin configuration nodes. Please refer
59 Each pin configuration node represents a desired configuration for a pin, a
60 pin group, or a list of pins or pin groups. The configuration can include the
61 function to select on those pin(s) and pin configuration parameters (such as
64 Pin configuration nodes contain pin configuration properties, either directly
65 or grouped in child subnodes. Both pin muxing and configuration parameters can
66 be grouped in that way and referenced as a single pin configuration node by
69 A configuration node or subnode must reference at least one pin (through the
71 configuration parameter. When the function is present only pin groups can be
74 All pin configuration nodes and subnodes names are ignored. All of those nodes
[all …]
|
| H A 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:
|
| 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.
|
| H A 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:
|
| H 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
|
| H A D | qcom,pmic-mpp.txt | 55 phrase "pin configuration node".
57 The pin configuration nodes act as a container for an arbitrary number of
58 subnodes. Each of these subnodes represents some desired configuration for a
59 pin or a list of pins. This configuration can include the
60 mux function to select on those pin(s), and various pin configuration
69 other words, a subnode that lists a mux function but no pin configuration
70 parameters implies no information about any pin configuration parameters.
75 to specify in a pin configuration subnode:
109 outputs are enabled. The hardware ignores the configuration
|
| H A D | pinctrl-max77620.txt | 8 including the meaning of the phrase "pin configuration node".
29 <pinctrl-bindings.txt>. Absence of properties will leave the configuration
42 customised properties are required to configure FPS configuration parameters
61 the FPS configuration register for that
62 GPIO to default configuration.
86 configuration register when system
94 configuration register when system
|
| H A D | marvell,mvebu-pinctrl.txt | 9 phrase "pin configuration node".
11 A Marvell SoC pin configuration node is a node of a group of pins which can
19 Required properties for pin configuration node:
22 marvell,pins given in this pin configuration node. The function has to be
|
| /f-stack/freebsd/contrib/libsodium/ |
| H A D | appveyor.yml | 8 configuration: Debug
10 configuration: Release
12 configuration: Debug
14 configuration: Release
|
| /f-stack/freebsd/contrib/device-tree/Bindings/powerpc/fsl/ |
| H 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
|
| /f-stack/freebsd/contrib/device-tree/Bindings/fpga/ |
| H A D | xlnx,zynqmp-pcap-fpga.txt | 2 The ZynqMP SoC uses the PCAP (Processor configuration Port) to configure the
3 Programmable Logic (PL). The configuration uses the firmware interface.
8 Example for full FPGA configuration:
|
| /f-stack/freebsd/contrib/device-tree/Bindings/pci/ |
| H A D | designware-pcie.txt | 7 - reg: For designware cores version < 4.80 contains the configuration
9 the configuration and ATU address space
10 - reg-names: Must be "config" for the PCIe configuration space and "atu" for
12 (The old way of getting the configuration address space from "ranges"
38 for data corruption. CDM registers include standard PCIe configuration
51 Example configuration:
|
| /f-stack/freebsd/contrib/device-tree/Bindings/usb/ |
| H A D | usb-device.txt | 13 for devices of class 0 or 9 (hub) with a single configuration and a single
37 the product id, CN is the configuration value and IN is the interface
43 - reg: the interface number and configuration value
45 The configuration component is not included in the textual representation of
46 an interface-node unit address for configuration 1.
92 interface@0 { /* interface 0 of configuration 1 */
97 interface@0,2 { /* interface 0 of configuration 2 */
|