[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f46b234e0aaf4356804d5e1446910bbedcbddb51.camel@redhat.com>
Date: Thu, 01 Jul 2021 07:59:42 -0500
From: Dennis Gilmore <dgilmore@...hat.com>
To: Uwe Kleine-König <uwe@...ine-koenig.org>,
linux-rockchip@...ts.infradead.org
Cc: Rob Herring <robh+dt@...nel.org>, Heiko Stuebner <heiko@...ech.de>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
"moderated list:ARM/Rockchip SoC support"
<linux-arm-kernel@...ts.infradead.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/4] arm64: dts: rockchip: helios64: fixup USB setup
On Thu, 2021-07-01 at 11:31 +0200, Uwe Kleine-König wrote:
> Hello,
>
> On 7/1/21 2:40 AM, Dennis Gilmore wrote:
> > Without the usbdrd_dwc3_1 node defined u-boot will throw an error
> > and
> > reset the system.
>
> I wonder if this should better be fixed in u-boot then?!
>
> > All other rk3399 systems use this format
>
> This is true for the dwc nodes, however for the usb2 nodes there are
> several that use this idiom (and even repeat the label name), see for
> example the &u2phy0 node in
> arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi .
>
looking at that file is where I got the idea to set it up as I have
proposed, it follows the format I have submitted
Dennis
> In my eyes it's a bit ugly to have the two nodes as separate entities
> and on the same indentation level in the machine dts given that one
> is
> the parent of the other and enabling USB needs both status settings.
>
> Best regards
> Uwe
>
Powered by blists - more mailing lists