From: "Heiko Stübner" <heiko@sntech.de>
To: Shunqian Zheng <zhengsq@rock-chips.com>
Cc: gregkh@linuxfoundation.org, srinivas.kandagatla@linaro.org,
maxime.ripard@free-electrons.com, caesar.wang@rock-chips.com,
mturquette@baylibre.com, sboyd@codeaurora.org,
linux-clk@vger.kernel.org, dianders@chromium.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
xjq@rock-chips.com
Subject: Re: [PATCH v2 0/5] Add eFuse driver of Rockchip SoC
Date: Sat, 12 Dec 2015 20:21:55 +0100 [thread overview]
Message-ID: <25029139.jfQHqpcHTE@diego> (raw)
In-Reply-To: <1439288024-13359-1-git-send-email-zhengsq@rock-chips.com>
Am Dienstag, 11. August 2015, 18:13:39 schrieb Shunqian Zheng:
> 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.
I've now applied both the clock-ids addition as well as the dts node for 4.5
after seeing that the nvmem driver did actually make it into the kernel.
I've taken the liberty to
- split the clock-id patch (into header addition and clock-tree reference)
- already add the efuse_1024 clock id, if someone wants to use that later
Heiko
prev parent reply other threads:[~2015-12-12 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 10:13 [PATCH v2 0/5] Add eFuse driver of Rockchip SoC Shunqian Zheng
2015-08-11 10:13 ` [PATCH v2 1/5] clk: rockchip: rk3288: Add the clock id of eFuse Shunqian Zheng
2015-08-12 1:31 ` Stephen Boyd
2015-08-11 10:13 ` [PATCH v2 2/5] nvmem: fix the out-of-range leak in read/write() Shunqian Zheng
2015-08-11 10:13 ` [PATCH v2 3/5] nvmem: rockchip-efuse: implement efuse driver Shunqian Zheng
2015-08-11 10:13 ` [PATCH v2 4/5] Documentation: rockchip-efuse: describe the usage of eFuse Shunqian Zheng
2015-08-11 10:13 ` [PATCH v2 5/5] ARM: dts: rockchip: add eFuse config of rk3288 SoC Shunqian Zheng
2015-12-12 19:21 ` Heiko Stübner [this message]
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=25029139.jfQHqpcHTE@diego \
--to=heiko@sntech.de \
--cc=caesar.wang@rock-chips.com \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maxime.ripard@free-electrons.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=xjq@rock-chips.com \
--cc=zhengsq@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox