From: Aisheng Dong <aisheng.dong@nxp.com>
To: Aisheng Dong <aisheng.dong@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"sboyd@kernel.org" <sboyd@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH RESEND v1 0/4] dt-binding: clk: prepare for imx8qm clock support
Date: Wed, 16 Jan 2019 05:40:01 +0000 [thread overview]
Message-ID: <AM0PR04MB42115D3E98B8B319936AC60E80820@AM0PR04MB4211.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1547207400-28307-1-git-send-email-aisheng.dong@nxp.com>
Ping...
BTW, as the first two patches change the same firmware binding doc fs.scu.txt.
I'm not sure whether it should go to Shawn's tree for the binding part, or Stephen's clock tree.
Shawn & Stephen,
What's your suggestion?
Regards
Dong Aisheng
> From: Aisheng Dong [mailto:aisheng.dong@nxp.com]
> Sent: Friday, January 11, 2019 7:56 PM
>
> After a bit more investigation on IMX8QM, it seemed SCU clock can be used in
> a similar way as IMX8QXP. So update the binding and driver to be a bit generic
> for easily extension of IMX8QM support later.
>
> Dong Aisheng (4):
> dt-bindings: fsl: scu: add fallback compatible string for clock
> dt-bindings: fsl: scu: add imx8qm scu clock support
> clk: imx: scu: add fallback compatible string support
> dt-bindings: imx8-clock: add a53 and a72 clock id
>
> Documentation/devicetree/bindings/arm/freescale/fsl,scu.txt | 7 +++++--
> drivers/clk/imx/clk-imx8qxp.c | 1 +
> include/dt-bindings/clock/imx8-clock.h | 6 ++++--
> 3 files changed, 10 insertions(+), 4 deletions(-)
>
> --
> 2.7.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-16 5:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 11:55 [PATCH RESEND v1 0/4] dt-binding: clk: prepare for imx8qm clock support Aisheng Dong
2019-01-11 11:55 ` [PATCH RESEND v1 1/4] dt-bindings: fsl: scu: add fallback compatible string for clock Aisheng Dong
2019-01-21 23:25 ` Rob Herring
2019-01-22 19:05 ` Stephen Boyd
2019-01-11 11:56 ` [PATCH RESEND v1 2/4] dt-bindings: fsl: scu: add imx8qm scu clock support Aisheng Dong
2019-01-21 23:27 ` Rob Herring
2019-01-22 12:58 ` Aisheng Dong
2019-01-22 19:06 ` Stephen Boyd
2019-01-11 11:56 ` [PATCH RESEND v1 3/4] clk: imx: scu: add fallback compatible string support Aisheng Dong
2019-01-11 11:56 ` [PATCH RESEND v1 4/4] dt-bindings: imx8-clock: add a53 and a72 clock id Aisheng Dong
2019-01-22 0:10 ` Rob Herring
2019-01-22 12:59 ` Aisheng Dong
2019-01-30 16:45 ` Rob Herring
2019-01-16 5:40 ` Aisheng Dong [this message]
2019-01-16 11:02 ` [PATCH RESEND v1 0/4] dt-binding: clk: prepare for imx8qm clock support Shawn Guo
2019-01-22 19:06 ` Stephen Boyd
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=AM0PR04MB42115D3E98B8B319936AC60E80820@AM0PR04MB4211.eurprd04.prod.outlook.com \
--to=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--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=robh+dt@kernel.org \
--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).