From: "Yang, Wenyou" <wenyou.yang@atmel.com>
To: Romain Izard <romain.izard.pro@gmail.com>,
<linux-mtd@lists.infradead.org>, <devicetree@vger.kernel.org>
Cc: Josh Wu <rainyfeeling@outlook.com>,
Nicolas Ferre <nicolas.ferre@atmel.com>
Subject: Re: [PATCH v3 0/5] mtd: atmel_nand: Add support for NAND Flash on SAMA5D2
Date: Wed, 3 Feb 2016 14:54:32 +0800 [thread overview]
Message-ID: <56B1A428.2060500@atmel.com> (raw)
In-Reply-To: <1454322360-8666-1-git-send-email-romain.izard.pro@gmail.com>
Hi Romain,
On 2016/2/1 18:25, Romain Izard wrote:
> The NAND Flash controller for SAMA5D2 has small differences that make it
> impossible to use the existing driver for SAMA5D3. This patchset uses the
> device tree's compatible string to get those differences, and the code is
> slightly modified to handle them.
>
> Base on linux-mtd-next, commit 15c0be7bec002f9a529dd0966d0db96dde176fd0
>
> See previous revisions to apply on the Atmel Linux 4.1 branch.
>
> Compile tested for sama5_defconfig, and tested on SAMA5D3xek as there is no
> existing SAMA5D2 board with NAND Flash memory (yet).
Tested it on the SAMA5D2 board, with device: 8-bit ECC
(MT29F4G08ABAEAWP-IT:E) and 24-bit ECC (MT29F64G08CBAAAWP-Z:A).
For all series, you can add,
Tested-by: Wenyou Yang <wenyou.yang@atmel.com>
>
> V3 -> V2:
> - Rebase on linux-mtd-next
> - Skip patches already in the tree
>
> V2 -> V1:
> - Rebase on v4.4
> - Use of_device_get_match_data
> - Split message cleanup
> - Reword a small part of the atmel_nand device tree binding
> - Use 'caps' for all private data structures
>
> RFC -> V1:
> - Split the support of 32-bit ECC on SAMA5D2 in two commits
> - Fix the missing ECC strength configuration code
>
> Romain Izard (5):
> mtd: atmel_nand: Support variable RB_EDGE interrupts
> dt-bindings: atmel_nand: Reword the documenation
> mtd: atmel_nand: Support PMECC on SAMA5D2
> mtd: atmel_nand: Support 32-bit ECC strength
> ARM: at91/dt: sama5d2: add nand0 and nfc0 nodes
>
> .../devicetree/bindings/mtd/atmel-nand.txt | 31 +++++----
> arch/arm/boot/dts/sama5d2.dtsi | 38 +++++++++++
> drivers/mtd/nand/atmel_nand.c | 77 ++++++++++++++++++----
> drivers/mtd/nand/atmel_nand_ecc.h | 9 ++-
> drivers/mtd/nand/atmel_nand_nfc.h | 3 +-
> 5 files changed, 131 insertions(+), 27 deletions(-)
>
Best Regards,
Wenyou Yang
next prev parent reply other threads:[~2016-02-03 6:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 10:25 [PATCH v3 0/5] mtd: atmel_nand: Add support for NAND Flash on SAMA5D2 Romain Izard
2016-02-01 10:25 ` [PATCH v3 1/5] mtd: atmel_nand: Support variable RB_EDGE interrupts Romain Izard
2016-02-01 10:25 ` [PATCH v3 2/5] dt-bindings: atmel_nand: Reword the documenation Romain Izard
2016-02-01 10:25 ` [PATCH v3 3/5] mtd: atmel_nand: Support PMECC on SAMA5D2 Romain Izard
2016-02-01 10:25 ` [PATCH v3 4/5] mtd: atmel_nand: Support 32-bit ECC strength Romain Izard
2016-02-01 10:26 ` [PATCH v3 5/5] ARM: at91/dt: sama5d2: add nand0 and nfc0 nodes Romain Izard
2016-02-03 6:54 ` Yang, Wenyou [this message]
2016-02-04 13:33 ` [PATCH v3 0/5] mtd: atmel_nand: Add support for NAND Flash on SAMA5D2 Boris Brezillon
2016-02-04 14:43 ` Romain Izard
2016-03-01 10:27 ` Nicolas Ferre
2016-03-01 11:29 ` Romain Izard
2016-03-01 12:27 ` 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=56B1A428.2060500@atmel.com \
--to=wenyou.yang@atmel.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nicolas.ferre@atmel.com \
--cc=rainyfeeling@outlook.com \
--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).