From: Jianqun Xu <jay.xu@rock-chips.com>
To: heiko@sntech.de, linux@arm.linux.org.uk, grant.likely@linaro.org,
robh+dt@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Jianqun Xu <jay.xu@rock-chips.com>
Subject: [PATCH 0/2] rockchip: efuse: add driver to support rk3288 efuse
Date: Mon, 1 Dec 2014 15:34:39 +0800 [thread overview]
Message-ID: <1417419281-9243-1-git-send-email-jay.xu@rock-chips.com> (raw)
In RK3288, there are two eFuse. One is organized as 32bits by 8 one-time
programmable electrical fuses with random access interface, and the other
is organized as 32bits by 32 one-time programmable electrical fuses.
Jianqun Xu (2):
rockchip: efuse: add documentation for rk3288 efuse driver
rockchip: efuse: add efuse driver for rk3288 efuse
.../bindings/fuse/rockchip,rk3288-efuse.txt | 14 ++
arch/arm/mach-rockchip/efuse.c | 165 +++++++++++++++++++++
arch/arm/mach-rockchip/efuse.h | 15 ++
3 files changed, 194 insertions(+)
create mode 100644 Documentation/devicetree/bindings/fuse/rockchip,rk3288-efuse.txt
create mode 100644 arch/arm/mach-rockchip/efuse.c
create mode 100644 arch/arm/mach-rockchip/efuse.h
--
1.9.1
next reply other threads:[~2014-12-01 7:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 7:34 Jianqun Xu [this message]
2014-12-01 7:34 ` [PATCH 1/2] rockchip: efuse: add documentation for rk3288 efuse driver Jianqun Xu
2014-12-01 7:34 ` [PATCH 2/2] rockchip: efuse: add efuse driver for rk3288 efuse Jianqun Xu
2014-12-01 14:10 ` Heiko Stübner
2014-12-02 15:04 ` Jianqun
[not found] ` <547DD519.4080505-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2015-02-25 23:35 ` Heiko Stübner
2014-12-01 21:01 ` Stefan Wahren
2014-12-01 20:26 ` [PATCH 0/2] rockchip: efuse: add driver to support " Stefan Wahren
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=1417419281-9243-1-git-send-email-jay.xu@rock-chips.com \
--to=jay.xu@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=robh+dt@kernel.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).