From: Keiji Hayashibara <hayashibara.keiji@socionext.com>
To: srinivas.kandagatla@linaro.org
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, masami.hiramatsu@linaro.org,
jaswinder.singh@linaro.org, yamada.masahiro@socionext.com,
hayashi.kunihiko@socionext.com, owada.kiyoshi@socionext.com,
Keiji Hayashibara <hayashibara.keiji@socionext.com>
Subject: [PATCH v1 0/3] add UniPhier efuse support
Date: Fri, 1 Sep 2017 08:20:17 +0900 [thread overview]
Message-ID: <1504221620-358-1-git-send-email-hayashibara.keiji@socionext.com> (raw)
This series adds support for eFuse implemented on UniPhier LD20 SoCs.
The eFuse device is under soc-glue and this register implements as read only.
Keiji Hayashibara (3):
dt-bindings: nvmem: add description for UniPhier eFuse
nvmem: uniphier: add UniPhier eFuse driver
arm64: dts: uniphier: add efuse node for LD20
.../devicetree/bindings/nvmem/uniphier-efuse.txt | 45 ++++++++++
arch/arm64/boot/dts/socionext/uniphier-ld20.dtsi | 14 ++++
arch/arm64/configs/defconfig | 1 +
drivers/nvmem/Kconfig | 11 +++
drivers/nvmem/Makefile | 2 +
drivers/nvmem/uniphier-efuse.c | 98 ++++++++++++++++++++++
6 files changed, 171 insertions(+)
create mode 100644 Documentation/devicetree/bindings/nvmem/uniphier-efuse.txt
create mode 100644 drivers/nvmem/uniphier-efuse.c
--
2.7.4
next reply other threads:[~2017-08-31 23:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 23:20 Keiji Hayashibara [this message]
2017-08-31 23:20 ` [PATCH v1 1/3] dt-bindings: nvmem: add description for UniPhier eFuse Keiji Hayashibara
2017-09-04 12:55 ` Masahiro Yamada
2017-09-05 7:04 ` Keiji Hayashibara
2017-09-12 16:15 ` Rob Herring
2017-09-13 2:31 ` Keiji Hayashibara
2017-08-31 23:20 ` [PATCH v1 2/3] nvmem: uniphier: add UniPhier eFuse driver Keiji Hayashibara
2017-09-04 12:58 ` Masahiro Yamada
2017-09-07 0:36 ` Keiji Hayashibara
2017-08-31 23:20 ` [PATCH v1 3/3] arm64: dts: uniphier: add efuse node for LD20 Keiji Hayashibara
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=1504221620-358-1-git-send-email-hayashibara.keiji@socionext.com \
--to=hayashibara.keiji@socionext.com \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu@linaro.org \
--cc=owada.kiyoshi@socionext.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=yamada.masahiro@socionext.com \
/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).