linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] Introduce the new NAND core interface: ->exec_op()
Date: Fri, 1 Dec 2017 10:37:48 +0100	[thread overview]
Message-ID: <20171201103748.5bbd8ccc@bbrezillon> (raw)
In-Reply-To: <20171130170132.27522-1-miquel.raynal@free-electrons.com>

Hi all,

On Thu, 30 Nov 2017 18:01:27 +0100
Miquel Raynal <miquel.raynal@free-electrons.com> wrote:

> Hi,
> 
> This series adds the implementation of the NAND framework ->exec_op()
> interface with all the related hooks and helpers. The reasons for adding
> it are explained in details in the commit log:
> 
>         "mtd: nand: add ->exec_op() implementation"
> 
> Long story short: it will ease later expansion of the framework, as well
> as the implementation of new vendor specific commands, and should also
> ease driver development.
> 
> A lot of comments are written to explain how to use the new API. Several
> NAND controller drivers are already/almost converted to ->exec_op(), in
> particular a rework of the Marvell NAND controller driver, and will
> follow. One can have a look at them as examples to understand how to
> implement or rework NAND controller drivers. A proper external
> documentation is being written and will later be submitted.
> 
> Thank you,
> Miqu?l
> 
> 
> Boris Brezillon (2):
>   mtd: nand: provide several helpers to do common NAND operations
>   mtd: nand: force drivers to explicitly send READ/PROG commands
> 
> Miquel Raynal (3):
>   mtd: nand: use usual return values for the ->erase() hook
>   mtd: nand: use a static data_interface in the nand_chip structure
>   mtd: nand: add ->exec_op() implementation

Applied patches 1 to 4 (with a rewording of patch 4 commit message and
a fix in patch 1 to make single_erase() compliant with the new
->erase() semantic).

Note that I was prompt to apply those patches because I want them to
spend as much time as possible in linux-next so that we can detect and
fix regressions before the merge window. So please test linux-next on
your hardware.

This being said, nothing is set in stone, and if the series appears to
break existing setups and we can't fix the problems before -rc6, I'll
drop it.

Thanks,

Boris

> 
>  drivers/mtd/nand/atmel/nand-controller.c      |    9 +-
>  drivers/mtd/nand/bf5xx_nand.c                 |    6 +-
>  drivers/mtd/nand/brcmnand/brcmnand.c          |   20 +-
>  drivers/mtd/nand/cafe_nand.c                  |   20 +-
>  drivers/mtd/nand/denali.c                     |   40 +-
>  drivers/mtd/nand/diskonchip.c                 |    4 +-
>  drivers/mtd/nand/docg4.c                      |   21 +-
>  drivers/mtd/nand/fsl_elbc_nand.c              |   10 +-
>  drivers/mtd/nand/fsl_ifc_nand.c               |    6 +-
>  drivers/mtd/nand/fsmc_nand.c                  |    5 +-
>  drivers/mtd/nand/gpmi-nand/gpmi-nand.c        |   77 +-
>  drivers/mtd/nand/hisi504_nand.c               |    9 +-
>  drivers/mtd/nand/jz4740_nand.c                |   16 +-
>  drivers/mtd/nand/lpc32xx_mlc.c                |    7 +-
>  drivers/mtd/nand/lpc32xx_slc.c                |   33 +-
>  drivers/mtd/nand/mtk_nand.c                   |   25 +-
>  drivers/mtd/nand/nand_base.c                  | 2161 ++++++++++++++++++++++---
>  drivers/mtd/nand/nand_hynix.c                 |  124 +-
>  drivers/mtd/nand/nand_micron.c                |   83 +-
>  drivers/mtd/nand/nand_timings.c               |   21 +-
>  drivers/mtd/nand/omap2.c                      |   18 +-
>  drivers/mtd/nand/pxa3xx_nand.c                |   14 +-
>  drivers/mtd/nand/qcom_nandc.c                 |   27 +-
>  drivers/mtd/nand/r852.c                       |   11 +-
>  drivers/mtd/nand/sh_flctl.c                   |    6 +-
>  drivers/mtd/nand/sunxi_nand.c                 |   97 +-
>  drivers/mtd/nand/tango_nand.c                 |   27 +-
>  drivers/mtd/nand/tmio_nand.c                  |    5 +-
>  drivers/mtd/nand/vf610_nfc.c                  |    6 +-
>  drivers/staging/mt29f_spinand/mt29f_spinand.c |    5 +-
>  include/linux/mtd/rawnand.h                   |  414 ++++-
>  31 files changed, 2673 insertions(+), 654 deletions(-)
> 

      parent reply	other threads:[~2017-12-01  9:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30 17:01 [PATCH 0/5] Introduce the new NAND core interface: ->exec_op() Miquel Raynal
2017-11-30 17:01 ` [PATCH 1/5] mtd: nand: use usual return values for the ->erase() hook Miquel Raynal
2017-11-30 20:51   ` Boris Brezillon
2017-11-30 22:02     ` Miquel RAYNAL
2017-12-01  2:12       ` Masahiro Yamada
2017-12-01  9:39       ` Boris Brezillon
2017-11-30 17:01 ` [PATCH 2/5] mtd: nand: provide several helpers to do common NAND operations Miquel Raynal
2017-12-01  2:38   ` Masahiro Yamada
2017-11-30 17:01 ` [PATCH 3/5] mtd: nand: force drivers to explicitly send READ/PROG commands Miquel Raynal
2017-12-01  2:39   ` Masahiro Yamada
2017-11-30 17:01 ` [PATCH 4/5] mtd: nand: use a static data_interface in the nand_chip structure Miquel Raynal
2017-12-01  9:38   ` Boris Brezillon
2017-11-30 17:01 ` [PATCH 5/5] mtd: nand: add ->exec_op() implementation Miquel Raynal
2017-11-30 20:50   ` Boris Brezillon
2017-11-30 22:25     ` Miquel RAYNAL
2017-12-01  9:50       ` Boris Brezillon
2017-12-01  9:57         ` Miquel RAYNAL
2017-12-01 11:07   ` Boris Brezillon
2017-12-01  9:37 ` 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=20171201103748.5bbd8ccc@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).