From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Christophe LEROY <christophe.leroy@c-s.fr>
Cc: Richard Weinberger <richard@nod.at>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
Cyrille Pitchen <cyrille.pitchen@atmel.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: nand: gpio: make nCE GPIO optional
Date: Mon, 13 Feb 2017 14:22:50 +0100 [thread overview]
Message-ID: <20170213142250.7a10768a@bbrezillon> (raw)
In-Reply-To: <9cadc95b-dc67-9756-c244-9ce452ebeaf7@c-s.fr>
On Mon, 13 Feb 2017 13:58:24 +0100
Christophe LEROY <christophe.leroy@c-s.fr> wrote:
> Le 13/02/2017 à 11:30, Boris Brezillon a écrit :
> > On Fri, 10 Feb 2017 15:01:10 +0100 (CET)
> > Christophe Leroy <christophe.leroy@c-s.fr> wrote:
> >
> >> On some hardware, the nCE signal is wired to the ChipSelect associated
> >> to bus address of the NAND, so it is automatically driven during the
> >> memory access and it is not managed by a GPIO.
> >
> > Hm, I'm not sure how this can work, because, AFAIR, the nCE line needs
> > to stay low for the whole CMD+ADDR[+CMD] cycle, and with your patch
> > it's not guaranteed.
>
> Anyway, the patch just makes it possible to register the device
> allthough nCE GPIO is not defined.
> For people defining the nCE GPIO properly, the patch introduces no
> change at all.
Yes, I know that, just wanted to make sure that not explicitly
controlling the CE line was permitted. Modern controllers are indeed
controlling the CE line, but they usually ask you to specify the whole
CMD+ADDR[+CMD][+DATA] sequence.
>
> >
> > Can you tell us more about your NAND controller?
>
> [ 0.498490] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
> [ 0.504906] nand: Micron MT29F2G08ABAEAWP
> [ 0.508918] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048,
> OOB size: 64
>
> Diagrams on datasheet shows that CE\ can optionnaly go up between each
> access. See attached exemple.
I had a closer look at several datasheets (and the ONFI spec), and it
seems to be allowed as long as you follow the tCS and tCH requirements,
which I guess your controller is ensuring.
>
>
>
> >
> >>
> >> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
> >> ---
> >> drivers/mtd/nand/gpio.c | 18 ++++++++++++------
> >> 1 file changed, 12 insertions(+), 6 deletions(-)
> >>
> >> diff --git a/drivers/mtd/nand/gpio.c b/drivers/mtd/nand/gpio.c
> >> index 0d24857..85294f1 100644
> >> --- a/drivers/mtd/nand/gpio.c
> >> +++ b/drivers/mtd/nand/gpio.c
> >> @@ -78,7 +78,9 @@ static void gpio_nand_cmd_ctrl(struct mtd_info *mtd, int cmd, unsigned int ctrl)
> >> gpio_nand_dosync(gpiomtd);
> >>
> >> if (ctrl & NAND_CTRL_CHANGE) {
> >> - gpio_set_value(gpiomtd->plat.gpio_nce, !(ctrl & NAND_NCE));
> >> + if (gpio_is_valid(gpiomtd->plat.gpio_nce))
> >> + gpio_set_value(gpiomtd->plat.gpio_nce,
> >> + !(ctrl & NAND_NCE));
> >> gpio_set_value(gpiomtd->plat.gpio_cle, !!(ctrl & NAND_CLE));
> >> gpio_set_value(gpiomtd->plat.gpio_ale, !!(ctrl & NAND_ALE));
> >> gpio_nand_dosync(gpiomtd);
> >> @@ -201,7 +203,8 @@ static int gpio_nand_remove(struct platform_device *pdev)
> >>
> >> if (gpio_is_valid(gpiomtd->plat.gpio_nwp))
> >> gpio_set_value(gpiomtd->plat.gpio_nwp, 0);
> >> - gpio_set_value(gpiomtd->plat.gpio_nce, 1);
> >> + if (gpio_is_valid(gpiomtd->plat.gpio_nce))
> >> + gpio_set_value(gpiomtd->plat.gpio_nce, 1);
> >>
> >> return 0;
> >> }
> >> @@ -239,10 +242,13 @@ static int gpio_nand_probe(struct platform_device *pdev)
> >> if (ret)
> >> return ret;
> >>
> >> - ret = devm_gpio_request(&pdev->dev, gpiomtd->plat.gpio_nce, "NAND NCE");
> >> - if (ret)
> >> - return ret;
> >> - gpio_direction_output(gpiomtd->plat.gpio_nce, 1);
> >> + if (gpio_is_valid(gpiomtd->plat.gpio_nce)) {
> >> + ret = devm_gpio_request(&pdev->dev, gpiomtd->plat.gpio_nce,
> >> + "NAND NCE");
> >> + if (ret)
> >> + return ret;
> >> + gpio_direction_output(gpiomtd->plat.gpio_nce, 1);
> >> + }
> >>
> >> if (gpio_is_valid(gpiomtd->plat.gpio_nwp)) {
> >> ret = devm_gpio_request(&pdev->dev, gpiomtd->plat.gpio_nwp,
next prev parent reply other threads:[~2017-02-13 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 14:01 [PATCH] mtd: nand: gpio: make nCE GPIO optional Christophe Leroy
2017-02-10 15:12 ` Marek Vasut
2017-02-13 10:30 ` Boris Brezillon
2017-02-13 12:58 ` Christophe LEROY
2017-02-13 13:22 ` Boris Brezillon [this message]
2017-03-16 9:35 ` Boris Brezillon
2017-05-01 21:46 ` Brian Norris
2017-05-02 5:47 ` Christophe LEROY
2017-05-02 9:03 ` Boris Brezillon
2017-05-02 16:15 ` Brian Norris
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=20170213142250.7a10768a@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=christophe.leroy@c-s.fr \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.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