public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
Cc: Miquel Raynal <miquel.raynal@free-electrons.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Brian Norris <computersforpeace@gmail.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Chen-Yu Tsai <wens@csie.org>,
	Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
	Daniel Mack <daniel@zonque.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Gregory Clement <gregory.clement@free-electrons.com>,
	Han Xu <han.xu@nxp.com>,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	Jason Cooper <jason@lakedaemon.net>,
	Josh Wu <rainyfeeling@outlook.com>,
	Kamal Dasu <kdasu.kdev@gmail.com>,
	Marek Vasut <marek.vasut@gmail.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Maxime Ripard <maxime.ripard@free-electrons.com>,
	Maxim Levitsky <maximlevitsky@gmail.com>,
	Richard Weinberger <richard@nod.at>,
	Robert Jarzmik <robert.jarzmik@free.fr>,
	Rob Herring <robh+dt@kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Stefan Agner <stefan@agner.ch>,
	Sylvain Lemieux <slemieux.tyco@gmail.com>,
	Vladimir Zapolskiy <vz@mleia.com>,
	Wenyou Yang <wenyou.yang@atmel.com>,
	Will Deacon <will.deacon@arm.com>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Antoine Tenart <antoine.tenart@free-electrons.com>,
	Igor Grinberg <grinberg@compulab.co.il>,
	Nadav Haklai <nadavh@marvell.com>,
	Ofer Heifetz <oferh@marvell.com>,
	Neta Zur Hershkovits <neta@marvell.com>,
	Hanna Hawa <hannah@marvell.com>,
	linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: [RFC 00/12] Marvell NAND controller rework with ->exec_op()
Date: Thu, 19 Oct 2017 13:30:40 +0200	[thread overview]
Message-ID: <20171019133040.0c5ded1a@bbrezillon> (raw)
In-Reply-To: <c40bff37-4a8e-2c83-6d2a-b6579ea5233c@sigmadesigns.com>

Hi Marc,

On Thu, 19 Oct 2017 10:47:07 +0200
Marc Gonzalez <marc_gonzalez@sigmadesigns.com> wrote:

> [ Dropping all mailing lists except linux-mtd ]
> 
> On 19/10/2017 00:29, Boris Brezillon wrote:
> 
> > Still need to review patch 6, but I'd like to say I'm really happy to
> > see that happen, finally. Hopefully that will help us make the NAND
> > framework a bit easier to maintain and allow us to support advanced
> > NAND features without having to patch all NAND controller drivers every
> > time we add a new vendor specific operation. I also have in mind a few
> > NAND controller drivers that have been rejected because they were not
> > fitting in the ->cmd_ctrl() approach and I didn't want to add more
> > drivers with their own partially implemented/broken ->cmdfunc() method.
> > 
> > Kudos for the work you've done, and I hope we'll get reviews from other
> > active NAND driver maintainers/contributors. To all NAND driver
> > maintainers: note that the long term goal is to get rid of  
> > ->cmd_ctrl()/cmdfunc()/read/write_buf/byte/word() entirely and replace  
> > them with a single ->exec_op() hook. Please let us know if you need
> > extra things that are not yet exposed in nand_op_instr/nand_op_parser
> > or if you would like things to be done differently.  
> 
> A long time ago, we discussed a limitation of the API for reads
> and writes handling only a single page at a time. My controller
> is able to "burst" 1-15 contiguous pages.
> 
> Does this rewrite help with such a feature, or is it orthogonal?

It's kind of orthogonal. To do what you want to do we'd need to extend
the current nand_chip/nand_ecc_ctrl interfaces to pass the MTD request
directly to the NAND controller driver and let it detect when a burst
access makes sense. Right now this is not my priority, but yes, I've
already thought a bit about how this interface would look like (see
this presentation [1] page 31).

Regards,

Boris

[1]https://events.linuxfoundation.org/sites/events/files/slides/brezillon-nand-framework_0.pdf

      reply	other threads:[~2017-10-19 11:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 14:36 [RFC 00/12] Marvell NAND controller rework with ->exec_op() Miquel Raynal
2017-10-18 14:36 ` [RFC 01/12] mtd: nand: provide several helpers to do common NAND operations Miquel Raynal
2017-10-18 14:36 ` [RFC 02/12] mtd: nand: force drivers to explicitly send READ/PROG commands Miquel Raynal
2017-10-20  9:29   ` Stefan Agner
2017-10-20 11:18     ` Boris Brezillon
2017-11-06 15:02     ` Miquel RAYNAL
2017-10-18 14:36 ` [RFC 03/12] mtd: nand: use a static data_interface in the nand_chip structure Miquel Raynal
2017-10-18 17:02   ` Boris Brezillon
2017-11-03 13:46     ` Miquel RAYNAL
2017-10-18 14:36 ` [RFC 04/12] mtd: nand: add ->exec_op() implementation Miquel Raynal
2017-10-18 21:57   ` Boris Brezillon
2017-11-06 14:09     ` Miquel RAYNAL
2017-10-18 14:36 ` [RFC 05/12] dt-bindings: mtd: add Marvell NAND controller documentation Miquel Raynal
2017-10-18 22:01   ` Boris Brezillon
2017-10-24 19:04   ` Rob Herring
2017-11-06 13:24     ` Miquel RAYNAL
2017-10-18 14:36 ` [RFC 06/12] mtd: nand: add reworked Marvell NAND controller driver Miquel Raynal
2017-10-19  7:18   ` Boris Brezillon
2017-11-06 13:49     ` Miquel RAYNAL
2017-10-18 14:36 ` [RFC 07/12] ARM: dts: armada-370-xp: use reworked " Miquel Raynal
2017-10-18 14:36 ` [RFC 08/12] ARM: dts: armada-375: " Miquel Raynal
2017-10-18 14:36 ` [RFC 09/12] ARM: dts: armada-38x: " Miquel Raynal
2017-10-18 14:36 ` [RFC 10/12] ARM: dts: armada-39x: " Miquel Raynal
2017-10-18 14:36 ` [RFC 11/12] ARM: dts: pxa: " Miquel Raynal
2017-10-18 14:36 ` [RFC 12/12] ARM64: dts: marvell: use reworked NAND controller driver on Armada 7K/8K Miquel Raynal
2017-10-18 22:29 ` [RFC 00/12] Marvell NAND controller rework with ->exec_op() Boris Brezillon
2017-10-19  8:47   ` Marc Gonzalez
2017-10-19 11:30     ` 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=20171019133040.0c5ded1a@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=andrew@lunn.ch \
    --cc=antoine.tenart@free-electrons.com \
    --cc=catalin.marinas@arm.com \
    --cc=computersforpeace@gmail.com \
    --cc=cyrille.pitchen@wedev4u.fr \
    --cc=daniel@zonque.org \
    --cc=dwmw2@infradead.org \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=gregory.clement@free-electrons.com \
    --cc=grinberg@compulab.co.il \
    --cc=han.xu@nxp.com \
    --cc=hannah@marvell.com \
    --cc=haojian.zhuang@gmail.com \
    --cc=jason@lakedaemon.net \
    --cc=kdasu.kdev@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=marc_gonzalez@sigmadesigns.com \
    --cc=marek.vasut@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=maximlevitsky@gmail.com \
    --cc=miquel.raynal@free-electrons.com \
    --cc=nadavh@marvell.com \
    --cc=neta@marvell.com \
    --cc=oferh@marvell.com \
    --cc=rainyfeeling@outlook.com \
    --cc=richard@nod.at \
    --cc=robert.jarzmik@free.fr \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=slemieux.tyco@gmail.com \
    --cc=stefan@agner.ch \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=vz@mleia.com \
    --cc=wens@csie.org \
    --cc=wenyou.yang@atmel.com \
    --cc=will.deacon@arm.com \
    --cc=yamada.masahiro@socionext.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