From: Aisheng Dong <aisheng.dong@nxp.com>
To: Stephen Boyd <sboyd@kernel.org>, Shawn Guo <shawnguo@kernel.org>
Cc: "linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: RE: [PATCH RESEND V5 00/11] clk: imx8: add new clock binding for better pm support
Date: Tue, 21 Jan 2020 05:00:56 +0000 [thread overview]
Message-ID: <AM0PR04MB42115D5A9D431D6EEA0C8D2D800D0@AM0PR04MB4211.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <AM0PR04MB42111A436D719D321ADB479380200@AM0PR04MB4211.eurprd04.prod.outlook.com>
Gently ping..
> From: Aisheng Dong <aisheng.dong@nxp.com>
> Sent: Thursday, January 2, 2020 4:26 PM
>
> Hi Stephen,
>
> Could you take a look at this?
>
> Regards
> Aisheng
>
> > From: Shawn Guo <shawnguo@kernel.org>
> > Sent: Wednesday, December 11, 2019 4:05 PM
> >
> > On Sun, Nov 17, 2019 at 08:25:08PM +0800, Dong Aisheng wrote:
> > > This is a follow up of this patch series.
> > > [V2,0/2] clk: imx: scu: add parsing clocks from device tree support
> > >
> > > This patch series is a preparation for the MX8 Architecture improvement.
> > > As for IMX SCU based platforms like MX8QM and MX8QXP, they are
> > > comprised of a couple of SS(Subsystems) while most of them within
> > > the same SS can be shared. e.g. Clocks, Devices and etc.
> > >
> > > However, current clock binding is using SW IDs for device tree to
> > > use which can cause troubles in writing the common <soc>-ss-xx.dtsi
> > > file for different SoCs.
> > >
> > > This patch series aims to introduce a new binding which is more
> > > close to hardware and platform independent and can makes us write a
> > > more general drivers for different SCU based SoCs.
> > >
> > > Another important thing is that on MX8, each Clock resource is
> > > associated with a power domain. So we have to attach that clock
> > > device to the power domain in order to make it work properly.
> > > Further more, the clock state will be lost when its power domain is
> > > completely off during suspend/resume, so we also introduce the clock
> > > state save&restore
> > mechanism.
> > >
> > > ChangeLog:
> > > v4->v5:
> > > * Address all comments from Stephen
> >
> > Hi Stephen,
> >
> > Are you fine with this version?
> >
> > Shawn
next prev parent reply other threads:[~2020-01-21 5:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 12:25 [PATCH RESEND V5 00/11] clk: imx8: add new clock binding for better pm support Dong Aisheng
2019-11-17 12:25 ` [PATCH RESEND v5 01/11] dt-bindings: firmware: imx-scu: new binding to parse clocks from device tree Dong Aisheng
2019-11-17 12:25 ` [PATCH RESEND v5 02/11] dt-bindings: clock: imx-lpcg: add support " Dong Aisheng
2019-11-17 12:25 ` [PATCH RESEND v5 03/11] clk: imx: scu: add two cells binding support Dong Aisheng
2019-11-17 12:25 ` [PATCH RESEND v5 04/11] clk: imx: scu: bypass cpu power domains Dong Aisheng
2019-11-17 12:25 ` [PATCH RESEND v5 05/11] clk: imx: scu: allow scu clk to take device pointer Dong Aisheng
2019-11-17 12:25 ` [PATCH RESEND v5 06/11] clk: imx: scu: add runtime pm support Dong Aisheng
2019-11-17 12:25 ` [PATCH RESEND v5 07/11] clk: imx: scu: add suspend/resume support Dong Aisheng
2019-11-17 12:25 ` [PATCH RESEND v5 08/11] clk: imx: imx8qxp-lpcg: add parsing clocks from device tree Dong Aisheng
2019-11-17 12:25 ` [PATCH RESEND v5 09/11] clk: imx: lpcg: allow lpcg clk to take device pointer Dong Aisheng
2019-11-17 12:25 ` [PATCH RESEND v5 10/11] clk: imx: clk-imx8qxp-lpcg: add runtime pm support Dong Aisheng
2019-11-17 12:25 ` [PATCH RESEND v5 11/11] clk: imx: lpcg: add suspend/resume support Dong Aisheng
2019-12-11 8:05 ` [PATCH RESEND V5 00/11] clk: imx8: add new clock binding for better pm support Shawn Guo
2020-01-02 8:25 ` Aisheng Dong
2020-01-21 5:00 ` Aisheng Dong [this message]
2020-02-07 11:06 ` Oliver Graute
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=AM0PR04MB42115D5A9D431D6EEA0C8D2D800D0@AM0PR04MB4211.eurprd04.prod.outlook.com \
--to=aisheng.dong@nxp.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=mturquette@baylibre.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).