From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] mtd: nand: fsmc: support SDR timing configuration
Date: Mon, 15 May 2017 21:36:13 +0200 [thread overview]
Message-ID: <20170515213613.47bfa595@bbrezillon> (raw)
In-Reply-To: <1493455956-18362-1-git-send-email-thomas.petazzoni@free-electrons.com>
On Sat, 29 Apr 2017 10:52:33 +0200
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> This patch series add support for configuring the FSMC NAND controller
> timings according to the SDR timings exposed by the NAND chip.
>
> Changes since v1:
>
> - Dropped all patches from the series that have already been merged
> in nand/next.
>
> - Rework the implementation as suggested by Boris Brezillon, i.e by
> implementing ->setup_data_interface() only when we are going to use
> the NAND SDR timings. If there is a "timings" DT property, we keep
> using the old strategy without ->setup_data_interface().
>
> The patch series is based on the nand/next branch.
Applied to nand/next.
Thanks,
Boris
>
> Best regards,
>
> Thomas
>
> Thomas Petazzoni (3):
> mtd: nand: fsmc: reduce number of arguments of fsmc_nand_setup()
> mtd: nand: fsmc: add support for SDR timings
> mtd: nand: fsmc: remove default timings
>
> drivers/mtd/nand/fsmc_nand.c | 120 +++++++++++++++++++++++++++++++++----------
> 1 file changed, 94 insertions(+), 26 deletions(-)
>
prev parent reply other threads:[~2017-05-15 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 8:52 [PATCH v2 0/3] mtd: nand: fsmc: support SDR timing configuration Thomas Petazzoni
2017-04-29 8:52 ` [PATCH v2 1/3] mtd: nand: fsmc: reduce number of arguments of fsmc_nand_setup() Thomas Petazzoni
2017-04-29 8:52 ` [PATCH v2 2/3] mtd: nand: fsmc: add support for SDR timings Thomas Petazzoni
2017-04-29 8:52 ` [PATCH v2 3/3] mtd: nand: fsmc: remove default timings Thomas Petazzoni
2017-05-15 19:36 ` 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=20170515213613.47bfa595@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).