From: Sascha Hauer <s.hauer@pengutronix.de>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.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>,
Michael Grzeschik <m.grzeschik@pengutronix.de>
Subject: Re: [PATCH 1/2] nvmem: Add driver for the i.MX IIM
Date: Fri, 3 Mar 2017 11:47:13 +0100 [thread overview]
Message-ID: <20170303104713.p25bzw4exjavjlti@pengutronix.de> (raw)
In-Reply-To: <cf3664ee-dd90-a9c4-2b43-883c599aa6bf@linaro.org>
On Fri, Mar 03, 2017 at 09:54:07AM +0000, Srinivas Kandagatla wrote:
>
>
> On 03/03/17 09:50, Srinivas Kandagatla wrote:
> >
> >
> > On 13/02/17 15:31, Sascha Hauer wrote:
> > > From: Michael Grzeschik <m.grzeschik@pengutronix.de>
> > >
> > > This adds a readonly nvmem driver for the i.MX IC Identification Module
> > > (IIM). The IIM is found on the older i.MX SoCs like the i.MX25, i.MX27,
> > > i.MX31, i.MX35, i.MX51 and the i.MX53.
> > >
> > > The IIM can control up to 8 fuse banks with 256 bit each. Not all of the
> > > banks are equipped on the different SoCs. The actual number of fuses
> > > differ from 512 on the i.MX27 and 1152 on the i.MX53.
> > >
> > > The fuses are one time writable, but writing is currently not supported
> > > in the driver.
> > >
> > > Signed-off-by: Michael Grzeschik <m.grzeschik@pengutronix.de>
> > > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> >
> >
> > > ---
> > > drivers/nvmem/Kconfig | 11 ++++
> > > drivers/nvmem/Makefile | 2 +
> > > drivers/nvmem/imx-iim.c | 171
> > > ++++++++++++++++++++++++++++++++++++++++++++++++
> > > 3 files changed, 184 insertions(+)
> > > create mode 100644 drivers/nvmem/imx-iim.c
> >
> > Patch looks good to me, Will pick both bindings and this patch in next
> > cycle for 4.12.
> Opps sent email too quick..
>
> Can you also make sure that ids are null terminated as reported by kbuild
> https://www.spinics.net/lists/arm-kernel/msg562543.html in next version.
>
Thanks for looking. I just sent the v2 series.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2017-03-03 11:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 15:31 [PATCH v1] nvmem: i.MX IIM driver Sascha Hauer
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 [this message]
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
2017-03-03 10:45 [PATCH v2] " Sascha Hauer
2017-03-03 10:45 ` [PATCH 1/2] nvmem: Add driver for the i.MX IIM 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=20170303104713.p25bzw4exjavjlti@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=m.grzeschik@pengutronix.de \
--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).