From: Stefan Agner <stefan@agner.ch>
To: dwmw2@infradead.org, computersforpeace@gmail.com,
boris.brezillon@free-electrons.com, marek.vasut@gmail.com,
richard@nod.at, cyrille.pitchen@atmel.com
Cc: robh+dt@kernel.org, mark.rutland@arm.com, shawnguo@kernel.org,
kernel@pengutronix.de, han.xu@nxp.com,
fabio.estevam@freescale.com, LW@KARO-electronics.de,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Stefan Agner <stefan@agner.ch>
Subject: [PATCH v2 0/5] mtd: nand: gpmi: add i.MX 7 support
Date: Fri, 21 Apr 2017 18:23:33 -0700 [thread overview]
Message-ID: <20170422012338.4635-1-stefan@agner.ch> (raw)
This patchset adds support for i.MX 7 SoC for the GPMI NAND controller.
There have been similar patchsets already:
https://lkml.org/lkml/2016/2/23/912
However, this patchset does not make use of any of the new features.
The current feature set seems to work fine, I successfully run the MTD
tests on a Colibri iMX7.
--
Stefan
Changes since v1:
- Make clks_count const
- Introduce IS_IMX7D for i.MX 7 SoC's and make it part of GPMI_IS_MX6
Stefan Agner (5):
mtd: nand: gpmi: unify clock handling
mtd: nand: gpmi: add i.MX 7 SoC support
mtd: gpmi: document current clock requirements
ARM: dts: imx7: add GPMI NAND
ARM: dts: imx7-colibri: add NAND support
.../devicetree/bindings/mtd/gpmi-nand.txt | 14 +++++-
arch/arm/boot/dts/imx7-colibri.dtsi | 9 ++++
arch/arm/boot/dts/imx7s.dtsi | 31 ++++++++++++
drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 56 +++++++++++++---------
drivers/mtd/nand/gpmi-nand/gpmi-nand.h | 9 +++-
5 files changed, 93 insertions(+), 26 deletions(-)
--
2.12.2
next reply other threads:[~2017-04-22 1:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 1:23 Stefan Agner [this message]
2017-04-22 1:23 ` [PATCH v2 1/5] mtd: nand: gpmi: unify clock handling Stefan Agner
2017-04-22 1:23 ` [PATCH v2 2/5] mtd: nand: gpmi: add i.MX 7 SoC support Stefan Agner
2017-04-22 1:23 ` [PATCH v2 3/5] mtd: gpmi: document current clock requirements Stefan Agner
[not found] ` <20170422012338.4635-4-stefan-XLVq0VzYD2Y@public.gmane.org>
2017-04-28 17:13 ` Rob Herring
[not found] ` <20170422012338.4635-1-stefan-XLVq0VzYD2Y@public.gmane.org>
2017-04-22 1:23 ` [PATCH v2 4/5] ARM: dts: imx7: add GPMI NAND Stefan Agner
[not found] ` <20170422012338.4635-5-stefan-XLVq0VzYD2Y@public.gmane.org>
2017-05-04 19:13 ` Han Xu
2017-05-04 21:50 ` Stefan Agner
[not found] ` <48b5c543e713f9597b67a39a51ffd521-XLVq0VzYD2Y@public.gmane.org>
2017-05-04 22:59 ` Han Xu
[not found] ` <8f039bb6-9bc3-349a-cfe8-727e4caf41de-3arQi8VN3Tc@public.gmane.org>
2017-05-25 8:22 ` Stefan Agner
2017-04-22 1:23 ` [PATCH v2 5/5] ARM: dts: imx7-colibri: add NAND support Stefan Agner
2017-04-22 11:43 ` [PATCH v2 0/5] mtd: nand: gpmi: add i.MX 7 support Marek Vasut
2017-05-03 13:25 ` Shawn Guo
2017-05-15 19:38 ` Boris Brezillon
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=20170422012338.4635-1-stefan@agner.ch \
--to=stefan@agner.ch \
--cc=LW@KARO-electronics.de \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=fabio.estevam@freescale.com \
--cc=han.xu@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=mark.rutland@arm.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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).