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: <20200217070429.GB7973@dragon>
Date:   Mon, 17 Feb 2020 15:04:30 +0800
From:   Shawn Guo <shawnguo@...nel.org>
To:     Aisheng Dong <aisheng.dong@....com>,
        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?

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?

Shawn