[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Sat, 12 Dec 2015 20:21:55 +0100
From: Heiko Stübner <heiko@...ech.de>
To: Shunqian Zheng <zhengsq@...k-chips.com>
Cc: gregkh@...uxfoundation.org, srinivas.kandagatla@...aro.org,
maxime.ripard@...e-electrons.com, caesar.wang@...k-chips.com,
mturquette@...libre.com, sboyd@...eaurora.org,
linux-clk@...r.kernel.org, dianders@...omium.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
xjq@...k-chips.com
Subject: Re: [PATCH v2 0/5] Add eFuse driver of Rockchip SoC
Am Dienstag, 11. August 2015, 18:13:39 schrieb Shunqian Zheng:
> 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.
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
--
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