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 v2 3/8] MTD: xway: the latched command should be persistent
Date: Sun, 19 Jun 2016 14:09:51 +0200 [thread overview]
Message-ID: <20160619140951.41b0cada@bbrezillon> (raw)
In-Reply-To: <8ca1d792-e73b-ab5c-f832-7469879ad678@hauke-m.de>
On Sun, 19 Jun 2016 14:04:51 +0200
Hauke Mehrtens <hauke@hauke-m.de> wrote:
> On 06/19/2016 01:52 PM, Boris Brezillon wrote:
> > On Sat, 18 Jun 2016 21:14:07 +0200
> > Hauke Mehrtens <hauke@hauke-m.de> wrote:
> >
> >> From: John Crispin <john@phrozen.org>
> >>
> >> If they are not persistent a different address will be used and the
> >> controller will deactivate some pins.
> >>
> >> Signed-off-by: John Crispin <john@phrozen.org>
> >> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
> >> ---
> >> drivers/mtd/nand/xway_nand.c | 16 ++++++++--------
> >> 1 file changed, 8 insertions(+), 8 deletions(-)
> >>
> >> diff --git a/drivers/mtd/nand/xway_nand.c b/drivers/mtd/nand/xway_nand.c
> >> index 2889e48..346781a 100644
> >> --- a/drivers/mtd/nand/xway_nand.c
> >> +++ b/drivers/mtd/nand/xway_nand.c
> >> @@ -67,6 +67,7 @@
> >>
> >> struct xway_nand_data {
> >> struct nand_chip chip;
> >> + u32 xway_latchcmd;
> >> };
> >>
> >> static void xway_reset_chip(struct nand_chip *chip)
> >> @@ -104,22 +105,21 @@ static void xway_select_chip(struct mtd_info *mtd, int chip)
> >>
> >> static void xway_cmd_ctrl(struct mtd_info *mtd, int cmd, unsigned int ctrl)
> >> {
> >> - struct nand_chip *this = mtd_to_nand(mtd);
> >> - unsigned long nandaddr = (unsigned long) this->IO_ADDR_W;
> >> + struct nand_chip *chip = mtd_to_nand(mtd);
> >> + struct xway_nand_data *data = nand_get_controller_data(chip);
> >> + unsigned long nandaddr = (unsigned long) chip->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;
> >> + data->xway_latchcmd = NAND_WRITE_CMD;
> >> + else if (ctrl & NAND_ALE)
> >> + data->xway_latchcmd = NAND_WRITE_ADDR;
> >> }
> >>
> >> if (cmd != NAND_CMD_NONE) {
> >> spin_lock_irqsave(&ebu_lock, flags);
> >> - writeb(cmd, this->IO_ADDR_W);
> >> + writeb(cmd, (void __iomem *) (nandaddr | data->xway_latchcmd));
> >> while ((ltq_ebu_r32(EBU_NAND_WAIT) & NAND_WAIT_WR_C) == 0)
> >> ;
> >> spin_unlock_irqrestore(&ebu_lock, flags);
> >
> > Not sure what you're trying to do exactly. AFAICS, your controller seems
> > to handle each addr and cmd cycles independently, so all you have to do
> > is something like that:
> >
> > /*
> > * I'm assuming baseaddr has been initialized to the NAND
> > * controller base address.
> > */
> >
> > if (cmd == NAND_CMD_NONE)
> > return;
> >
> > spin_lock_irqsave(&ebu_lock, flags);
> > if (ctrl & NAND_CLE)
> > writeb(cmd, baseaddr + NAND_WRITE_CMD);
> > else
> > writeb(cmd, baseaddr + NAND_WRITE_ADDR);
> >
> > while ((ltq_ebu_r32(EBU_NAND_WAIT) & NAND_WAIT_WR_C) == 0)
> > ;
> > spin_unlock_irqrestore(&ebu_lock, flags);
> >
>
> Is NAND_CLE always set when the line to the NAND flash chip should be
> set?
Yes it is (see the nand_command() [1] and nand_command_lp() [2]
implementations).
> Then this should work and we ignore NAND_CTRL_CHANGE .
>
> Hauke
[1]http://lxr.free-electrons.com/source/drivers/mtd/nand/nand_base.c#L588
[2]http://lxr.free-electrons.com/source/drivers/mtd/nand/nand_base.c#L691
next prev parent reply other threads:[~2016-06-19 12:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 19:14 [PATCH v2 0/8] MTD: xway: fix driver Hauke Mehrtens
2016-06-18 19:14 ` [PATCH v2 1/8] MTD: xway: convert to normal platform driver Hauke Mehrtens
2016-06-19 11:32 ` Boris Brezillon
2016-06-19 11:58 ` Hauke Mehrtens
2016-06-18 19:14 ` [PATCH v2 2/8] MTD: xway: add some more documentation Hauke Mehrtens
2016-06-19 11:39 ` Boris Brezillon
2016-06-18 19:14 ` [PATCH v2 3/8] MTD: xway: the latched command should be persistent Hauke Mehrtens
2016-06-19 11:52 ` Boris Brezillon
2016-06-19 12:04 ` Hauke Mehrtens
2016-06-19 12:09 ` Boris Brezillon [this message]
2016-06-18 19:14 ` [PATCH v2 4/8] MTD: xway: remove endless loop Hauke Mehrtens
2016-06-19 12:14 ` Boris Brezillon
2016-06-19 12:32 ` Hauke Mehrtens
2016-06-19 12:57 ` Boris Brezillon
2016-06-18 19:14 ` [PATCH v2 5/8] MTD: xway: add missing write_buf and read_buf to nand driver Hauke Mehrtens
2016-06-19 12:38 ` Boris Brezillon
2016-06-18 19:14 ` [PATCH v2 6/8] MTD: xway: fix nand locking Hauke Mehrtens
2016-06-19 12:41 ` Boris Brezillon
2016-06-19 12:53 ` Richard Weinberger
2016-06-19 12:56 ` Hauke Mehrtens
2016-06-19 13:04 ` Boris Brezillon
2016-06-19 12:58 ` Boris Brezillon
2016-06-18 19:14 ` [PATCH v2 7/8] MTD: xway: extract read and write function Hauke Mehrtens
2016-06-19 12:42 ` Boris Brezillon
2016-06-18 19:14 ` [PATCH v2 8/8] MTD: xway: use global NAND_CMD_RESET define Hauke Mehrtens
2016-06-19 13:06 ` Boris Brezillon
2016-06-19 12:50 ` [PATCH v2 0/8] MTD: xway: fix driver Boris Brezillon
2016-06-19 13:13 ` Hauke Mehrtens
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=20160619140951.41b0cada@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.