From: Ladislav Michl <ladis@linux-mips.org>
To: linux-mtd@lists.infradead.org
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Boris Brezillon <boris.brezillon@bootlin.com>
Subject: atmel-nand-controller: NAND chip selects?
Date: Mon, 11 Jun 2018 13:04:25 +0200 [thread overview]
Message-ID: <20180611110425.GA4059@lenoch> (raw)
Consider there are more NAND chips connected to the same lines and only nCE
(connected to GPIO line one per each chip) is used to select them.
How is driver supposed to work in such situation?
Common memory region cannot be requested multiple times as well as the
same gpio for R/B cannot be requested. Something as davinci_nand for
memory region? Use 'ranges' property? How should one express in DT gpio
is shared between child nodes?
Any pointers appreciated. Thank you,
ladis
next reply other threads:[~2018-06-11 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 11:04 Ladislav Michl [this message]
2018-06-11 11:21 ` atmel-nand-controller: NAND chip selects? Boris Brezillon
2018-06-11 14:42 ` Ladislav Michl
2018-06-11 18:22 ` Boris Brezillon
2018-06-11 20:30 ` Boris Brezillon
2018-06-11 21:31 ` Ladislav Michl
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=20180611110425.GA4059@lenoch \
--to=ladis@linux-mips.org \
--cc=alexandre.belloni@bootlin.com \
--cc=boris.brezillon@bootlin.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nicolas.ferre@microchip.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;
as well as URLs for NNTP newsgroup(s).