From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] mtd: nand: introduce NAND_ROW_ADDR_3 flag and improve Denali driver
Date: Fri, 22 Sep 2017 12:08:44 +0200 [thread overview]
Message-ID: <20170922120844.6cc692e6@bbrezillon> (raw)
In-Reply-To: <1505268351-31941-1-git-send-email-yamada.masahiro@socionext.com>
On Wed, 13 Sep 2017 11:05:49 +0900
Masahiro Yamada <yamada.masahiro@socionext.com> wrote:
> Currently, Denali NAND driver always expects 3 row address cycle
> devices because the driver init code hard-code the register setting.
> I will fix it in 2/2.
>
> Many drivers check chip->chipsize if the third row address cycle
> is needed or not. This is not nice because 32MB, 128MB are
> magic numbers. nand_scan_ident can decide it and provide a
> driver-friendly flag.
>
> 1/2 is touching verious drivers.
> I hope Acked-by from driver maintainers if this change looks good.
>
Applied.
Thanks,
Boris
>
> Changes in v2:
> - Fix build error
>
> Masahiro Yamada (2):
> mtd: nand: introduce NAND_ROW_ADDR_3 flag
> mtd: nand: denali: support two row address cycle devices
>
> drivers/mtd/nand/atmel/nand-controller.c | 3 +--
> drivers/mtd/nand/au1550nd.c | 3 +--
> drivers/mtd/nand/denali.c | 4 ++--
> drivers/mtd/nand/diskonchip.c | 3 +--
> drivers/mtd/nand/hisi504_nand.c | 3 +--
> drivers/mtd/nand/mxc_nand.c | 3 +--
> drivers/mtd/nand/nand_base.c | 9 +++++----
> drivers/mtd/nand/nuc900_nand.c | 2 +-
> include/linux/mtd/rawnand.h | 3 +++
> 9 files changed, 16 insertions(+), 17 deletions(-)
>
prev parent reply other threads:[~2017-09-22 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 2:05 [PATCH v2 0/2] mtd: nand: introduce NAND_ROW_ADDR_3 flag and improve Denali driver Masahiro Yamada
2017-09-13 2:05 ` [PATCH v2 1/2] mtd: nand: introduce NAND_ROW_ADDR_3 flag Masahiro Yamada
2017-09-13 2:45 ` Yang, Wenyou
2017-09-22 10:08 ` Boris Brezillon [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=20170922120844.6cc692e6@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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).