[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5DvKi4nXfoSBWbe6qedoWO7RiSP5CvJEkBAVUioyVBN=Q@mail.gmail.com>
Date: Tue, 2 Jan 2018 13:13:29 -0200
From: Fabio Estevam <festevam@...il.com>
To: Anson Huang <anson.huang@....com>
Cc: "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Mark Rutland <mark.rutland@....com>,
"A.s. Dong" <aisheng.dong@....com>, Jacky Bai <ping.bai@....com>,
viresh kumar <viresh.kumar@...aro.org>,
"rjw@...ysocki.net" <rjw@...ysocki.net>,
Russell King - ARM Linux <linux@...linux.org.uk>,
Rob Herring <robh+dt@...nel.org>,
Sascha Hauer <kernel@...gutronix.de>,
Fabio Estevam <fabio.estevam@....com>,
Shawn Guo <shawnguo@...nel.org>
Subject: Re: [PATCH 2/2] cpufreq: imx6q: add 696MHz operating point for i.mx6ul
Hi Anson,
On Tue, Jan 2, 2018 at 1:05 PM, Anson Huang <anson.huang@....com> wrote:
> This change is to support 696MHz operating point, both the speed grading
> check and pll rate change are necessary for 696MHz support, do you think
> they should be in different patch?
I thought this could also change the behaviour for mx6q/dl/qp.
Are the others SoCs safe with this change?
Powered by blists - more mailing lists