From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Boris Brezillon <boris.brezillon@bootlin.com>
Cc: Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Richard Weinberger <richard@nod.at>,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
Mike Dunn <mikedunn@newsguy.com>,
Sergey Larin <cerg2010cerg2010@mail.ru>
Subject: Re: [PATCH v2 1/4] mtd: rawnand: Remove docg4
Date: Thu, 6 Sep 2018 22:12:15 +0200 [thread overview]
Message-ID: <20180906221215.230382cd@xps13> (raw)
In-Reply-To: <20180804205923.25298-1-boris.brezillon@bootlin.com>
Hi Boris,
Boris Brezillon <boris.brezillon@bootlin.com> wrote on Sat, 4 Aug 2018
22:59:20 +0200:
> The diskonchip G4 driver does not fit very well in the raw/parallel
> NAND framework simply because such chips have an internal controller
> translating DoC-specific commands into NAND ones.
>
> Keeping such a driver in the raw NAND framework is a real burden for
> NAND maintainers.
>
> Not to mention that some parts of this driver are a bit worrisome:
>
> - writes are done by subpages, even though we're interfacing with an MLC
> chip which are known to not support subpage writes very well (it might
> be that the FTL handles the complexity for us though)
>
> - some part of the code are simply ignoring return codes of function that
> can fail in a few occasions
>
> - there's a hack to support OOB writes when no data is provided. This
> operation is not supported by the chip and should have been rejected,
> and nandwrite and other userspace tools should have been patched to
> deal with such devices
>
> - the driver is apparently broken when ignore_badblocks module param
> is not set to 1 and nobody noticed that (don't know since when this
> is the case, but it's not a recent change)
> http://lists.infradead.org/pipermail/linux-mtd/2018-July/082472.html
>
> Add to that the fact that we already have a docg3 driver in
> drivers/mtd/devices/docg3.c and, looking at the code (and regs), it
> seems docg3 and docg4 have a lot in common (even the author of this
> driver seemed to have realized that interfacing with the raw NAND
> framework might have been a bad idea
> http://lists.infradead.org/pipermail/linux-mtd/2012-January/039517.html).
>
> For all these reasons, I'm proposing to remove this driver. If anyone
> ever wants to add support for this chip back, I'd suggest extending
> the docg3 driver instead of adding a completely new driver.
>
> Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com>
> Cc: Mike Dunn <mikedunn@newsguy.com>
> Cc: Robert Jarzmik <robert.jarzmik@free.fr>
> Cc: Sergey Larin <cerg2010cerg2010@mail.ru>
> ---
> Changes in v2:
> - none
> ---
> drivers/mtd/nand/raw/Kconfig | 20 -
> drivers/mtd/nand/raw/Makefile | 1 -
> drivers/mtd/nand/raw/docg4.c | 1442 -----------------------------------------
> 3 files changed, 1463 deletions(-)
> delete mode 100644 drivers/mtd/nand/raw/docg4.c
Series applied to nand/next.
Thanks,
Miquèl
prev parent reply other threads:[~2018-09-06 20:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 20:59 [PATCH v2 1/4] mtd: rawnand: Remove docg4 Boris Brezillon
2018-08-04 20:59 ` [PATCH v2 2/4] ARM: pxa: palmtreo: Drop docg4 specific init Boris Brezillon
2018-08-19 19:38 ` Robert Jarzmik
2018-09-04 20:57 ` Miquel Raynal
2018-09-09 19:11 ` Robert Jarzmik
[not found] ` <1c78935418904123a9cc27a65ec9d3e4@IL-EXCH02.marvell.com>
2018-08-20 7:46 ` [EXT] Re: nand speed test Miquel Raynal
2018-08-20 7:50 ` Kostya Porotchkin
2018-08-04 20:59 ` [PATCH v2 3/4] mtd: rawnand: Make maxchips an unsigned int Boris Brezillon
2018-08-04 20:59 ` [PATCH v2 4/4] mtd: rawnand: Do not treat !maxchips specially in nand_scan_with_ids() Boris Brezillon
2018-08-05 19:12 ` [PATCH v2 1/4] mtd: rawnand: Remove docg4 Robert Jarzmik
2018-08-05 19:51 ` Boris Brezillon
2018-09-06 20:12 ` Miquel Raynal [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180906221215.230382cd@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=boris.brezillon@bootlin.com \
--cc=cerg2010cerg2010@mail.ru \
--cc=computersforpeace@gmail.com \
--cc=daniel@zonque.org \
--cc=dwmw2@infradead.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=mikedunn@newsguy.com \
--cc=richard@nod.at \
--cc=robert.jarzmik@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).