On Mon, May 08, 2017 at 05:24:52PM +0200, Jorge Ramirez wrote: > On 05/08/2017 05:20 PM, Tom Rini wrote: > >On Mon, May 08, 2017 at 05:15:56PM +0200, Jorge Ramirez-Ortiz wrote: > > > >>[PATCHv3 1/5] ARM64: dts: hi3798cv200-poplar: add device tree bindings > >>[PATCHv3 2/5] ARM64: dts: poplar: add usb-ehci node > >>[PATCHv3 3/5] ARM64: dts: poplar: add clock frequency to the console > >So, let me try differently. When is the board DT going into Linux > >directly (well, likely anyhow). v4.12? Or later? Also, are you adding > >U-Boot specific nodes/etc to the DT? If so, those go into a > >-u-boot.dtsi (git grep around for details) not the main one. And we > >need to explain really why they're u-boot specific. Thanks! > > sorry Tom I am not trying to duck the question, I just dont know the > answer yet :) > I'll let Alex Elder (el...@linaro.org) explain since he has been > leading the kernel upstreaming process. > > Yes the USB host is still under development in the kernel so there > is no support for it yet. > Since Marek adviced to use the ehci-generic DM driver - which I > agree is a better option- I had to add a the node for it. > > If you think that is an issue I can remove ehci-generic but I'd > rather keep it (it wont be hard to keep the device tree in sync)
Well, lets let Alex answer how things are going wrt upstreaming the kernel. We ought not need a special node for U-Boot here :) -- Tom
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
