All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shunqian Zheng <zhengsq@rock-chips.com>
To: gregkh@linuxfoundation.org, srinivas.kandagatla@linaro.org,
	maxime.ripard@free-electrons.com, heiko@sntech.de,
	caesar.wang@rock-chips.com
Cc: dianders@chromium.org, linux-rockchip@lists.infradead.org,
	linux-kernel@vger.kernel.org, xjq@rock-chips.com,
	ZhengShunQian <zhengsq@rock-chips.com>
Subject: [PATCH v1 0/5] Add eFuse driver of Rockchip SoC
Date: Tue, 11 Aug 2015 14:15:01 +0800	[thread overview]
Message-ID: <1439273706-28274-1-git-send-email-zhengsq@rock-chips.com> (raw)

From: ZhengShunQian <zhengsq@rock-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


             reply	other threads:[~2015-08-11  6:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-11  6:15 Shunqian Zheng [this message]
2015-08-11  6:15 ` [PATCH v1 1/5] clk: rockchip: rk3288: Add the clock id of eFuse Shunqian Zheng
2015-08-11  6:15   ` Shunqian Zheng
2015-08-11  7:16   ` Heiko Stübner
2015-08-11  7:22     ` Heiko Stübner
2015-08-11  7:43       ` Shunqian Zheng
2015-08-11  7:43         ` Shunqian Zheng
2015-08-11  7:23     ` Shunqian Zheng
2015-08-11  6:15 ` [PATCH v1 2/5] nvmem: fix the out-of-range leak in read/write() Shunqian Zheng
2015-08-11  6:15 ` [PATCH v1 3/5] nvmem: rockchip-efuse: implement efuse driver Shunqian Zheng
2015-08-11  6:15   ` Shunqian Zheng
2015-08-11  8:13   ` Srinivas Kandagatla
2015-08-11  8:13     ` Srinivas Kandagatla
2015-08-11  6:15 ` [PATCH v1 4/5] Documentation: rockchip-efuse: describe the usage of eFuse Shunqian Zheng
2015-08-11  6:15   ` Shunqian Zheng
2015-08-11  6:15 ` [PATCH v1 5/5] ARM: dts: rockchip: add eFuse config of rk3288 SoC Shunqian Zheng

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=1439273706-28274-1-git-send-email-zhengsq@rock-chips.com \
    --to=zhengsq@rock-chips.com \
    --cc=caesar.wang@rock-chips.com \
    --cc=dianders@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko@sntech.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=xjq@rock-chips.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.