[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1439176963-8969-1-git-send-email-zhengsq@rock-chips.com>
Date: Mon, 10 Aug 2015 11:22:40 +0800
From: Shunqian Zheng <zhengsq@...k-chips.com>
To: srinivas.kandagatla@...aro.org, maxime.ripard@...e-electrons.com,
heiko@...ech.de, linux-kernel@...r.kernel.org,
caesar.wang@...k-chips.com
Cc: dianders@...omium.org, linux-rockchip@...ts.infradead.org,
xjq@...k-chips.com, ZhengShunQian <zhengsq@...k-chips.com>
Subject: [PATCH 0/3] Add eFuse driver of Rockchip SoC
From: ZhengShunQian <zhengsq@...k-chips.com>
Base on nvmem framework, this three patches
implement the eFuse driver of Rockchip SoC.
The data from eFuse contains CPU leakage, chip code and version etc.
The flow of reading data from eFuse is quite simple,
config the CTRL register, write data address to CTRL
register, then data is available in DOUT register.
Although always enable eFuse clock seems awkward,
I can't find a better method to enable clock before
read/write in the nvmem framework.
Appreciate for any suggestions.
ZhengShunQian (3):
nvmem: fix the out-of-range leak in read/write()
nvmem: rockchip-efuse: implement eFuse driver
clk: rockchip: do not gate the efuse256 clock
.../devicetree/bindings/nvmem/rockchip-efuse.txt | 36 +++++
arch/arm/boot/dts/rk3288.dtsi | 13 ++
drivers/clk/rockchip/clk-rk3288.c | 2 +-
drivers/nvmem/Kconfig | 10 ++
drivers/nvmem/Makefile | 2 +
drivers/nvmem/core.c | 4 +-
drivers/nvmem/rockchip-efuse.c | 155 +++++++++++++++++++++
include/dt-bindings/clock/rk3288-cru.h | 1 +
8 files changed, 220 insertions(+), 3 deletions(-)
create mode 100644 Documentation/devicetree/bindings/nvmem/rockchip-efuse.txt
create mode 100644 drivers/nvmem/rockchip-efuse.c
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists