From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Boris Brezillon <bbrezillon@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Marek Vasut <marek.vasut@gmail.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org,
Richard Weinberger <richard@nod.at>
Subject: Re: [PATCH] mtd: rawnand: fsmc: Keep bank enable bit set
Date: Thu, 10 Jan 2019 09:42:23 +0100 [thread overview]
Message-ID: <20190110094223.2537527c@xps13> (raw)
In-Reply-To: <20190109231259.1ef5d31a@bbrezillon>
Hi Linus,
Please don't forget to Cc: me when it comes to NAND-related changes :)
Boris Brezillon <bbrezillon@kernel.org> wrote on Wed, 9 Jan 2019
23:12:59 +0100:
> On Wed, 9 Jan 2019 22:51:44 +0100
> Linus Walleij <linus.walleij@linaro.org> wrote:
>
> > Hammering the "bank enable" (PBKEN) bit on and off between
> > every command crashes the Nomadik NHK15 with this message:
> >
> > Scanning device for bad blocks
> > Unhandled fault: external abort on non-linefetch (0x008) at 0xcc95e000
> > pgd = (ptrval)
> > [cc95e000] *pgd=0b808811, *pte=40000653, *ppte=40000552
> > Internal error: : 8 [#1] PREEMPT ARM
> > Modules linked in:
> > CPU: 0 PID: 1 Comm: swapper Not tainted 4.20.0-rc2+ #72
> > Hardware name: Nomadik STn8815
> > PC is at fsmc_exec_op+0x194/0x204
> > (...)
> >
> > After a discussion we (me and Boris Brezillion) start to suspect
>
> ^ Brezillon :-)
>
> > that this bit does not immediately control the chip select line
> > at all, it rather enables access to the bank and the hardware
> > will drive the CS autonomously. If there is a NAND chip connected,
> > we should keep this enabled.
> >
> > As fsmc_nand_setup() sets this bit, we can simply remove the
> > offending code.
> >
> > Fixes: 550b9fc4e3af ("mtd: rawnand: fsmc: Stop implementing ->select_chip()")
> > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
>
> Reviewed-by: Boris Brezillon <bbrezillon@kernel.org>
>
> Would be great if someone could validate our assumption with a scope.
> This being said, given the description of the FSMC logic, I have little
> doubt that this bit does not directly controls the CE line, otherwise
> concurrent accesses to different memories on the same bus wouldn't work
> or would require a lot more synchronization than we currently have in
> Linux.
>
Acked-by: Miquel Raynal <miquel.raynal@bootlin.com>
Thanks,
Miquèl
next prev parent reply other threads:[~2019-01-10 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 21:51 [PATCH] mtd: rawnand: fsmc: Keep bank enable bit set Linus Walleij
2019-01-09 22:12 ` Boris Brezillon
2019-01-10 8:42 ` Miquel Raynal [this message]
2019-01-14 8:51 ` Boris Brezillon
2019-01-17 21:33 ` Linus Walleij
2019-01-18 6:36 ` Boris Brezillon
2019-01-18 11:44 ` 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=20190110094223.2537527c@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=bbrezillon@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linus.walleij@linaro.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--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).