[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20181207161036.GN6707@atomide.com>
Date: Fri, 7 Dec 2018 08:10:36 -0800
From: Tony Lindgren <tony@...mide.com>
To: Miquel Raynal <miquel.raynal@...tlin.com>
Cc: Boris Brezillon <boris.brezillon@...tlin.com>,
Janusz Krzysztofik <jmkrzyszt@...il.com>,
Aaro Koskinen <aaro.koskinen@....fi>,
Richard Weinberger <richard@....at>,
David Woodhouse <dwmw2@...radead.org>,
Brian Norris <computersforpeace@...il.com>,
Marek Vasut <marek.vasut@...il.com>,
Linus Walleij <linus.walleij@...aro.org>,
linux-mtd@...ts.infradead.org, linux-omap@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: Subject: [PATCH v4 0/4] mtd: rawnand: ams-delta: Use GPIO API
for data I/O
* Miquel Raynal <miquel.raynal@...tlin.com> [181207 08:04]:
> Hi Tony,
>
> Tony Lindgren <tony@...mide.com> wrote on Fri, 23 Nov 2018 09:03:33
> -0800:
>
> > * Boris Brezillon <boris.brezillon@...tlin.com> [181121 14:56]:
> > > On Wed, 21 Nov 2018 12:08:02 +0100
> > > Janusz Krzysztofik <jmkrzyszt@...il.com> wrote:
> > >
> > > > Finalize implementation of the idea suggested by Artem Bityutskiy and
> > > > Tony Lindgren, described in commit b027274d2e3a ("mtd: ams-delta: fix
> > > > request_mem_region() failure"). Use pure GPIO consumer API, as reqested
> > > > by Boris Brezillon.
> > > >
> > > > Janusz Krzysztofik (4):
> > > > ARM: OMAP1: ams-delta: Provide GPIO lookup table for NAND data port
> > > > mtd: rawnand: ams-delta: Request data port GPIO resource
> > > > mtd: rawnand: ams-delta: Use GPIO API for data I/O
> > > > ARM: OMAP1: ams-delta: Drop obsolete NAND resources
> > > >
> > > > arch/arm/mach-omap1/board-ams-delta.c | 22 ++----
> > > > drivers/mtd/nand/raw/ams-delta.c | 120 +++++++++++++++++++---------------
> > > > 2 files changed, 80 insertions(+), 62 deletions(-)
> > > >
> > > > Performance on Amstrad Delta is now acceptable after recent extensions
> > > > to GPIO API and rawnanad enhancements.
> > > >
> > > > Series intented to be merged via mtd tree, should not conflict with
> > > > other OMAP1 patches submitted for 4.21.
> > >
> > > We'll prepare an immutable tag, just in case.
> >
> > Sounds good to me thanks:
> >
> > Acked-by: Tony Lindgren <tony@...mide.com>
>
> Actually, I can't setup a topic branch with this series because it
> depends on other changes in nand/next. If a conflict happens in -next,
> I suppose we will have to send you a PR.
Hmm OK I have pretty much all the stuff applied and in next
already so if it's not conflicting now it should not conflict.
Regards,
Tony
Powered by blists - more mailing lists