From: wxt@rock-chips.com (Caesar Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] support the efuse for rk3188/rk3066a SoCs and cleanup driver on nvmem.
Date: Wed, 11 Nov 2015 15:34:27 +0800 [thread overview]
Message-ID: <1447227272-1728-1-git-send-email-wxt@rock-chips.com> (raw)
This patchset to support reading the efuse info for more SoCs.
(Note: support 32 bits SoCs).
Meanwhile, cleanup sunxi/rockchip drivers for more readability.
You can easy to test for following:
cd /sys/bus/nvmem/devices/rockchip-efuse0
localhost rockchip-efuse0 # busybox hexdump -C nvmem
Caesar Wang (4):
nvmem: sunxi: trivial: fix code style
nvmem: rockchip: trivial: Make the driver more readability
ARM: dts: rockchip: add eFuse node for rk3066a SoCs
ARM: dts: rockchip: add eFuse node for rk3188 SoCs
arch/arm/boot/dts/rk3066a.dtsi | 13 ++++++
arch/arm/boot/dts/rk3188.dtsi | 13 ++++++
drivers/nvmem/rockchip-efuse.c | 90 ++++++++++++++++++++----------------------
drivers/nvmem/sunxi_sid.c | 9 ++---
4 files changed, 71 insertions(+), 54 deletions(-)
--
1.9.1
next reply other threads:[~2015-11-11 7:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 7:34 Caesar Wang [this message]
2015-11-11 7:34 ` [PATCH 1/4] nvmem: sunxi: trivial: fix code style Caesar Wang
2015-11-11 7:34 ` [PATCH 2/4] nvmem: rockchip: trivial: Make the driver more readability Caesar Wang
2015-11-11 7:34 ` [PATCH 3/4] ARM: dts: rockchip: add eFuse node for rk3066a SoCs Caesar Wang
2015-12-14 9:57 ` Srinivas Kandagatla
2015-12-14 13:06 ` Heiko Stübner
2015-12-14 13:12 ` Heiko Stübner
2015-11-11 7:34 ` [PATCH 4/4] ARM: dts: rockchip: add eFuse node for rk3188 SoCs Caesar Wang
2015-12-02 2:44 ` [PATCH 0/4] support the efuse for rk3188/rk3066a SoCs and cleanup driver on nvmem Caesar Wang
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=1447227272-1728-1-git-send-email-wxt@rock-chips.com \
--to=wxt@rock-chips.com \
--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).