From: Aisheng Dong <aisheng.dong@nxp.com>
To: Oliver Graute <oliver.graute@gmail.com>, Shawn Guo <shawnguo@kernel.org>
Cc: "festevam@gmail.com" <festevam@gmail.com>,
Anson Huang <anson.huang@nxp.com>,
Stephen Boyd <sboyd@kernel.org>,
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: Fri, 14 Feb 2020 05:50:48 +0000 [thread overview]
Message-ID: <AM0PR04MB42111BF00621C1949E1FBA9080150@AM0PR04MB4211.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200213174225.GA11566@ripley>
> 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?
Regards
Aisheng
>
> Best regards,
>
> Oliver
next prev parent reply other threads:[~2020-02-14 5:50 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 [this message]
2020-02-17 7:04 ` Shawn Guo
2020-02-17 7:31 ` Aisheng Dong
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=AM0PR04MB42111BF00621C1949E1FBA9080150@AM0PR04MB4211.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.