From: Brian Norris <computersforpeace@gmail.com>
To: Romain Izard <romain.izard.pro@gmail.com>
Cc: linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
Josh Wu <rainyfeeling@outlook.com>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Yang Wenyou <Wenyou.Yang@atmel.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v4 1/5] mtd: atmel_nand: Support variable RB_EDGE interrupts
Date: Fri, 12 Feb 2016 10:27:57 -0800 [thread overview]
Message-ID: <20160212182757.GO19540@google.com> (raw)
In-Reply-To: <1455098187-9442-2-git-send-email-romain.izard.pro@gmail.com>
On Wed, Feb 10, 2016 at 10:56:23AM +0100, Romain Izard wrote:
> The NFC controller used to accelerate the NAND transfers on SAMA5 chips
> can use either RB_EDGE0 or RB_EDGE3 as its ready/busy interrupt bit.
>
> Use the controller's compatible string to select the correct bit.
>
> For the binding:
> Acked-by: Rob Herring <robh@kernel.org>
>
> Reviewed-by: Wenyou Yang <Wenyou.yang@atmel.com>
> Tested-by: Wenyou Yang <wenyou.yang@atmel.com>
> Reviewed-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> Signed-off-by: Romain Izard <romain.izard.pro@gmail.com>
> ---
> v4: collect tested-by and reviewed-by tags
> v3: constify atmel_nand_nfc_caps structures
> v2: use of_device_get_match_data
> rename struct atmel_nand_nfc_priv as atmel_nand_nfc_caps
> rename member rb_edge as rb_mask
> do not create defines for unused status bits
>
> .../devicetree/bindings/mtd/atmel-nand.txt | 2 +-
> drivers/mtd/nand/atmel_nand.c | 35 +++++++++++++++++-----
> drivers/mtd/nand/atmel_nand_nfc.h | 3 +-
> 3 files changed, 30 insertions(+), 10 deletions(-)
Applied patches 1-4, with the following style diff:
diff --git a/drivers/mtd/nand/atmel_nand.c b/drivers/mtd/nand/atmel_nand.c
index aaad1b98dd0d..20cbaabb2959 100644
--- a/drivers/mtd/nand/atmel_nand.c
+++ b/drivers/mtd/nand/atmel_nand.c
@@ -2395,7 +2395,7 @@ static int atmel_nand_nfc_probe(struct platform_device *pdev)
nfc->caps = (const struct atmel_nand_nfc_caps *)
of_device_get_match_data(&pdev->dev);
- if (NULL == nfc->caps)
+ if (!nfc->caps)
return -ENODEV;
nfc_writel(nfc->hsmc_regs, IDR, 0xffffffff);
next prev parent reply other threads:[~2016-02-12 18:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 9:56 [PATCH v4 0/5] mtd: atmel_nand: Add support for NAND Flash on SAMA5D2 Romain Izard
2016-02-10 9:56 ` [PATCH v4 1/5] mtd: atmel_nand: Support variable RB_EDGE interrupts Romain Izard
2016-02-12 18:27 ` Brian Norris [this message]
2016-02-10 9:56 ` [PATCH v4 2/5] dt-bindings: atmel_nand: Reword the documentation Romain Izard
2016-02-10 9:56 ` [PATCH v4 3/5] mtd: atmel_nand: Support PMECC on SAMA5D2 Romain Izard
2016-02-10 9:56 ` [PATCH v4 4/5] mtd: atmel_nand: Support 32-bit ECC strength Romain Izard
2016-02-12 18:30 ` Brian Norris
2016-02-10 9:56 ` [PATCH v4 5/5] ARM: at91/dt: sama5d2: add nand0 and nfc0 nodes Romain Izard
2016-03-01 12:28 ` Nicolas Ferre
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=20160212182757.GO19540@google.com \
--to=computersforpeace@gmail.com \
--cc=Wenyou.Yang@atmel.com \
--cc=boris.brezillon@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nicolas.ferre@atmel.com \
--cc=rainyfeeling@outlook.com \
--cc=robh@kernel.org \
--cc=romain.izard.pro@gmail.com \
/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).