From: Sascha Hauer <s.hauer@pengutronix.de>
To: linux-kernel@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Shawn Guo <shawnguo@kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
kernel@pengutronix.de, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: [PATCH v1] nvmem: i.MX IIM driver
Date: Mon, 13 Feb 2017 16:31:47 +0100 [thread overview]
Message-ID: <20170213153149.11710-1-s.hauer@pengutronix.de> (raw)
This adds a readonly nvmem driver for the i.MX IC Identification Module (IIM)
which is found on the older i.MX SoCs. The IIM is part of the i.MX dts files
for long now, but so far there is no binding document for it, so add one now.
Sascha
----------------------------------------------------------------
Michael Grzeschik (1):
nvmem: Add driver for the i.MX IIM
Sascha Hauer (1):
dt-bindings: nvmem: Add i.MX IIM binding doc
.../devicetree/bindings/nvmem/imx-iim.txt | 22 +++
drivers/nvmem/Kconfig | 11 ++
drivers/nvmem/Makefile | 2 +
drivers/nvmem/imx-iim.c | 171 +++++++++++++++++++++
4 files changed, 206 insertions(+)
create mode 100644 Documentation/devicetree/bindings/nvmem/imx-iim.txt
create mode 100644 drivers/nvmem/imx-iim.c
next reply other threads:[~2017-02-13 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 15:31 Sascha Hauer [this message]
2017-02-13 15:31 ` [PATCH 1/2] nvmem: Add driver for the i.MX IIM Sascha Hauer
2017-02-13 22:33 ` kbuild test robot
2017-02-14 8:00 ` Sascha Hauer
2017-03-03 9:50 ` Srinivas Kandagatla
2017-03-03 9:54 ` Srinivas Kandagatla
2017-03-03 10:47 ` Sascha Hauer
2017-02-13 15:31 ` [PATCH 2/2] dt-bindings: nvmem: Add i.MX IIM binding doc Sascha Hauer
2017-03-03 6:36 ` [PATCH v1] nvmem: i.MX IIM driver Sascha Hauer
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=20170213153149.11710-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=srinivas.kandagatla@linaro.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).