From: Mathieu Malaterre <malat@debian.org>
To: Marcin Nowakowski <marcin.nowakowski@mips.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Zubair.Kakakhel@mips.com, Mathieu Malaterre <malat@debian.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Ralf Baechle <ralf@linux-mips.org>,
PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-mips@linux-mips.org
Subject: [PATCH v2 0/2] Add efuse driver for Ingenic JZ4780 SoC
Date: Thu, 28 Dec 2017 22:29:51 +0100 [thread overview]
Message-ID: <20171228212954.2922-1-malat@debian.org> (raw)
This patchset bring support for read-only access to the JZ4780 efuse as found
on MIPS Creator CI20.
To keep the driver as simple as possible, it was not possible to re-use most of
the nvmem core functionalities. This driver is not compatible with the original
efuse driver as found in the custom linux kernel from upstream (1), in
particular it does not expose to the users neither:
`/sys/devices/platform/*/chip_id` nor `/sys/devices/platform/*/user_id`.
The goal of this driver is to provide access to the MAC address to the dm9000
driver.
(1) https://github.com/ZubairLK/CI20_linux/commit/6efd4ffca7dcfaff0794ab60cd6922ce96c60419
Changes in v2:
Properly handle offset and byte value from the main entry point.
Also add a commit message in patch #2.
Mathieu Malaterre (1):
dts: Probe efuse for CI20
PrasannaKumar Muralidharan (1):
nvmem: add driver for JZ4780 efuse
.../ABI/testing/sysfs-driver-jz4780-efuse | 16 ++
.../bindings/nvmem/ingenic,jz4780-efuse.txt | 17 ++
MAINTAINERS | 5 +
arch/mips/boot/dts/ingenic/jz4780.dtsi | 40 ++-
arch/mips/configs/ci20_defconfig | 2 +
drivers/nvmem/Kconfig | 10 +
drivers/nvmem/Makefile | 2 +
drivers/nvmem/jz4780-efuse.c | 305 +++++++++++++++++++++
8 files changed, 385 insertions(+), 12 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-driver-jz4780-efuse
create mode 100644 Documentation/devicetree/bindings/nvmem/ingenic,jz4780-efuse.txt
create mode 100644 drivers/nvmem/jz4780-efuse.c
--
2.11.0
next reply other threads:[~2017-12-28 21:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 21:29 Mathieu Malaterre [this message]
2017-12-28 21:29 ` [PATCH v2 1/2] nvmem: add driver for JZ4780 efuse Mathieu Malaterre
2017-12-29 12:35 ` Marcin Nowakowski
2018-01-02 12:02 ` Srinivas Kandagatla
2018-01-02 16:17 ` PrasannaKumar Muralidharan
2018-01-03 20:02 ` Rob Herring
2018-01-06 12:43 ` PrasannaKumar Muralidharan
2018-01-11 15:08 ` Rob Herring
2018-01-17 17:31 ` PrasannaKumar Muralidharan
2018-01-18 1:59 ` Rob Herring
2018-01-20 8:11 ` PrasannaKumar Muralidharan
2017-12-28 21:29 ` [PATCH v2 2/2] dts: Probe efuse for CI20 Mathieu Malaterre
2018-01-03 20:04 ` Rob Herring
2018-01-17 20:54 ` James Hogan
2018-01-02 12:01 ` [PATCH v2 0/2] Add efuse driver for Ingenic JZ4780 SoC Srinivas Kandagatla
2018-01-02 16:17 ` PrasannaKumar Muralidharan
2018-01-02 17:58 ` Srinivas Kandagatla
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=20171228212954.2922-1-malat@debian.org \
--to=malat@debian.org \
--cc=Zubair.Kakakhel@mips.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=marcin.nowakowski@mips.com \
--cc=mark.rutland@arm.com \
--cc=prasannatsmkumar@gmail.com \
--cc=ralf@linux-mips.org \
--cc=robh+dt@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).