Re: Subject: [PATCH v4 0/4] mtd: rawnand: ams-delta: Use GPIO API for data I/O
From: Tony Lindgren <tony@atomide.com>
Date: 2018-12-07 16:10:43
Also in:
linux-omap, lkml
* Miquel Raynal [off-list ref] [181207 08:04]:
Hi Tony, Tony Lindgren [off-list ref] wrote on Fri, 23 Nov 2018 09:03:33 -0800:quoted
* Boris Brezillon [off-list ref] [181121 14:56]:quoted
On Wed, 21 Nov 2018 12:08:02 +0100 Janusz Krzysztofik [off-list ref] wrote:quoted
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@atomide.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 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel