[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3728837.exfccSJxkh@diego>
Date: Thu, 01 Sep 2016 22:43:32 +0200
From: Heiko Stübner <heiko@...ech.de>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc: Finley Xiao <finley.xiao@...k-chips.com>,
maxime.ripard@...e-electrons.com, robh+dt@...nel.org,
mark.rutland@....com, linux@...linux.org.uk,
catalin.marinas@....com, will.deacon@....com,
dianders@...omium.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, wxt@...k-chips.com,
jay.xu@...k-chips.com, huangtao@...k-chips.com, cl@...k-chips.com,
tony.xie@...k-chips.com
Subject: Re: [PATCH v4 0/3] nvmem: rockchip-efuse: support more rockchip SoCs
Hi srini,
Am Donnerstag, 1. September 2016, 21:02:23 schrieb Srinivas Kandagatla:
> On 29/08/16 10:50, Finley Xiao wrote:
> > As the timing and organization of efuse may be different
> > between rockchip SoCs, so their read function may be different.
> > We add different device tree compatible string for rockchip SoCs
> > to match their own read function.
> >
> > V3->V4:
> > - 3/3 change the type of out_value into u32 and buf into u8, their values
> >
> > come from register, use u32 and u8 may be more readable.
> >
> > Finley Xiao (3):
> > nvmem: rockchip-efuse: update compatible strings for Rockchip efuse
> > ARM: dts: rockchip: update compatible strings for Rockchip efuse
> > nvmem: rockchip-efuse: add rk3399-efuse support
>
> I can take patch 1 and 3, but dts has to go via arm soc tree.
that is really fine, and also what I somehow expect :-) .
So once you picked these two (I guess after Doug's comments are fixed) I'll
pick up the dts patch.
Heiko
Powered by blists - more mailing lists