From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: Daniel Mack <daniel@zonque.org>,
Richard Weinberger <richard.weinberger@gmail.com>,
stable@vger.kernel.org, linux-mtd@lists.infradead.org,
haojian.zhuang@gmail.com, robert.jarzmik@free.fr,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mtd: rawnand: marvell: select target before setting up data interface
Date: Fri, 5 Apr 2019 11:48:35 +0200 [thread overview]
Message-ID: <20190405114835.2696ef69@xps13> (raw)
In-Reply-To: <20190330192036.193e9e1c@collabora.com>
Hi Daniel,
Boris Brezillon <boris.brezillon@collabora.com> wrote on Sat, 30 Mar
2019 19:20:36 +0100:
> On Mon, 25 Mar 2019 17:21:42 +0100
> Daniel Mack <daniel@zonque.org> wrote:
>
> > Hi Miquel,
> >
> > On 25/3/2019 10:09 AM, Miquel Raynal wrote:
> > > Daniel Mack <daniel@zonque.org> wrote on Fri, 22 Mar 2019 19:48:08
> > > +0100:
> > >
> > >> Hi Miquel,
> > >>
> > >> On 22/3/2019 9:30 AM, Miquel Raynal wrote:
> > >>> + Richard: this is fixes materials
> > >>>
> > >>> Daniel Mack <daniel@zonque.org> wrote on Thu, 21 Mar 2019 22:20:10
> > >>> +0100:
> > >>>
> > >>>> Now that the nand drivers are responsible for selecting the target
> > >>>> prior to hardware access, a call to marvell_nfc_select_target() is
> > >>>> necessary from marvell_nfc_setup_data_interface().
> > >>>>
> > >>>> This is a regression introduced by commit b25251414f6e ("mtd:
> > >>>> rawnand: marvell: Stop implementing ->select_chip()").
> > >>>>
> > >>>> Fixes: b25251414f6e ("mtd: rawnand: marvell: Stop implementing ->select_chip()")
> > >>>> Cc: Boris Brezillon <boris.brezillon@collabora.com>
> > >>>> Cc: <stable@vger.kernel.org>
> > >>>> Signed-off-by: Daniel Mack <daniel@zonque.org>
> > >>>> ---
> > >>>> drivers/mtd/nand/raw/marvell_nand.c | 2 ++
> > >>>> 1 file changed, 2 insertions(+)
> > >>>>
> > >>>> diff --git a/drivers/mtd/nand/raw/marvell_nand.c b/drivers/mtd/nand/raw/marvell_nand.c
> > >>>> index 84283c6bb0ff..93abe5be8995 100644
> > >>>> --- a/drivers/mtd/nand/raw/marvell_nand.c
> > >>>> +++ b/drivers/mtd/nand/raw/marvell_nand.c
> > >>>> @@ -2325,6 +2325,8 @@ static int marvell_nfc_setup_data_interface(struct nand_chip *chip, int chipnr,
> > >>>> struct marvell_nfc_timings nfc_tmg;
> > >>>> int read_delay;
> > >>>>
> > >>>> + marvell_nfc_select_target(chip, chip->cur_cs);
> > >>>> +
> > >>>> sdr = nand_get_sdr_timings(conf);
> > >>>> if (IS_ERR(sdr))
> > >>>> return PTR_ERR(sdr);
> > >>>
> > >>> I had a short look yesterday and this is very likely to be the root
> > >>> cause of the regression, thank you very much!
> > >>
> > >> Yes it is, it fixes the regression I have reported.
> > >>
> > >> Do you want me to resend with that nit addressed you mentioned? My
> > >> version works well, I know that much :)
> > >
> > > Yes please, resent with Boris' comment addressed and we'll be fine.
> >
> > I tried this now, and with 'chip->cur_cs' instead of 'chipnr', the
> > regression is back. This function is invoked twice during boot, and in
> > both cases, 'chip->cur_cs' is -1, while 'chipnr' is 0. The 2nd time this
> > function is invoked, the 'selected_die' cache value is 0, so
> > marvell_nfc_select_target() bails early, which seems to be a problem.
> >
> > I can't quite make sense of that yet, all I know is that calling
> > marvell_nfc_select_target() with -1 from
> > marvell_nfc_setup_data_interface() makes the driver functional again. Hmm.
>
> Can you try with the following diff applied?
> --->8---
> diff --git a/drivers/mtd/nand/raw/marvell_nand.c b/drivers/mtd/nand/raw/marvell_nand.c
> index f38e5c1b87e4..e8eccf6afc8f 100644
> --- a/drivers/mtd/nand/raw/marvell_nand.c
> +++ b/drivers/mtd/nand/raw/marvell_nand.c
> @@ -722,9 +722,6 @@ static void marvell_nfc_select_target(struct nand_chip *chip,
> struct marvell_nfc *nfc = to_marvell_nfc(chip->controller);
> u32 ndcr_generic;
>
> - if (chip == nfc->selected_chip && die_nr == marvell_nand->selected_die)
> - return;
> -
> writel_relaxed(marvell_nand->ndtr0, nfc->regs + NDTR0);
> writel_relaxed(marvell_nand->ndtr1, nfc->regs + NDTR1);
>
I tested on a pxa board and an armada board and I don't reproduce the
bug without this change. What is special with your setup?
I was trying to understand the fix to write a decent commit log but as
I cannot reproduce I am stuck. So if you need this fix please send the
patch with, hopefully, an explanation of what's wrong.
Thank you!
Miquèl
prev parent reply other threads:[~2019-04-05 9:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 21:20 [PATCH] mtd: rawnand: marvell: select target before setting up data interface Daniel Mack
2019-03-22 8:30 ` Miquel Raynal
2019-03-22 9:05 ` Boris Brezillon
2019-03-22 18:48 ` Daniel Mack
2019-03-25 9:09 ` Miquel Raynal
2019-03-25 16:21 ` Daniel Mack
2019-03-30 18:09 ` Boris Brezillon
2019-03-30 18:20 ` Boris Brezillon
2019-04-01 15:29 ` Daniel Mack
2019-04-05 9:48 ` Miquel Raynal [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=20190405114835.2696ef69@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=boris.brezillon@collabora.com \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@gmail.com \
--cc=robert.jarzmik@free.fr \
--cc=stable@vger.kernel.org \
/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).