generic-pin-header

Description

GPIO pins exposed on an ordinary male or female pin headers.

This generic description has no reference to a concrete interface
with firmly defined and assigned signals. Rather, it serves the general
abstraction of arbitrary and freely definable male and female connectors,
which do not follow any generally valid specifications. Examples of this
are auxiliary or commissioning interfaces.

The counting manner and direction does not matter here and must be
specified by the respective system and must be adhered to for itself.
Here are a few examples from practice, as they are often encountered:

    1 --o       1 --o  o-- N        1 --o  o-- N/2+1   1 --o  o-- 2
    2 --o       2 --o  o-- N-1      2 --o  o-- …       … --o  o-- …
    … --o       … --o  o-- …        … --o  o-- …     N/2 --o  o-- N/2+1
  N-1 --o       … --o  o-- …        … --o  o-- N-1     … --o  o-- …
    N --o     N/2 --o  o-- N/2+1  N/2 --o  o-- N     N-1 --o  o-- N

Properties

Node specific properties

Properties not inherited from the base binding file.

Name	Type	Details
`gpio-map`	`compound`	This property is required.
`gpio-map-mask`	`compound`
`gpio-map-pass-thru`	`compound`
`#gpio-cells`	`int`	Number of items to expect in a GPIO specifier This property is required.

Deprecated node specific properties

Deprecated properties not inherited from the base binding file.

(None)

Base properties

Properties inherited from the base binding file, which defines common properties that may be set on many nodes. Not all of these may apply to the “generic-pin-header” compatible.

Name	Type	Details
`status`	`string`	indicates the operational status of a device Legal values: `'ok'`, `'okay'`, `'disabled'`, `'reserved'`, `'fail'`, `'fail-sss'` See Important properties for more information.
`compatible`	`string-array`	compatible strings This property is required. See Important properties for more information.
`reg`	`array`	register space See Important properties for more information.
`reg-names`	`string-array`	name of each register space
`interrupts`	`array`	interrupts for device See Important properties for more information.
`interrupts-extended`	`compound`	extended interrupt specifier for device
`interrupt-names`	`string-array`	name of each interrupt
`interrupt-parent`	`phandle`	phandle to interrupt controller node
`label`	`string`	Human readable string describing the device (used as device_get_binding() argument) See Important properties for more information. This property is deprecated.
`clocks`	`phandle-array`	Clock gate information
`clock-names`	`string-array`	name of each clock
`#address-cells`	`int`	number of address cells in reg property
`#size-cells`	`int`	number of size cells in reg property
`dmas`	`phandle-array`	DMA channels specifiers
`dma-names`	`string-array`	Provided names of DMA channel specifiers
`io-channels`	`phandle-array`	IO channels specifiers
`io-channel-names`	`string-array`	Provided names of IO channel specifiers
`mboxes`	`phandle-array`	mailbox / IPM channels specifiers
`mbox-names`	`string-array`	Provided names of mailbox / IPM channel specifiers
`power-domains`	`phandle-array`	Power domain specifiers
`power-domain-names`	`string-array`	Provided names of power domain specifiers
`#power-domain-cells`	`int`	Number of cells in power-domains property
`zephyr,deferred-init`	`boolean`	Do not initialize device automatically on boot. Device should be manually initialized using device_init().
`wakeup-source`	`boolean`	Property to identify that a device can be used as wake up source. When this property is provided a specific flag is set into the device that tells the system that the device is capable of wake up the system. Wake up capable devices are disabled (interruptions will not wake up the system) by default but they can be enabled at runtime if necessary.
`zephyr,pm-device-runtime-auto`	`boolean`	Automatically configure the device for runtime power management after the init function runs.
`zephyr,disabling-power-states`	`phandles`	List of power states that will disable this device power.