summaryrefslogtreecommitdiffstats
path: root/arch/arm/boot/dts/exynos5410.dtsi
diff options
context:
space:
mode:
authorEnric Balletbo i Serra <enric.balletbo@collabora.com>2019-06-13 18:27:45 +0200
committerHeiko Stuebner <heiko@sntech.de>2019-06-27 14:41:38 +0200
commite6d237fdc13a790c1f73b74f7a9e85529b9ed44b (patch)
tree8818a01020ca56838f96ab83a471e7ee6057294d /arch/arm/boot/dts/exynos5410.dtsi
parentarm64: dts: rockchip: enable rk3328 watchdog clock (diff)
downloadlinux-e6d237fdc13a790c1f73b74f7a9e85529b9ed44b.tar.xz
linux-e6d237fdc13a790c1f73b74f7a9e85529b9ed44b.zip
arm64: dts: rockchip: Update DWC3 modules on RK3399 SoCs
As per binding documentation [1], the DWC3 core should have the "ref", "bus_early" and "suspend" clocks. As explained in the binding, those clocks are required for new platforms but not for existing platforms before commit fe8abf332b8f ("usb: dwc3: support clocks and resets for DWC3 core"). However, as those clocks are really treated as required, this ends with having some annoying messages when the "rockchip,rk3399-dwc3" is used: [ 1.724107] dwc3 fe800000.dwc3: Failed to get clk 'ref': -2 [ 1.731893] dwc3 fe900000.dwc3: Failed to get clk 'ref': -2 [ 2.495937] dwc3 fe800000.dwc3: Failed to get clk 'ref': -2 [ 2.647239] dwc3 fe900000.dwc3: Failed to get clk 'ref': -2 In order to remove those annoying messages, update the DWC3 hardware module node and add all the required clocks. With this change, both, the glue node and the DWC3 core node, have the clocks defined, but that's not really a problem and there isn't a side effect on do this. So, we can get rid of the annoying get clk error messages. [1] Documentation/devicetree/bindings/usb/dwc3.txt Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Diffstat (limited to 'arch/arm/boot/dts/exynos5410.dtsi')
0 files changed, 0 insertions, 0 deletions