[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <481e832401c148baf222639f10f494b90dcd23c9.camel@v3.sk>
Date: Mon, 26 Aug 2019 13:59:27 +0200
From: Lubomir Rintel <lkundrak@...sk>
To: Marc Zyngier <maz@...nel.org>, Olof Johansson <olof@...om.net>
Cc: Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Thomas Gleixner <tglx@...utronix.de>,
Jason Cooper <jason@...edaemon.net>,
Kishon Vijay Abraham I <kishon@...com>,
Russell King <linux@...linux.org.uk>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-clk@...r.kernel.org
Subject: Re: [PATCH v2 00/20] Initial support for Marvell MMP3 SoC
On Fri, 2019-08-23 at 10:42 +0100, Marc Zyngier wrote:
> On 23/08/2019 08:21, Lubomir Rintel wrote:
> > On Thu, 2019-08-22 at 11:31 +0100, Marc Zyngier wrote:
> > > On 22/08/2019 10:26, Lubomir Rintel wrote:
> > > > Hi,
> > > >
> > > > this is a second spin of a patch set that adds support for the Marvell
> > > > MMP3 processor. MMP3 is used in OLPC XO-4 laptops, Panasonic Toughpad
> > > > FZ-A1 tablet and Dell Wyse 3020 Tx0D thin clients.
> > > >
> > > > Compared to v1, there's a handful of fixes in response to reviews. Patch
> > > > 02/20 is new. Details in individual patches.
> > > >
> > > > Apart from the adjustments in mach-mmp/, the patch makes necessary
> > > > changes to the irqchip driver and adds an USB2 PHY driver. The latter
> > > > has a dependency on the mach-mmp/ changes, so it can't be submitted
> > > > separately.
> > > >
> > > > The patch set has been tested to work on Wyse Tx0D and not ruin MMP2
> > > > support on XO-1.75.
> > >
> > > How do you want this series to be merged? I'm happy to take the irqchip
> > > related patches as well as the corresponding DT change (once reviewed)
> > > through my tree.
> >
> > I was hoping for the Arm SoC tree, because there are some dependencies
> > (MMP3 USB PHY depends on MMP3 SoC).
> >
> > That said, the irqchip patches are rather independent and the only
> > downside of them going in via a different tree will be that the other
> > tree that will lack them won't boot on MMP3 (things will compile
> > though). I don't know if that's okay. What's typically done in cases
> > like these?
>
> I usually take the irqchip patches that can be built standalone (without
> dependency on header files, for example). If you want them to go via
> another tree, stick my
>
> Acked-by: Marc Zyngier <maz@...nel.org>
>
> on patches #6 through #9.
Actually, please go ahead and pick the irqchip patches into your tree.
The rest of the patch set may need a couple more spins, and it will be
nice if it gets shorter.
Thank you
Lubo
Powered by blists - more mailing lists