From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] i.MX6 OCOTP NVMEM support
Date: Mon, 24 Aug 2015 10:26:04 +0200 [thread overview]
Message-ID: <1440404764.4444.2.camel@pengutronix.de> (raw)
In-Reply-To: <1438940901-5779-1-git-send-email-p.zabel@pengutronix.de>
Hi Greg,
Am Freitag, den 07.08.2015, 11:48 +0200 schrieb Philipp Zabel:
> Hi,
>
> These patches add support for the i.MX On-Chip OTP (eFuse) Controller found
> in i.MX6Q/D, i.MX6S/DL, i.MX6SL, and i.MX6SX SoCs to the NVMEM framework.
> Greg, could you take them into the char-misc tree together with the NVMEM
> framework?
is anything blocking this?
best regards
Philipp
> Changes since v1:
> - Dropped unneeded clk.h include
> - Fixed MODULE_LICENSE
> - Droped third patch (adding the clock to the device tree node can be done separately)
>
> Philipp Zabel (2):
> nvmem: Add i.MX6 OCOTP device tree binding documentation
> nvmem: imx-ocotp: Add i.MX6 OCOTP driver
>
> .../devicetree/bindings/nvmem/imx-ocotp.txt | 20 +++
> drivers/nvmem/Kconfig | 11 ++
> drivers/nvmem/Makefile | 2 +
> drivers/nvmem/imx-ocotp.c | 154 +++++++++++++++++++++
> 4 files changed, 187 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/imx-ocotp.txt
> create mode 100644 drivers/nvmem/imx-ocotp.c
prev parent reply other threads:[~2015-08-24 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 9:48 [PATCH v2 0/2] i.MX6 OCOTP NVMEM support Philipp Zabel
2015-08-07 9:48 ` [PATCH v2 1/2] nvmem: Add i.MX6 OCOTP device tree binding documentation Philipp Zabel
2015-08-07 9:48 ` [PATCH v2 2/2] nvmem: imx-ocotp: Add i.MX6 OCOTP driver Philipp Zabel
2015-08-24 8:26 ` Philipp Zabel [this message]
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=1440404764.4444.2.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).