public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Arseniy Krasnov <avkrasnov@sberdevices.ru>
Cc: <oxffffaa@gmail.com>, <kernel@sberdevices.ru>,
	<stable@vger.kernel.org>, <linux-mtd@lists.infradead.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-amlogic@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	Liang Yang <liang.yang@amlogic.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Jerome Brunet <jbrunet@baylibre.com>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	Kevin Hilman <khilman@baylibre.com>,
	Jianxin Pan <jianxin.pan@amlogic.com>
Subject: Re: [PATCH v1] mtd: rawnand: meson: fix ready/busy command
Date: Mon, 5 Jun 2023 11:50:33 +0200	[thread overview]
Message-ID: <20230605115033.7a9eb4c9@xps-13> (raw)
In-Reply-To: <9bea333a-e5fc-af89-29a0-fa01236488a3@sberdevices.ru>

Hi Arseniy,

avkrasnov@sberdevices.ru wrote on Mon, 5 Jun 2023 11:27:34 +0300:

> On 05.06.2023 11:17, Miquel Raynal wrote:
> > Hi Arseniy,
> > 
> > avkrasnov@sberdevices.ru wrote on Mon, 5 Jun 2023 09:39:40 +0300:
> >   
> >> Hello Miquel!
> >>
> >> I exclude this patch from the recent Meson patchset, as it is fix and not related to another patches.
> >> Also I think that I can split Meson patchset (from links below) in the following way:
> >> 1) Patch/patchset for OOB layout
> >> 2) Patchset for "nand-rb" logic (meson_nand.c + DT bindings)
> >> These two can also go independently:
> >> 3) https://lore.kernel.org/linux-mtd/20230601061850.3907800-6-AVKrasnov@sberdevices.ru/
> >> 4) https://lore.kernel.org/linux-mtd/20230601061850.3907800-7-AVKrasnov@sberdevices.ru/  
> > 
> > LGTM.  
> 
> I think we don't need this patch with new RB_INT value. I dive into conversations with Liang Yang - author of this driver. He said,
> that this define is "special" polling mode. Now I'm a little bit more experienced in NAND area, so IIUC we have two basic waiting modes:
> 1) Software, by sending status command, then polling reply from controller, and then finally send READ0 to exit status reading mode (nand_soft_waitrdy()).

This is useful...

> 2) By RB pin and interrupt - in this mode we send vendor specific command to the controller and it triggers interrupt on RB pin update.
>    In this case RB pin must be connected to the controller. This mode is already implemented by Liang Yang.

...this is useful...

> 
> Now, command with this new define works in the following way: we send status command, by instead of reading reply from it by software,
> controller itself checks RB pin and status ready bit in IO bus. Driver just waits on completion. After waiting we need to send
> READ0 command again to make controller leave status reading mode. I think this is like "intermediate" mode between software polling
> and hardware interrupt - there is no need to spin in loop, waiting for status ready bit, but still need to leave status mode by sending
> READ0 command. I'm not sure that we need this as third mode of waiting for command is done. May be at least not in this work on Meson driver,
> so I guess to drop this patch at  this moment and add 'nand_soft_waitrdy()' support.

...I agree we can skip this one.

Thanks,
Miquèl

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-06-05  9:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05  6:10 [PATCH v1] mtd: rawnand: meson: fix ready/busy command Arseniy Krasnov
2023-06-05  6:39 ` Arseniy Krasnov
2023-06-05  8:17   ` Miquel Raynal
2023-06-05  8:27     ` Arseniy Krasnov
2023-06-05  9:50       ` Miquel Raynal [this message]
2023-06-05  7:05 ` Greg KH
2023-06-05  7:50   ` Arseniy Krasnov

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=20230605115033.7a9eb4c9@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=avkrasnov@sberdevices.ru \
    --cc=jbrunet@baylibre.com \
    --cc=jianxin.pan@amlogic.com \
    --cc=kernel@sberdevices.ru \
    --cc=khilman@baylibre.com \
    --cc=liang.yang@amlogic.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=neil.armstrong@linaro.org \
    --cc=oxffffaa@gmail.com \
    --cc=richard@nod.at \
    --cc=stable@vger.kernel.org \
    --cc=vigneshr@ti.com \
    /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