[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DB7PR04MB44904E50D1B0AC71D999D1C288020@DB7PR04MB4490.eurprd04.prod.outlook.com>
Date: Wed, 5 Feb 2020 03:07:08 +0000
From: Peng Fan <peng.fan@....com>
To: Fabio Estevam <festevam@...il.com>
CC: Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Stephen Boyd <sboyd@...nel.org>, Abel Vesa <abel.vesa@....com>,
Aisheng Dong <aisheng.dong@....com>,
Leonard Crestez <leonard.crestez@....com>,
Sascha Hauer <kernel@...gutronix.de>,
dl-linux-imx <linux-imx@....com>, Jacky Bai <ping.bai@....com>,
Anson Huang <anson.huang@....com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-clk <linux-clk@...r.kernel.org>
Subject: RE: [PATCH 0/7] ARM: imx: imx7ulp: add cpufreq support
> Subject: Re: [PATCH 0/7] ARM: imx: imx7ulp: add cpufreq support
>
> Hi Peng,
>
> On Tue, Feb 4, 2020 at 10:41 AM <peng.fan@....com> wrote:
>
> > I not include the voltage configuration, because imx-rpmsg and pf1550
> > rpmsg driver still not upstreamed.
>
> Any plans for upstreaming imx-rpmsg? I assume this will go into the
> remoteproc framework.
I need check with Richard first, if no plan, I'll take it.
>
> Without this driver, the i.MX7ULP support in mainline is very limited in
> functionality.
To test only clk change, rpmsg driver is not a must. I have tested that,
mhz could correctly show 500MHz and 720Mhz with the diff applied
in cover letter.
I'll try to push forward with rpmsg and regulator part, but both not
go through shawn's tree. This patchset without the dts part, cpufreq
also not take effect, so it is safe to be in if got reviewed. After
the rpmsg/regulator part got in, we could add the dts patch to
switch on cpufreq for i.MX7ULP.
Thanks,
Peng.
>
> Thanks
Powered by blists - more mailing lists