From: Michal Simek <michal.simek@xilinx.com>
To: Michael Walle <michael@walle.cc>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Michal Simek <michal.simek@xilinx.com>,
Russell King <linux@armlinux.org.uk>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 0/3] ARM: add NAND support to Ebang EBAZ4205 board
Date: Mon, 21 Jun 2021 13:00:43 +0200 [thread overview]
Message-ID: <407a3259-6526-4c7d-6bec-bce1fd91ea01@xilinx.com> (raw)
In-Reply-To: <20210616155437.27378-1-michael@walle.cc>
On 6/16/21 5:54 PM, Michael Walle wrote:
> Thanks to Miguel, there is finally a NAND driver for this SoC and we can
> now support the NAND device on the EBAZ4205.
>
> Btw. I'm not sure how often the PL35x NAND controller is used in SoC and
> if it qualifies to add it to the multi_v7 defconfig.
>
> Michael Walle (3):
> ARM: configs: multi_v7: enable PL35x NAND controller
> ARM: dts: zynq: add NAND flash controller node
> ARM: dts: ebaz4205: enable NAND support
>
> arch/arm/boot/dts/zynq-7000.dtsi | 21 +++++++++++++++++++++
> arch/arm/boot/dts/zynq-ebaz4205.dts | 12 ++++++++++++
> arch/arm/configs/multi_v7_defconfig | 1 +
> 3 files changed, 34 insertions(+)
>
Queue.
Thanks,
Michal
prev parent reply other threads:[~2021-06-21 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 15:54 [PATCH 0/3] ARM: add NAND support to Ebang EBAZ4205 board Michael Walle
2021-06-16 15:54 ` [PATCH 1/3] ARM: configs: multi_v7: enable PL35x NAND controller Michael Walle
2021-06-16 15:54 ` [PATCH 2/3] ARM: dts: zynq: add NAND flash controller node Michael Walle
2021-06-16 15:54 ` [PATCH 3/3] ARM: dts: ebaz4205: enable NAND support Michael Walle
2021-06-16 15:58 ` [PATCH 0/3] ARM: add NAND support to Ebang EBAZ4205 board Michael Walle
2021-06-21 11:00 ` Michal Simek [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=407a3259-6526-4c7d-6bec-bce1fd91ea01@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael@walle.cc \
--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).