From: Punnaiah Choudary Kalluri <punnaiah.choudary.kalluri@xilinx.com>
To: <robh+dt@kernel.org>, <pawel.moll@arm.com>,
<mark.rutland@arm.com>, <ijc+devicetree@hellion.org.uk>,
<galak@codeaurora.org>, <rob@landley.net>,
<michal.simek@xilinx.com>, <grant.likely@linaro.org>,
<gregkh@linuxfoundation.org>, <jason@lakedaemon.net>,
<ezequiel.garcia@free-electrons.com>, <arnd@arndb.de>,
<dwmw2@infradead.org>, <computersforpeace@gmail.com>,
<artem.bityutskiy@linux.intel.com>, <pekon@ti.com>,
<jussi.kivilinna@iki.fi>, <acourbot@nvidia.com>,
<ivan.khoronzhuk@ti.com>, <joern@logfs.org>
Cc: devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
kalluripunnaiahchoudary@gmail.com, kpc528@gmail.com,
Punnaiah Choudary Kalluri <punnaia@xilinx.com>
Subject: [PATCH RFC 0/3] Add arm pl353 smc driver for xilinx zynq soc
Date: Thu, 27 Mar 2014 23:51:04 +0530 [thread overview]
Message-ID: <bb33414a-fa06-4aea-af85-143e6dca95c7@CH1EHSMHS001.ehs.local> (raw)
The following patches add arm pl353 static memory controller driver for
xilinx zynq soc. The arm pl353 smc supports two interfaces i.e nand and
nor/sram memory interfaces. The current implementation supports only a
single SMC instance and nand specific configuration.
xilinx zynq TRM link:
http://www.xilinx.com/support/documentation/user_guides/ug585-Zynq-7000-TRM.pdf
ARM pl353 smc TRM link:
http://infocenter.arm.com/help/topic/com.arm.doc.ddi0380g/
DDI0380G_smc_pl350_series_r2p1_trm.pdf
Punnaiah Choudary Kalluri (3):
Devicetree: Add pl353 smc controller devicetree binding information
memory: pl353: Add driver for arm pl353 static memory controller
nand: pl353: Add driver for arm pl353 smc nand interface
.../bindings/memory-controllers/pl353-smc.txt | 53 +
drivers/memory/Kconfig | 8 +
drivers/memory/Makefile | 1 +
drivers/memory/pl353-smc.c | 560 ++++++++++
drivers/mtd/nand/Kconfig | 8 +
drivers/mtd/nand/Makefile | 1 +
drivers/mtd/nand/pl353_nand.c | 1122 ++++++++++++++++++++
include/linux/memory/pl353-smc.h | 37 +
8 files changed, 1790 insertions(+), 0 deletions(-)
create mode 100644 Documentation/devicetree/bindings/memory-controllers/pl353-smc.txt
create mode 100644 drivers/memory/pl353-smc.c
create mode 100644 drivers/mtd/nand/pl353_nand.c
create mode 100644 include/linux/memory/pl353-smc.h
--
1.7.4
reply other threads:[~2014-03-27 18:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bb33414a-fa06-4aea-af85-143e6dca95c7@CH1EHSMHS001.ehs.local \
--to=punnaiah.choudary.kalluri@xilinx.com \
--cc=acourbot@nvidia.com \
--cc=arnd@arndb.de \
--cc=artem.bityutskiy@linux.intel.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ivan.khoronzhuk@ti.com \
--cc=jason@lakedaemon.net \
--cc=joern@logfs.org \
--cc=jussi.kivilinna@iki.fi \
--cc=kalluripunnaiahchoudary@gmail.com \
--cc=kpc528@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=pawel.moll@arm.com \
--cc=pekon@ti.com \
--cc=punnaia@xilinx.com \
--cc=rob@landley.net \
--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).