blob: 5a237a3b7bf83be1a9c81a34e6dd9e5a8ae458fa [file] [log] [blame]
Marek Vasutb68e5d92020-07-25 16:50:56 +02001// SPDX-License-Identifier: GPL-2.0+ OR BSD-3-Clause
2/*
3 * Copyright (C) 2020 Marek Vasut <marex@denx.de>
4 */
5
6#include "stm32mp15xx-dhcom.dtsi"
7
8/ {
9 model = "DH Electronics STM32MP15xx DHCOM DRC02";
10 compatible = "dh,stm32mp15xx-dhcom-drc02", "st,stm32mp1xx";
11
12 aliases {
13 serial0 = &uart4;
14 serial1 = &usart3;
15 serial2 = &uart8;
16 };
17
18 chosen {
19 stdout-path = "serial0:115200n8";
20 };
21};
22
23&adc {
24 status = "disabled";
25};
26
27&dac {
28 status = "disabled";
29};
30
31&gpiob {
32 /*
33 * NOTE: On DRC02, the RS485_RX_En is controlled by a separate
34 * GPIO line, however the STM32 UART driver assumes RX happens
35 * during TX anyway and that it only controls drive enable DE
36 * line. Hence, the RX is always enabled here.
37 */
38 usb-hub {
39 gpio-hog;
40 gpios = <8 GPIO_ACTIVE_HIGH>;
41 output-high;
42 line-name = "rs485-rx-en";
43 };
44};
45
46&gpiod {
47 gpio-line-names = "", "", "", "",
48 "", "", "", "",
49 "", "", "", "Out1",
50 "Out2", "", "", "";
51};
52
53&gpioi {
54 gpio-line-names = "In1", "", "", "",
55 "", "", "", "",
56 "In2", "", "", "",
57 "", "", "", "";
58
59 /*
60 * NOTE: The USB Hub on the DRC02 needs a reset signal to be
61 * pulled high in order to be detected by the USB Controller.
62 * This signal should be handled by USB power sequencing in
63 * order to reset the Hub when USB bus is powered down, but
64 * so far there is no such functionality.
65 */
66 usb-hub {
67 gpio-hog;
68 gpios = <2 GPIO_ACTIVE_HIGH>;
69 output-high;
70 line-name = "usb-hub-reset";
71 };
72};
73
74&i2c2 {
75 pinctrl-names = "default";
76 pinctrl-0 = <&i2c2_pins_a>;
77 i2c-scl-rising-time-ns = <185>;
78 i2c-scl-falling-time-ns = <20>;
79 status = "okay";
80 /* spare dmas for other usage */
81 /delete-property/dmas;
82 /delete-property/dma-names;
83 status = "okay";
84
85 eeprom@50 {
86 compatible = "atmel,24c04";
87 reg = <0x50>;
88 pagesize = <16>;
89 };
90};
91
92&i2c5 { /* TP7/TP8 */
93 pinctrl-names = "default";
94 pinctrl-0 = <&i2c5_pins_a>;
95 i2c-scl-rising-time-ns = <185>;
96 i2c-scl-falling-time-ns = <20>;
97 status = "okay";
98 /* spare dmas for other usage */
99 /delete-property/dmas;
100 /delete-property/dma-names;
101};
102
103&sdmmc3 {
104 /*
105 * On DRC02, the SoM does not have SDIO WiFi. The pins
106 * are used for on-board microSD slot instead.
107 */
108 /delete-property/broken-cd;
109 cd-gpios = <&gpioi 10 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>;
110 disable-wp;
111};
112
113&spi1 {
114 pinctrl-names = "default";
115 pinctrl-0 = <&spi1_pins_a>;
116 cs-gpios = <&gpioz 3 0>;
117 /* Use PIO for the display */
118 /delete-property/dmas;
119 /delete-property/dma-names;
120 status = "disabled"; /* Enable once there is display driver */
121 /*
122 * Note: PF3/GPIO_A , PD6/GPIO_B , PG0/GPIO_C , PC6/GPIO_E are
123 * also connected to the display board connector.
124 */
125};
126
127&usart3 {
128 pinctrl-names = "default";
129 pinctrl-0 = <&usart3_pins_a>;
130 status = "okay";
131};
132
133/*
134 * Note: PI3 is UART1_RTS and PI5 is UART1_CTS on DRC02 (uart4 of STM32MP1),
135 * however the STM32MP1 pinmux cannot map them to UART4 .
136 */
137
138&uart8 { /* RS485 */
139 pinctrl-names = "default";
140 pinctrl-0 = <&uart8_pins_a>;
141 rts-gpios = <&gpioe 6 GPIO_ACTIVE_HIGH>;
142 status = "okay";
143};
144
145&usbh_ehci {
146 phys = <&usbphyc_port0>;
147 status = "okay";
148};
149
150&usbphyc {
151 status = "okay";
152};
153
154&usbphyc_port0 {
155 phy-supply = <&vdd_usb>;
156 vdda1v1-supply = <&reg11>;
157 vdda1v8-supply = <&reg18>;
158};