From: Linus Walleij <linus.walleij@linaro.org>
To: christophe.kerello@st.com
Cc: "Boris Brezillon" <boris.brezillon@bootlin.com>,
"Miquèl Raynal" <miquel.raynal@bootlin.com>,
"Richard Weinberger" <richard@nod.at>,
"David Woodhouse" <dwmw2@infradead.org>,
"Brian Norris" <computersforpeace@gmail.com>,
"Mark Vasut" <marek.vasut@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
linux-mtd@lists.infradead.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [ v3 2/3] mtd: rawnand: stm32_fmc2: add STM32 FMC2 NAND flash controller driver
Date: Thu, 13 Dec 2018 11:45:35 +0100 [thread overview]
Message-ID: <CACRpkdbiX=9tDnE+tR7Jj-QEY_=_MvS9v8Jg8X7MzQcX7aPp-Q@mail.gmail.com> (raw)
In-Reply-To: <7c295246-8756-9363-a891-856ddf7af92b@st.com>
On Fri, Dec 7, 2018 at 5:53 PM Christophe Kerello
<christophe.kerello@st.com> wrote:
> On 12/7/18 10:06 AM, Linus Walleij wrote:
> Based on FMC2 datasheet,
> The FMC2 controller includes 2 memory controllers:
> - the NOR/PSRAM memory controller
> - the NAND memory controller
>
> The NOR/PSRAM controller mapping is starting at 0.
> The NAND controller mapping is starting at 0x80.
>
> We have only planned to develop a driver for the NAND memory controller.
> There is currently no customer request to develop the NOR/PSRAM memory
> controller.
OK I get it, so there is no FSMC (v1), but a NOR controller, thanks!
If people need to access the NOR controller I think they can just patch
your driver to handle both or have a second driver on the side
(I suspect the pins are anyways set up such that you can just
use either NOR or NAND.)
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-12-13 10:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 16:41 [ v3 0/3] mtd: rawnand: add STM32 FMC2 NAND flash controller driver Christophe Kerello
2018-11-29 16:41 ` [ v3 1/3] dt-bindings: mtd: stm32_fmc2: add STM32 FMC2 NAND controller documentation Christophe Kerello
2018-12-07 23:42 ` Rob Herring
2018-11-29 16:41 ` [ v3 2/3] mtd: rawnand: stm32_fmc2: add STM32 FMC2 NAND flash controller driver Christophe Kerello
2018-12-07 9:06 ` Linus Walleij
2018-12-07 10:21 ` [Linux-stm32] " Benjamin GAIGNARD
2018-12-07 12:47 ` Linus Walleij
2018-12-07 16:53 ` Christophe Kerello
2018-12-13 10:45 ` Linus Walleij [this message]
2018-12-07 10:18 ` Miquel Raynal
2018-12-07 10:53 ` Christophe Kerello
2018-11-29 16:41 ` [ v3 3/3] mtd: rawnand: stm32_fmc2: add manual mode Christophe Kerello
2018-12-07 9:16 ` Linus Walleij
2018-12-07 10:56 ` Christophe Kerello
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='CACRpkdbiX=9tDnE+tR7Jj-QEY_=_MvS9v8Jg8X7MzQcX7aPp-Q@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=boris.brezillon@bootlin.com \
--cc=christophe.kerello@st.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marek.vasut@gmail.com \
--cc=mark.rutland@arm.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh+dt@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).