blob: d3033ea42ec1adb2328d92333d71637991d43fd2 [file] [log] [blame]
Caleb Connolly87da7802024-02-26 17:26:42 +00001// SPDX-License-Identifier: GPL-2.0+
2
3#include <dt-bindings/gpio/gpio.h>
4
5/delete-node/ &usb3_vbus_reg;
6/delete-node/ &usb_vbus_boost_pin;
7
8/ {
9 /* U-Boot uses different bindings for GPIO regulators, this
10 * one is required for USB
11 */
12 usb3_vbus_reg: usb3_vbus_reg {
13 compatible = "regulator-gpio";
14 regulator-name = "usb3_vbus_reg";
15 regulator-min-microvolt = <5000000>;
16 regulator-max-microvolt = <5000000>;
17 enable-gpios = <&pms405_gpios 3 GPIO_ACTIVE_HIGH>;
18 enable-active-high;
19 states = <0 0>, <5000000 1>;
20 };
21};
22
23&blsp1_uart2 {
24 /* This defines the bit clock divider which defines the baud rate.
25 * 0xFF is a divider of 16 for both the RX and TX lines. The QCS404
26 * clock driver in U-Boot hardcodes a 1843200Hz frequency for the
27 * UART core clock, and 1843200 / 16 = 115200.
28 */
29 bit-rate = <0xFF>;
30};
31
32&gcc {
33 /* The clock framework in U-Boot "sort of" has the idea of linking an
34 * individual clock to a device via uclass_priv. However the qcom clock
35 * driver instead associates many clocks with a single device. This is
36 * usually fine but it seems that assigned-clocks wreak havoc on this
37 * and we wind up having a reference to the XO clock which is associated
38 * with the qcom_clk device...
39 * For now we'll just remove these properties, no other board has these.
40 */
41 /delete-property/ assigned-clock-rates;
42 /delete-property/ assigned-clocks;
43};
44
45&usb3_dwc3 {
46 /* Make sure the VBUS supply is switched on */
47 vbus-supply = <&usb3_vbus_reg>;
48};