On Tue, Aug 31, 2021 at 11:19:20PM +0200, Michael Walle wrote:
> Am 2021-08-31 20:51, schrieb Vladimir Oltean:
> > On Tue, Aug 31, 2021 at 05:40:19PM +0200, Michael Walle wrote:
> > > This series sync the device tree of the LS1028A SoC with the linux
> > > one.
> > > To ease future debugging and reviewing, we first clean up the
> > > existing one,
> > > removing bogus nodes, moving all CCSR related nodes in /soc and
> > > update the
> > > drivers to accept the offical compatible strings.
> > > 
> > > This was tested on a sl28 board, but the ls1028a.dtsi sync also
> > > affects the
> > > LS1028A-RDB and -QDS. It would be nice if someone could actually
> > > test it on
> > > such a board.
> > > 
> > > I didn't sync the device trees for the NXP boards because u-boot
> > > related
> > > things aren't split into its own -u-boot.dtsi file. So I'll leave
> > > that task
> > > to NXP :)
> > > 
> > > The following patch is a prerequisite for this series:
> > > https://patchwork.ozlabs.org/project/uboot/patch/20210825210510.24766-1-trini@konsulko.com/
> > 
> > Thanks for the work, this is appreciated.

Yes, thanks for getting the ball rolling on this!

> > So this needs a v2, but in general, who do you expect to pick up your
> > patches?
> 
> Mh, I haven't found a rule how patches are picked up in u-boot but most of
> the
> time they go through the qoriq git tree. Why do you ask?

I too would expect these to come ia the qoriq tree.  We don't have the
number of custodians/maintainers Linux has, so we also don't have the
very fine grained tree merge path.  For driver changes, etc, that aren't
also touching a core subsystem, I'm fine with whichever custodian feels
most comfortable taking them and sending me a pull request.

-- 
Tom