Commit 75843b63 authored by Matt Ranostay's avatar Matt Ranostay Committed by Vignesh Raghavendra

arm64: dts: ti: k3-j784s4-main: Add support for USB

Add support for the USB 3.0 controller
Signed-off-by: default avatarMatt Ranostay <mranostay@ti.com>
Signed-off-by: default avatarRavi Gunasekaran <r-gunasekaran@ti.com>
Tested-by: Andrew Halaney <ahalaney@redhat.com> # k3-j784s4-evm
Reviewed-by: default avatarRoger Quadros <rogerq@kernel.org>
Link: https://lore.kernel.org/r/20240507095545.8210-2-r-gunasekaran@ti.comSigned-off-by: default avatarVignesh Raghavendra <vigneshr@ti.com>
parent 4b5156e1
......@@ -88,6 +88,13 @@ serdes_ln_ctrl: mux-controller@4080 {
<J784S4_SERDES4_LANE2_EDP_LANE2>,
<J784S4_SERDES4_LANE3_EDP_LANE3>;
};
usb_serdes_mux: mux-controller@4000 {
compatible = "reg-mux";
reg = <0x4000 0x4>;
#mux-control-cells = <1>;
mux-reg-masks = <0x0 0x8000000>; /* USB0 to SERDES0 lane 3 mux */
};
};
gic500: interrupt-controller@1800000 {
......@@ -581,6 +588,38 @@ main_gpio6: gpio@630000 {
status = "disabled";
};
usbss0: usb@4104000 {
bootph-all;
compatible = "ti,j721e-usb";
reg = <0x00 0x4104000 0x00 0x100>;
dma-coherent;
power-domains = <&k3_pds 398 TI_SCI_PD_EXCLUSIVE>;
clocks = <&k3_clks 398 21>, <&k3_clks 398 2>;
clock-names = "ref", "lpm";
assigned-clocks = <&k3_clks 398 21>; /* USB2_REFCLK */
assigned-clock-parents = <&k3_clks 398 22>; /* HFOSC0 */
#address-cells = <2>;
#size-cells = <2>;
ranges;
status = "disabled"; /* Needs lane config */
usb0: usb@6000000 {
bootph-all;
compatible = "cdns,usb3";
reg = <0x00 0x6000000 0x00 0x10000>,
<0x00 0x6010000 0x00 0x10000>,
<0x00 0x6020000 0x00 0x10000>;
reg-names = "otg", "xhci", "dev";
interrupts = <GIC_SPI 96 IRQ_TYPE_LEVEL_HIGH>, /* irq.0 */
<GIC_SPI 102 IRQ_TYPE_LEVEL_HIGH>, /* irq.6 */
<GIC_SPI 120 IRQ_TYPE_LEVEL_HIGH>; /* otgirq.0 */
interrupt-names = "host",
"peripheral",
"otg";
};
};
main_i2c0: i2c@2000000 {
compatible = "ti,j721e-i2c", "ti,omap4-i2c";
reg = <0x00 0x02000000 0x00 0x100>;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment