[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM0PR04MB42111BF00621C1949E1FBA9080150@AM0PR04MB4211.eurprd04.prod.outlook.com>
Date: Fri, 14 Feb 2020 05:50:48 +0000
From: Aisheng Dong <aisheng.dong@....com>
To: Oliver Graute <oliver.graute@...il.com>,
Shawn Guo <shawnguo@...nel.org>
CC: "festevam@...il.com" <festevam@...il.com>,
Anson Huang <anson.huang@....com>,
Stephen Boyd <sboyd@...nel.org>,
Leonard Crestez <leonard.crestez@....com>,
Peng Fan <peng.fan@....com>,
"linux-clk@...r.kernel.org" <linux-clk@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: clk: imx: clock driver for imx8qm?
> From: Oliver Graute <oliver.graute@...il.com>
> Sent: Friday, February 14, 2020 1:42 AM
>
> On 13/02/20, Aisheng Dong wrote:
> > Hi Oliver,
> >
> > >
> > > is someone working on clock driver for imx8qm? I miss at least a
> > > clk-imx8qm.c in the drivers/imx/clk/ directory. I saw that you are
> > > working in this area and perhaps you can give me some insights what is
> needed here.
> > >
> >
> > MX8QM/QXP are using the same clock driver clk-imx8qxp.c
>
> ok thx, for that clarification.
>
> >
> > [PATCH RESEND V5 00/11] clk: imx8: add new clock binding for better pm
> > The review of that patch series is pending for a couple of months.
>
> yes that is what I currently use. So further imx8qm development can happen if
> this is integrated?
Yes, it blocks the most following MX8QXP/QM work.
Let me loop in Shawn to see if any suggestions.
Shawn,
Any ideas?
Regards
Aisheng
>
> Best regards,
>
> Oliver
Powered by blists - more mailing lists