From: Vignesh R <vigneshr@ti.com>
To: Marek Vasut <marek.vasut@gmail.com>,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
Rob Herring <robh+dt@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Vignesh R <vigneshr@ti.com>
Subject: [PATCH 0/7] K2G: Add QSPI support
Date: Tue, 1 Aug 2017 10:24:27 +0530 [thread overview]
Message-ID: <20170801045434.8733-1-vigneshr@ti.com> (raw)
This series adds support for Cadence QSPI for 66AK2G SoC. The first
three patches enhance the cadence-quadspi driver to support loopback
clock and pm_runtime and tweaks for 66AK2G SoC. Remaining patches add
DT nodes and enable the driver in defconfig.
Tested on 66AK2G GP and ICE boards.
Vignesh R (7):
mtd: spi-nor: cadence-quadspi: add a delay in write sequence
mtd: spi-nor: cadence-quadspi: Add support to enable loopback clock
circuit
mtd: spi-nor: cadence-quadspi: Add runtime PM support
ARM: dts: keystone-k2g: Add QSPI DT entry
ARM: dts: keystone-k2g-evm: Add QSPI node
ARM: dts: keystone-k2g-ice: Add QSPI node
ARM: configs: keystone: Enable Cadence QSPI driver
.../devicetree/bindings/mtd/cadence-quadspi.txt | 4 ++
arch/arm/boot/dts/keystone-k2g-evm.dts | 69 ++++++++++++++++++++++
arch/arm/boot/dts/keystone-k2g-ice.dts | 69 ++++++++++++++++++++++
arch/arm/boot/dts/keystone-k2g.dtsi | 15 +++++
arch/arm/configs/keystone_defconfig | 1 +
drivers/mtd/spi-nor/cadence-quadspi.c | 32 +++++++++-
6 files changed, 188 insertions(+), 2 deletions(-)
--
2.13.3
next reply other threads:[~2017-08-01 4:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 4:54 Vignesh R [this message]
2017-08-01 4:54 ` [PATCH 1/7] mtd: spi-nor: cadence-quadspi: add a delay in write sequence Vignesh R
[not found] ` <20170801045434.8733-2-vigneshr-l0cyMroinI0@public.gmane.org>
2017-08-10 0:05 ` Rob Herring
2017-08-10 5:24 ` Vignesh R
2017-08-10 0:08 ` Rob Herring
2017-08-10 5:28 ` Vignesh R
2017-08-01 4:54 ` [PATCH 2/7] mtd: spi-nor: cadence-quadspi: Add support to enable loopback clock circuit Vignesh R
[not found] ` <20170801045434.8733-3-vigneshr-l0cyMroinI0@public.gmane.org>
2017-08-10 0:10 ` Rob Herring
2017-08-10 5:25 ` Vignesh R
[not found] ` <20170801045434.8733-1-vigneshr-l0cyMroinI0@public.gmane.org>
2017-08-01 4:54 ` [PATCH 3/7] mtd: spi-nor: cadence-quadspi: Add runtime PM support Vignesh R
2017-08-01 4:54 ` [PATCH 5/7] ARM: dts: keystone-k2g-evm: Add QSPI node Vignesh R
2017-08-01 4:54 ` [PATCH 4/7] ARM: dts: keystone-k2g: Add QSPI DT entry Vignesh R
2017-08-01 4:54 ` [PATCH 6/7] ARM: dts: keystone-k2g-ice: Add QSPI node Vignesh R
2017-08-01 4:54 ` [PATCH 7/7] ARM: configs: keystone: Enable Cadence QSPI driver Vignesh R
2017-08-01 18:01 ` [PATCH 0/7] K2G: Add QSPI support Santosh Shilimkar
[not found] ` <29c0e8ec-1f9f-cfc9-2d0e-e4d31890b699-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2017-08-02 5:52 ` Vignesh R
2017-08-02 17:19 ` Santosh Shilimkar
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=20170801045434.8733-1-vigneshr@ti.com \
--to=vigneshr@ti.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--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=robh+dt@kernel.org \
--cc=ssantosh@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).