From: Boris Brezillon <bbrezillon@kernel.org>
To: Paul Cercueil <paul@crapouillou.net>
Cc: David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
Richard Weinberger <richard@nod.at>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Harvey Hunt <harveyhuntnexus@gmail.com>,
Mathieu Malaterre <malat@debian.org>,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/9] mtd: rawnand: jz4780: Add support for the JZ4740
Date: Sun, 3 Feb 2019 15:08:27 +0100 [thread overview]
Message-ID: <20190203150827.401ac31d@bbrezillon> (raw)
In-Reply-To: <1549202213.1950.1@crapouillou.net>
On Sun, 03 Feb 2019 10:56:53 -0300
Paul Cercueil <paul@crapouillou.net> wrote:
> Le dim. 3 févr. 2019 à 4:31, Boris Brezillon <bbrezillon@kernel.org>
> a écrit :
> > On Sat, 2 Feb 2019 20:19:21 -0300
> > Paul Cercueil <paul@crapouillou.net> wrote:
> >
> >> Add support for probing the jz4780-nand driver on the JZ4740 SoC
> >> from
> >> Ingenic.
> >>
> >> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
> >> ---
> >>
> >> Changes:
> >>
> >> v2: - Add support for the JZ4740 and not the JZ4725B: they behave
> >> the
> >> same, and JZ4740 is fully upstream while JZ4725B is not. The
> >> JZ4725B devicetree will then simply use the
> >> "ingenic,jz4740-nand"
> >> compatible string.
> >> - Fix the number of bytes for the ECC when the ECC strength is
> >> 4.
> >> This is needed for the JZ4740, which uses Reed-Solomon
> >> instead of
> >> BCH.
> >>
> >> drivers/mtd/nand/raw/ingenic/jz4780_nand.c | 48
> >> +++++++++++++++++-----
> >
> > If we're going to make the driver compatible with jz4740 and jz4725b
> > maybe we should rename the source files jz47xx_{nand,bch}.{c,h}.
>
> I don't know about that. Adding support for new hardware isn't a good
> reason to
> rename the driver, or so I've been told around here, as you then make
> it harder
> to review the git history of the driver.
You already move files to a sub-directory so that doesn't make a huge
difference, history will be hard to follow because of this move anyway.
next prev parent reply other threads:[~2019-02-03 14:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-02 23:19 [PATCH v2 0/9] Ingenic JZ4780 NAND patchset v2 Paul Cercueil
2019-02-02 23:19 ` [PATCH v2 1/9] mtd: rawnand: Move drivers for Ingenic SoCs to subfolder Paul Cercueil
2019-02-02 23:19 ` [PATCH v2 2/9] dt-bindings: mtd: ingenic: Add compatible strings for the JZ4740 Paul Cercueil
2019-02-18 19:20 ` Rob Herring
2019-02-02 23:19 ` [PATCH v2 3/9] mtd: rawnand: jz4780: Use SPDX license notifiers Paul Cercueil
2019-02-02 23:19 ` [PATCH v2 4/9] mtd: rawnand: jz4780: Add support for the JZ4740 Paul Cercueil
2019-02-03 7:31 ` Boris Brezillon
2019-02-03 13:56 ` Paul Cercueil
2019-02-03 14:08 ` Boris Brezillon [this message]
2019-02-03 14:10 ` Paul Cercueil
2019-02-03 14:24 ` Boris Brezillon
2019-02-02 23:19 ` [PATCH v2 5/9] mtd: rawnand: jz4780: Add ooblayout for the JZ4725B Paul Cercueil
2019-02-03 7:21 ` Boris Brezillon
2019-02-02 23:19 ` [PATCH v2 6/9] mtd: rawnand: jz4780: Add ooblayout for the Qi Ben Nanonote Paul Cercueil
2019-02-03 7:30 ` Boris Brezillon
2019-02-02 23:19 ` [PATCH v2 7/9] mtd: rawnand: jz4780-bch: Separate top-level and SoC specific code Paul Cercueil
2019-02-02 23:19 ` [PATCH v2 8/9] mtd: rawnand: jz4780-bch: Add support for the JZ4725B Paul Cercueil
2019-02-02 23:19 ` [PATCH v2 9/9] mtd: rawnand: jz4780-bch: Add support for the JZ4740 Paul Cercueil
2019-02-03 7:35 ` Boris Brezillon
2019-02-03 13:58 ` Paul Cercueil
2019-02-03 14:16 ` Boris Brezillon
2019-02-03 14:56 ` Paul Cercueil
2019-02-03 15:07 ` Boris Brezillon
2019-02-03 15:41 ` Paul Cercueil
2019-02-04 9:26 ` kbuild test robot
2019-02-04 10:02 ` kbuild test robot
2019-02-03 7:20 ` [PATCH v2 0/9] Ingenic JZ4780 NAND patchset v2 Boris Brezillon
2019-02-03 13:01 ` Paul Cercueil
2019-02-03 14:04 ` Boris Brezillon
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=20190203150827.401ac31d@bbrezillon \
--to=bbrezillon@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=harveyhuntnexus@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=malat@debian.org \
--cc=marek.vasut@gmail.com \
--cc=mark.rutland@arm.com \
--cc=miquel.raynal@bootlin.com \
--cc=paul@crapouillou.net \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
/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).