From: Brian Norris <computersforpeace@gmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-mtd@lists.infradead.org, Mike Dunn <mikedunn@newsguy.com>
Subject: Re: [PATCH] mtd: nand: refactor erase_cmd() to return chip status
Date: Wed, 7 May 2014 10:12:29 -0700 [thread overview]
Message-ID: <20140507171229.GD28907@ld-irv-0074> (raw)
In-Reply-To: <CAF2Aj3hB-6=yfCOhqXrWGcPey1DEGqkUfkEsRdrQbXz80s_sug@mail.gmail.com>
(Your reply was multipart HTML/Text, so the list probably bounced you)
On Wed, May 07, 2014 at 11:59:56AM +0100, Lee Jones wrote:
> On 7 May 2014 00:12, "Brian Norris" <computersforpeace@gmail.com>
> wrote:
> >
> > The nand_chip::erase_cmd callback previously served a dual purpose; for
> > one, it allowed a per-flash-chip override, so that AG-AND devices could
> > use a different erase command than other NAND. These AND devices were
> > dropped in commit xxxxx. On the other hand, some drivers (denali and
> I think you still need to fill this in.
Yes... I should re-read my commit messages before sending! This should
be:
commit 14c6578683367b1e7af0c3c09e872b45a45183a7
(mtd: nand: remove AG-AND support)
> > doc-g4) need to use this sort of callback to implement
> > controller-specific erase operations.
> >
> > To make the latter operation easier for some drivers (e.g., ST's new BCH
> > NAND driver), it helps if the command dispatch and wait functions can be
> > lumped together, rather than called separately.
> >
> > This patch does two things:
> > Â 1. Pull the call to chip->waitfunc() into chip->erase_cmd(), and return
> > Â Â the status from this callback
> > Â 2. Rename erase_cmd() to just erase(), since this callback does a
> > Â Â little more than just send a command
> >
> > Signed-off-by: Brian Norris <computersforpeace@gmail.com>
> > Cc: Mike Dunn <mikedunn@newsguy.com>
> > Cc: Lee Jones <lee.jones@linaro.org>
> > ---
> >  drivers/mtd/nand/denali.c   |  7 +++----
> >  drivers/mtd/nand/docg4.c   |  6 ++++--
> > Â drivers/mtd/nand/nand_base.c | 14 +++++++-------
> >  include/linux/mtd/nand.h   |  5 ++---
> > Â 4 files changed, 16 insertions(+), 16 deletions(-)
> If the code hasn't changed since the pastebin:
> Tested-by: Lee Jones <lee.jones@linaro.org>
It is the same.
I've updated my commit message locally. I'll give this a few days, then
push the patch.
Thanks,
Brian
next prev parent reply other threads:[~2014-05-07 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 23:11 [PATCH] mtd: nand: refactor erase_cmd() to return chip status Brian Norris
[not found] ` <CAF2Aj3hB-6=yfCOhqXrWGcPey1DEGqkUfkEsRdrQbXz80s_sug@mail.gmail.com>
2014-05-07 17:12 ` Brian Norris [this message]
2014-05-09 20:21 ` Brian Norris
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=20140507171229.GD28907@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mikedunn@newsguy.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