/Zephyr-latest/dts/bindings/regulator/ |
D | x-powers,axp192-regulator.yaml | 20 /* all properties for DCDC1 */ 23 /* all properties for DCDC2 */ 26 /* all properties for DCDC3 */ 29 /* all properties for LDOIO0 */ 32 /* all properties for LDO2 */ 35 /* all properties for LDO3 */ 58 properties:
|
D | nordic,npm6001-regulator.yaml | 18 /* all properties for BUCK0 */ 21 /* all properties for BUCK1 */ 24 /* all properties for BUCK2 */ 27 /* all properties for BUCK3 */ 30 /* all properties for LDO0 */ 33 /* all properties for LDO1 */
|
D | maxim,max20335-regulator.yaml | 18 /* all properties for BUCK1 */ 21 /* all properties for BUCK2 */ 24 /* all properties for LDO1 */ 27 /* all properties for LDO2 */ 30 /* all properties for LDO3 */
|
D | mps,mpm54304.yaml | 18 /* all properties for BUCK1 */ 21 /* all properties for BUCK2 */ 24 /* all properties for BUCK3 */ 27 /* all properties for BUCK4 */
|
D | nordic,npm1300-regulator.yaml | 19 /* all properties for BUCK1 */ 22 /* all properties for BUCK2 */ 25 /* all properties for LDO1 */ 28 /* all properties for LDO2 */ 37 properties: 67 properties:
|
D | nxp,pca9420.yaml | 15 /* all properties for BUCK1 */ 18 /* all properties for BUCK2 */ 21 /* all properties for LDO1 */ 24 /* all properties for LDO2 */ 33 properties: 88 properties:
|
D | nordic,npm1100.yaml | 14 /* all properties for BUCK */ 24 properties: 31 properties:
|
/Zephyr-latest/scripts/dts/python-devicetree/tests/test-bindings-include/ |
D | simple.yaml | 3 # Base properties for testing property filters up to 6 properties: 15 properties: 24 properties:
|
D | include.yaml | 5 properties: 13 properties: 20 properties:
|
/Zephyr-latest/soc/nordic/nrf54h/bicr/ |
D | bicr-schema.json | 4 "properties": { object 8 "properties": { object 32 "properties": { object 122 "properties": { object 156 "properties": { object 178 "properties": { object 185 "properties": { object 234 "properties": { object 251 "properties": { object 279 "properties": { object [all …]
|
/Zephyr-latest/doc/hardware/peripherals/ |
D | charger.rst | 17 host controller by setting the relevant properties, and can be adjusted at runtime to respond to 28 Properties subsection 34 Chargers typically support multiple properties, such as temperature readings of the battery-pack 37 Properties are fetched by the client one at a time using :c:func:`charger_get_prop`. 38 Properties are set by the client one at a time using :c:func:`charger_set_prop`.
|
/Zephyr-latest/doc/build/dts/ |
D | phandles.rst | 40 :ref:`dt-bindings-properties` in the devicetree bindings documentation. 68 These properties have type ``phandle``. 76 properties like ``pinctrl-0``, ``pinctrl-1`` etc. may contain multiple 87 These properties have type ``phandles``. 98 These properties have type ``phandle-array``. 102 phandle-array properties 105 These properties are commonly used to specify a resource that is owned by 111 Usually, properties with this type are written like ``phandle-array-prop`` in 135 document more rules about how to use phandle-array properties in practice. 140 Perhaps the most common use case for phandle-array properties is specifying one argument [all …]
|
D | api-usage.rst | 63 properties. 128 - :ref:`simple-properties` 129 - :ref:`reg-properties` 130 - :ref:`interrupts-properties` 131 - :ref:`phandle-properties` 135 Checking properties and values 146 .. _simple-properties: 148 Simple properties 152 numeric array, and string array properties. 166 That is, properties also need special characters converted to underscores. [all …]
|
D | bindings-syntax.rst | 37 properties: 38 # Requirements for and descriptions of the properties that this 67 datasheets or example nodes or properties as well. 114 .. _dt-bindings-properties: 116 Properties section in Devicetree bindings syntax 119 The ``properties:`` key describes properties that nodes which match the binding 127 properties: 141 The build system uses bindings to generate C macros for devicetree properties 144 build system only generates macros for properties listed in the ``properties:`` 145 key for the matching binding. Properties not mentioned in the binding are [all …]
|
/Zephyr-latest/dts/bindings/pinctrl/ |
D | microchip,mec5-pinctrl.yaml | 8 pin function selection and pin properties. For example, you can use this 21 A group can also specify shared pin properties common to all the specified 23 supported standard pin properties: 33 Custom pin properties for drive strength and slew rate are available: 47 To change a pin's pinctrl default properties add a reference to the 48 pin in the board's DTS file and set the properties. 67 properties: 90 properties:
|
D | microchip,xec-pinctrl.yaml | 9 pin function selection and pin properties. For example, you can use this 22 A group can also specify shared pin properties common to all the specified 24 supported standard pin properties: 34 Custom pin properties for drive strength and slew rate are available: 48 To change a pin's pinctrl default properties add a reference to the 49 pin in the board's DTS file and set the properties. 68 properties: 91 properties:
|
D | silabs,dbus-pinctrl.yaml | 6 pin function selection and pin properties. For example, you can use this 28 /* Group of output pins with shared properties (name is arbitrary) */ 37 /* Group of input pins with shared properties (name is arbitrary) */ 55 of the properties on the group. 57 The possible pin properties are as follows: 68 Only one of the above properties must be set at a time, as they are mutually 69 exclusive. Additional properties may be combined with the above ones: 108 properties: 113 An array of pins sharing the same group properties. The pins should be
|
D | nxp,s32k3-pinctrl.yaml | 8 the pin function selection and pin properties. This node, labeled 'pinctrl' in 12 peripheral with the same configuration properties. The 'pinmux' property in 13 a group selects the pins to be configured, and the remaining properties set 39 In addition to 'pinmux' property, each group can contain other properties such as 54 If only the required properties are supplied, the pin configuration register 86 properties: 91 An array of pins sharing the same group properties. The pins must be
|
D | ene,kb1200-pinctrl.yaml | 5 pin function selection and pin properties. For example, you can use these 8 Here is a list of supported standard pin properties: 38 To change a pin's pinctrl default properties, add a reference to the 39 pin in the board's DTS file and set the properties as below: 59 properties: 82 properties:
|
D | espressif,esp32-pinctrl.yaml | 6 functionalities and pin properties as defined by pin states. In its turn, pin 8 provided pin properties. 12 could change a node's pin state properties. Though based on a particular board, 48 Only the 'pinmux' property above is actually required, other properties can 100 pin supports a set of properties required by the target peripheral. 103 the definitions at 'hal_espressif', however, pin properties (like 108 Another thing worth noting is that all pin properties should be grouped. 109 All pins sharing common properties go under a common group (in the above 137 properties:
|
/Zephyr-latest/dts/bindings/watchdog/ |
D | snps,designware-watchdog.yaml | 7 properties: 8 # This properties is also supported: 19 using the clocks properties.
|
/Zephyr-latest/dts/bindings/test/ |
D | vnd,great-grandchild-bindings.yaml | 16 description: child node, no properties 19 description: grandchild node, no properties 24 properties:
|
/Zephyr-latest/dts/bindings/dsa/ |
D | microchip_dsa.yaml | 8 properties: 21 description: Properties of slave port 22 properties:
|
/Zephyr-latest/dts/bindings/gpio/ |
D | intel,gpio.yaml | 10 properties: 12 description: reg properties not required if acpi enumerated 19 description: interrupts properties not required if acpi enumerated
|
/Zephyr-latest/cmake/linker/ |
D | linker_flags_template.cmake | 5 # Base properties. 6 # Basic linker properties which should always be applied for a Zephyr build. 9 # Base properties when C++ support is enabled. 10 # Basic linker properties which should always be applied for a Zephyr build 14 # Base properties when building Zephyr for an embedded target (baremetal).
|