[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 3 Mar 2020 06:16:03 +0000
From: Peng Fan <peng.fan@....com>
To: Viresh Kumar <viresh.kumar@...aro.org>
CC: "shawnguo@...nel.org" <shawnguo@...nel.org>,
"s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
"kernel@...gutronix.de" <kernel@...gutronix.de>,
"festevam@...il.com" <festevam@...il.com>,
dl-linux-imx <linux-imx@....com>,
Anson Huang <anson.huang@....com>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: RE: [PATCH 0/3] Convert i.MX6Q cpufreq to use nvmem API
Hi Viresh,
> Subject: Re: [PATCH 0/3] Convert i.MX6Q cpufreq to use nvmem API
>
> On 03-03-20, 10:14, peng.fan@....com wrote:
> > From: Peng Fan <peng.fan@....com>
> >
> > Use nvmem API is better compared with direclty accessing OCOTP registers.
> > nvmem could handle OCOTP clk, defer probe.
> >
> > Patch 1/3 is dts changes to add nvmem related properties Patch 2/3 is
> > a bug fix Patch 3/3 is convert to nvmem API
>
> Should I apply patch 2 and 3 ? And you can take 1/3 via ARM Soc tree as this
> shouldn't break anything.
Please take patch 2 and 3. Without patch 1, it just use legacy method,
not break things.
Thanks,
Peng.
>
> --
> viresh
Powered by blists - more mailing lists