All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aisheng Dong <aisheng.dong@nxp.com>
To: Shawn Guo <shawnguo@kernel.org>, 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?
Date: Mon, 17 Feb 2020 07:31:18 +0000	[thread overview]
Message-ID: <VI1PR04MB42220B24B1C46756A4B9E7B180160@VI1PR04MB4222.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200217070429.GB7973@dragon>

> From: Shawn Guo <shawnguo@kernel.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@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?
> 

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

  reply	other threads:[~2020-02-17  7:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 15:31 clk: imx: clock driver for imx8qm? Oliver Graute
2020-02-13 16:18 ` Aisheng Dong
2020-02-13 17:42   ` Oliver Graute
2020-02-14  5:50     ` Aisheng Dong
2020-02-17  7:04       ` Shawn Guo
2020-02-17  7:31         ` Aisheng Dong [this message]
2020-02-26 12:29           ` Fabio Estevam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=VI1PR04MB42220B24B1C46756A4B9E7B180160@VI1PR04MB4222.eurprd04.prod.outlook.com \
    --to=aisheng.dong@nxp.com \
    --cc=anson.huang@nxp.com \
    --cc=festevam@gmail.com \
    --cc=leonard.crestez@nxp.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver.graute@gmail.com \
    --cc=peng.fan@nxp.com \
    --cc=sboyd@kernel.org \
    --cc=shawnguo@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.