This is the documentation for the latest (main) development branch of Zephyr. If you are looking for the documentation of previous releases, use the drop-down menu on the left and select the desired version.

zephyr,gpio-emul¶

Vendor: Zephyr-specific binding

Description¶

GPIO Emulator

Properties¶

Properties not inherited from the base binding file.

Name	Type	Details
`rising-edge`	`boolean`	Enables support for rising edge interrupt detection
`falling-edge`	`boolean`	Enables support for falling edge interrupt detection
`high-level`	`boolean`	Enables support for high level interrupt detection
`low-level`	`boolean`	Enables support for low level interrupt detection
`#gpio-cells`	`int`	Number of items to expect in a GPIO specifier This property is required. Constant value: `2`
`gpio-controller`	`boolean`	Convey's this node is a GPIO controller This property is required.
`ngpios`	`int`	This property indicates the number of in-use slots of available slots for GPIOs. The typical example is something like this: the hardware register is 32 bits wide, but only 18 of the bits have a physical counterpart. The driver is generally written so that all 32 bits can be used, but the IP block is reused in a lot of designs, some using all 32 bits, some using 18 and some using 12. In this case, setting "ngpios = <18>;" informs the driver that only the first 18 GPIOs, at local offset 0 .. 17, are in use. For cases in which there might be holes in the slot range, this value should be the max slot number-1. Default value: `32`
`gpio-reserved-ranges`	`array`	If not all the GPIOs at offsets 0...N-1 are usable for ngpios = <N>, then this property contains an additional set of tuples which specify which GPIOs are unusable. This property indicates the start and size of the GPIOs that can't be used. For example, setting "gpio-reserved-ranges = <3 2>, <10 1>;" means that GPIO offsets 3, 4, and 10 are not usable, even if ngpios = <18>.
`gpio-line-names`	`string-array`	This is an array of strings defining the names of the GPIO lines going out of the GPIO controller

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 “zephyr,gpio-emul” compatible.

Name	Type	Details
`reg`	`array`	register space This property is required. See Important properties for more information.
`label`	`string`	Human readable string describing the device (used as device_get_binding() argument) This property is required. See Important properties for more information.
`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-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
`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
`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.

Specifier cell names¶

gpio cells: pin, flags