adi,sdp-120
Vendor: Analog Devices, Inc.
Description
GPIO pins exposed on a Analog devices SDP interface.
120-pin SDP interface:
1 VIN NC 120
2 NC NC 119
3 GND GND 118
4 GND GND 117
5 USB_VBUS VIO 116
6 GND GND 115
7 PAR_D23 PAR_D22 114
8 PAR_D21 PAR_D20 113
9 PAR_D19 PAR_D18 112
10 PAR_D17 PAR_D16 111
11 GND PAR_D15 110
12 PAR_D14 GND 109
13 PAR_D13 PAR_D12 108
14 PAR_D11 PAR_D10 107
15 PAR_D9 PAR_D8 106
16 PAR_D7 PAR_D6 105
17 GND GND 104
18 PAR_D5 PAR_D4 103
19 PAR_D3 PAR_D2 102
20 PAR_D1 PAR_D0 101
21 PAR_RD_N PAR_WR_N 100
22 PAR_CS_N PAR_INT 99
23 GND GND 98
24 PAR_A3 PAR_A2 97
25 PAR_A1 PAR_A0 96
26 PAR_FS3 PAR_FS2 95
27 PAR_FS1 PAR_CLK 94
28 GND GND 93
29 SPORT_TDV0 SPORT_RSCLK 92
30 SPORT_TDV1 SPORT_DR0 91
31 SPORT_DR1 SPORT_RFS 90
32 SPORT_DT1 SPORT_TFS 89
33 SPI_D2 SPORT_DT0 88
34 SPI_D3 SPORT_TSCLK 87
35 SERIAL_INT GND 86
36 GND SPI_SEL_A_N 85
37 SPI_SEL_B_N SPI_MOSI 84
38 SPI_SEL_C_N SPI_MISO 83
39 SPI_SEL1/SPI_SS_N SPI_CLK 82
40 GND GND 81
41 SDA_1 SDA_0 80
42 SCL_1 SCL_0 79
43 GPIO0 GPIO1 78
44 GPIO2 GPIO3 77
45 GPIO4 GPIO5 76
46 GND GND 75
47 GPIO6 GPIO7 74
48 TMR_A TMR_B 73
49 TMR_C TMR_D 72
50 NC CLKOUT 71
51 NC NC 70
52 GND GND 69
53 NC NC 68
54 NC NC 67
55 NC NC 66
56 EEPROM_A0 WAKE_N 65
57 RESET_OUT_N SLEEP_N 64
58 GND GND 63
59 UART_RX UART_TX 62
60 RESET_IN_N BMODE1 61
Properties
Node specific properties
Properties not inherited from the base binding file.
Name |
Type |
Details |
|---|---|---|
|
|
This property is required. |
|
|
|
|
|
|
|
|
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 “adi,sdp-120” compatible.
Name |
Type |
Details |
|---|---|---|
|
|
Indicates the operational status of the hardware or other
resource that the node represents. In particular:
- "okay" means the resource is operational and, for example,
can be used by device drivers
- "disabled" means the resource is not operational and the system
should treat it as if it is not present
For details, see "2.3.4 status" in Devicetree Specification v0.4.
Legal values: See Important properties for more information. |
|
|
This property is a list of strings that essentially define what
type of hardware or other resource this devicetree node
represents. Each device driver checks for specific compatible
property values to find the devicetree nodes that represent
resources that the driver should manage.
The recommended format is "vendor,device", The "vendor" part is
an abbreviated name of the vendor. The "device" is usually from
the datasheet.
The compatible property can have multiple values, ordered from
most- to least-specific. Having additional values is useful when the
device is a specific instance of a more general family, to allow the
system to match the most specific driver available.
For details, see "2.3.1 compatible" in Devicetree Specification v0.4.
This property is required. See Important properties for more information. |
|
|
Information used to address the device. The value is specific to
the device (i.e. is different depending on the compatible
property).
The "reg" property is typically a sequence of (address, length) pairs.
Each pair is called a "register block". Values are
conventionally written in hex.
For details, see "2.3.6 reg" in Devicetree Specification v0.4.
See Important properties for more information. |
|
|
Optional names given to each register block in the "reg" property.
For example:
/ {
soc {
#address-cells = <1>;
#size-cells = <1>;
uart@1000 {
reg = <0x1000 0x2000>, <0x3000 0x4000>;
reg-names = "foo", "bar";
};
};
};
The uart@1000 node has two register blocks:
- one with base address 0x1000, size 0x2000, and name "foo"
- another with base address 0x3000, size 0x4000, and name "bar"
|
|
|
Information about interrupts generated by the device, encoded as an array
of one or more interrupt specifiers. The format of the data in this property
varies by where the device appears in the interrupt tree. Devices with the same
"interrupt-parent" will use the same format in their interrupts properties.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
See Important properties for more information. |
|
|
Extended interrupt specifier for device, used as an alternative to
the "interrupts" property.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
|
|
|
Optional names given to each interrupt generated by a device.
The interrupts themselves are defined in either "interrupts" or
"interrupts-extended" properties.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
|
|
|
If present, this refers to the node which handles interrupts generated
by this device.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
|
|
|
Human readable string describing the device. Use of this property is
deprecated except as needed on a case-by-case basis.
For details, see "4.1.2 Miscellaneous Properties" in Devicetree
Specification v0.4.
See Important properties for more information. |
|
|
Information about the device's clock providers. In general, this property
should follow conventions established in the dt-schema binding:
https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/clock/clock.yaml
|
|
|
Optional names given to each clock provider in the "clocks" property.
|
|
|
This property encodes the number of <u32> cells used by address fields
in "reg" properties in this node's children.
For details, see "2.3.5 #address-cells and #size-cells" in Devicetree
Specification v0.4.
|
|
|
This property encodes the number of <u32> cells used by size fields in
"reg" properties in this node's children.
For details, see "2.3.5 #address-cells and #size-cells" in Devicetree
Specification v0.4.
|
|
|
DMA channel specifiers relevant to the device.
|
|
|
Optional names given to the DMA channel specifiers in the "dmas" property.
|
|
|
IO channel specifiers relevant to the device.
|
|
|
Optional names given to the IO channel specifiers in the "io-channels" property.
|
|
|
Mailbox / IPM channel specifiers relevant to the device.
|
|
|
Optional names given to the mbox specifiers in the "mboxes" property.
|
|
|
Power domain specifiers relevant to the device.
|
|
|
Optional names given to the power domain specifiers in the "power-domains" property.
|
|
|
Number of cells in power-domains property
|
|
|
Do not initialize device automatically on boot. Device should be manually
initialized using device_init().
|
|
|
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.
|
|
|
Automatically configure the device for runtime power management after the
init function runs.
|
|
|
List of power states that will disable this device power.
|