linux-kernel - RE: clk: imx: clock driver for imx8qm?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <VI1PR04MB42220B24B1C46756A4B9E7B180160@VI1PR04MB4222.eurprd04.prod.outlook.com>
Date:   Mon, 17 Feb 2020 07:31:18 +0000
From:   Aisheng Dong <aisheng.dong@....com>
To:     Shawn Guo <shawnguo@...nel.org>, Stephen Boyd <sboyd@...nel.org>
CC:     Oliver Graute <oliver.graute@...il.com>,
        "festevam@...il.com" <festevam@...il.com>,
        Anson Huang <anson.huang@....com>,
        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: Shawn Guo <shawnguo@...nel.org>
> Sent: Monday, February 17, 2020 3:05 PM
> 
> On Fri, Feb 14, 2020 at 05:50:48AM +0000, Aisheng Dong wrote:
> > > 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?
> 
> I guess there are still something Stephen is unhappy about, as we haven't got a
> nod from him.  Do we really addressed all his comments and concerns already?
> 

I remember I addressed all Stephen's comments in the last round of review
which is marked in the V5 resend change log.
https://www.spinics.net/lists/arm-kernel/msg769365.html

But I can double check it.
Should I re-send after a checking or wait for Stephen's feedback?

As this does block a lot of following qm/qxp work for a long time, hopefully we
can get some feedback/guidance from Stephen.

BTW, this patchset is already used in NXP internal 5.4 release although it's missed
5.4 LTS kernel.

Regards
Aisheng

> Shawn