From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Richard Weinberger <richard@nod.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: nand: Fix nand_command_lp() for 8bits opcodes
Date: Fri, 16 Sep 2016 15:16:20 +0200 [thread overview]
Message-ID: <20160916151620.0572d21d@bbrezillon> (raw)
In-Reply-To: <1465988991-1220-1-git-send-email-boris.brezillon@free-electrons.com>
On Wed, 15 Jun 2016 13:09:51 +0200
Boris Brezillon <boris.brezillon@free-electrons.com> wrote:
> 8 bits opcodes should be followed by a single address cycle. Make the
> 2nd address cycle dependent of !nand_opcode_8bits(command).
Applied.
>
> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> ---
> drivers/mtd/nand/nand_base.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c
> index 0b0dc29..c2f83236 100644
> --- a/drivers/mtd/nand/nand_base.c
> +++ b/drivers/mtd/nand/nand_base.c
> @@ -745,7 +745,10 @@ static void nand_command_lp(struct mtd_info *mtd, unsigned int command,
> column >>= 1;
> chip->cmd_ctrl(mtd, column, ctrl);
> ctrl &= ~NAND_CTRL_CHANGE;
> - chip->cmd_ctrl(mtd, column >> 8, ctrl);
> +
> + /* Only ouput a single addr cycle for 8bits opcodes. */
> + if (!nand_opcode_8bits(command))
> + chip->cmd_ctrl(mtd, column >> 8, ctrl);
> }
> if (page_addr != -1) {
> chip->cmd_ctrl(mtd, page_addr, ctrl);
prev parent reply other threads:[~2016-09-16 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 11:09 [PATCH] mtd: nand: Fix nand_command_lp() for 8bits opcodes Boris Brezillon
2016-09-16 13:16 ` 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=20160916151620.0572d21d@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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