Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 17 Feb 2020 15:04:30 +0800
From:   Shawn Guo <shawnguo@kernel.org>
To:     Aisheng Dong <aisheng.dong@nxp.com>,
        Stephen Boyd <sboyd@kernel.org>
Cc:     Oliver Graute <oliver.graute@gmail.com>,
        "festevam@gmail.com" <festevam@gmail.com>,
        Anson Huang <anson.huang@nxp.com>,
        Leonard Crestez <leonard.crestez@nxp.com>,
        Peng Fan <peng.fan@nxp.com>,
        "linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: clk: imx: clock driver for imx8qm?
Message-ID: <20200217070429.GB7973@dragon>
References: <20200213153151.GB6975@optiplex>
 <AM0PR04MB4211AC5AB9F6A055F36040A2801A0@AM0PR04MB4211.eurprd04.prod.outlook.com>
 <20200213174225.GA11566@ripley>
 <AM0PR04MB42111BF00621C1949E1FBA9080150@AM0PR04MB4211.eurprd04.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AM0PR04MB42111BF00621C1949E1FBA9080150@AM0PR04MB4211.eurprd04.prod.outlook.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, Feb 14, 2020 at 05:50:48AM +0000, Aisheng Dong wrote:
> > From: Oliver Graute <oliver.graute@gmail.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