[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1439273706-28274-1-git-send-email-zhengsq@rock-chips.com>
Date: Tue, 11 Aug 2015 14:15:01 +0800
From: Shunqian Zheng <zhengsq@...k-chips.com>
To: gregkh@...uxfoundation.org, srinivas.kandagatla@...aro.org,
maxime.ripard@...e-electrons.com, heiko@...ech.de,
caesar.wang@...k-chips.com
Cc: dianders@...omium.org, linux-rockchip@...ts.infradead.org,
linux-kernel@...r.kernel.org, xjq@...k-chips.com,
ZhengShunQian <zhengsq@...k-chips.com>
Subject: [PATCH v1 0/5] Add eFuse driver of Rockchip SoC
From: ZhengShunQian <zhengsq@...k-chips.com>
Base on nvmem framework, this series 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,
configure the CTRL register, write data address to CTRL
register, then data is available in DOUT register.
The changes versus V0:
1. Enable/disable clock when required.
2. Split the drivers patch into three patches.
3. Update the docs of eFuse.
ZhengShunQian (5):
clk: rockchip: rk3288: Add the clock id of eFuse
nvmem: fix the out-of-range leak in read/write()
nvmem: rockchip-efuse: implement efuse driver
Documentation: rockchip-efuse: describe the usage of eFuse
ARM: dts: rockchip: add eFuse config of rk3288 SoC
.../devicetree/bindings/nvmem/rockchip-efuse.txt | 38 ++++
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 | 193 +++++++++++++++++++++
include/dt-bindings/clock/rk3288-cru.h | 1 +
8 files changed, 260 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