raspberrypi,pico-header

Description

GPIO pins exposed on Raspberry Pi Pico headers.

The Raspberry Pi Pico layout provides 2 columns of 20 pins headers

This binding provides a nexus mapping for the default 26 pins as depicted below:

    0  GPIO0/UART0_TX      VBUS            -
    1  GPIO1/UART0_RX      VSYS            -
    -  GND                 GND             -
    2  GPIO2               3V3_EN          -
    3  GPIO3               3V3_OUT         -
    4  GPIO4/I2C0_SDA      ADC_VREF        -
    5  GPIO5/I2C0_SCL      GPIO28/ADC2     28
    -  GND                 GND             -
    6  GPIO6               GPIO27/ADC1     27
    7  GPIO7               GPIO26/ADC0     26
    8  GPIO8               RUN             -
    9  GPIO9               GPIO22          22
    -  GND                 GND             -
    10 GPIO10              GPIO21          21
    11 GPIO11              GPIO20          20
    12 GPIO12              GPIO19/SPI0_TX  19
    13 GPIO13              GPIO18/SPI0_SCK 18
    -  GND                 GND             -
    14 GPIO14              GPIO17/SPI0_CSn 17
    15 GPIO15              GPIO16/SPI0_RX  16

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 “raspberrypi,pico-header” compatible.

Name	Type	Details
`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.
`power-domain`	`phandle`	Power domain the device belongs to. The device will be notified when the power domain it belongs to is either suspended or resumed.
`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.
`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
`zephyr,deferred-init`	`boolean`	Do not initialize device automatically on boot. Device should be manually initialized using device_init().