From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: richard@nod.at, dwmw2@infradead.org, computersforpeace@gmail.com,
linux-mtd@lists.infradead.org, john@phrozen.org
Subject: Re: [PATCH v3 3/8] MTD: xway: the latched command should be persistent
Date: Sun, 19 Jun 2016 18:22:32 +0200 [thread overview]
Message-ID: <20160619182232.500f75fc@bbrezillon> (raw)
In-Reply-To: <1466352497-6806-4-git-send-email-hauke@hauke-m.de>
On Sun, 19 Jun 2016 18:08:12 +0200
Hauke Mehrtens <hauke@hauke-m.de> wrote:
> From: John Crispin <john@phrozen.org>
>
> With each write the pins on the NAND flash chip have to be activated.
> Instead of setting them only when NAND_CTRL_CHANGE is given, always set
> them.
This commit message is a bit fuzzy. How about:
"
mtd: nand: xway: Avoid messing up with IO_ADDR_W in ->cmd_ctrl()
The ->cmd_ctrl() function is adjusting the ->IO_ADDR_W value depending
on the command type each time NAND_CTRL_CHANGE is passed. This is not
only useless but can lead to an ->IO_ADDR_W corruption.
Get rid of this logic and rely on the NAND_CLE and NAND_ALE flags to
deduce the iomem address to write the cmd argument to.
"
BTW, please use the "mtd: nand: <nand-controller-driver>: " prefix in
your subject line (this applies to all the patches you sent so far).
>
> Signed-off-by: John Crispin <john@phrozen.org>
> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
> ---
> drivers/mtd/nand/xway_nand.c | 26 +++++++++++---------------
> 1 file changed, 11 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/mtd/nand/xway_nand.c b/drivers/mtd/nand/xway_nand.c
> index ec189e5..6028edb 100644
> --- a/drivers/mtd/nand/xway_nand.c
> +++ b/drivers/mtd/nand/xway_nand.c
> @@ -107,22 +107,18 @@ static void xway_cmd_ctrl(struct mtd_info *mtd, int cmd, unsigned int ctrl)
> unsigned long nandaddr = (unsigned long) this->IO_ADDR_W;
> unsigned long flags;
>
> - if (ctrl & NAND_CTRL_CHANGE) {
> - nandaddr &= ~(NAND_WRITE_CMD | NAND_WRITE_ADDR);
> - if (ctrl & NAND_CLE)
> - nandaddr |= NAND_WRITE_CMD;
> - else
> - nandaddr |= NAND_WRITE_ADDR;
> - this->IO_ADDR_W = (void __iomem *) nandaddr;
> - }
> + if (cmd == NAND_CMD_NONE)
> + return;
>
> - if (cmd != NAND_CMD_NONE) {
> - spin_lock_irqsave(&ebu_lock, flags);
> - writeb(cmd, this->IO_ADDR_W);
> - while ((ltq_ebu_r32(EBU_NAND_WAIT) & NAND_WAIT_WR_C) == 0)
> - ;
> - spin_unlock_irqrestore(&ebu_lock, flags);
> - }
> + spin_lock_irqsave(&ebu_lock, flags);
> + if (ctrl & NAND_CLE)
> + writeb(cmd, (void __iomem *) (nandaddr | NAND_WRITE_CMD));
> + else if (ctrl & NAND_ALE)
> + writeb(cmd, (void __iomem *) (nandaddr | NAND_WRITE_ADDR));
> +
> + while ((ltq_ebu_r32(EBU_NAND_WAIT) & NAND_WAIT_WR_C) == 0)
> + ;
> + spin_unlock_irqrestore(&ebu_lock, flags);
> }
>
> static int xway_dev_ready(struct mtd_info *mtd)
next prev parent reply other threads:[~2016-06-19 16:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 16:08 [PATCH v3 0/8] MTD: xway: fix driver Hauke Mehrtens
2016-06-19 16:08 ` [PATCH v3 1/8] MTD: xway: add some more documentation Hauke Mehrtens
2016-06-19 16:14 ` Boris Brezillon
2016-06-19 16:32 ` Hauke Mehrtens
2016-06-19 16:08 ` [PATCH v3 2/8] MTD: xway: convert to normal platform driver Hauke Mehrtens
2016-06-19 16:08 ` [PATCH v3 3/8] MTD: xway: the latched command should be persistent Hauke Mehrtens
2016-06-19 16:22 ` Boris Brezillon [this message]
2016-06-19 16:08 ` [PATCH v3 4/8] MTD: xway: use generic reset function Hauke Mehrtens
2016-06-19 16:08 ` [PATCH v3 5/8] MTD: xway: fix nand locking Hauke Mehrtens
2016-06-19 16:26 ` Boris Brezillon
2016-06-19 16:34 ` Hauke Mehrtens
2016-06-19 16:40 ` Boris Brezillon
2016-06-19 16:08 ` [PATCH v3 6/8] MTD: xway: extract read and write function Hauke Mehrtens
2016-06-19 16:08 ` [PATCH v3 7/8] MTD: xway: add nandaddr to own struct Hauke Mehrtens
2016-06-19 16:29 ` Boris Brezillon
2016-06-19 16:32 ` Boris Brezillon
2016-06-19 16:35 ` Hauke Mehrtens
2016-06-19 16:08 ` [PATCH v3 8/8] MTD: xway: add missing write_buf and read_buf to nand driver Hauke Mehrtens
2016-06-19 16:32 ` Boris Brezillon
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=20160619182232.500f75fc@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=hauke@hauke-m.de \
--cc=john@phrozen.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;
as well as URLs for NNTP newsgroup(s).