From: Aisheng Dong <aisheng.dong@nxp.com>
To: Stephen Boyd <sboyd@kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: RE: [PATCH V9 1/7] clk: imx: add configuration option for mmio clks
Date: Wed, 12 Dec 2018 10:27:24 +0000 [thread overview]
Message-ID: <AM0PR04MB4211C8B8DC2D5F2133D30B9F80A70@AM0PR04MB4211.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <AM0PR04MB4211D9C32A4DDCCF266B60C380A70@AM0PR04MB4211.eurprd04.prod.outlook.com>
Hi Stephen,
> > > > > diff --git a/drivers/clk/imx/Makefile b/drivers/clk/imx/Makefile
> > > > > index
> > > > > 5c0b11e..f850424 100644
> > > > > --- a/drivers/clk/imx/Makefile
> > > > > +++ b/drivers/clk/imx/Makefile
> > > > > @@ -1,6 +1,6 @@
> > > > > # SPDX-License-Identifier: GPL-2.0
> > > > >
> > > > > -obj-y += \
> > > > > +obj-$(CONFIG_MXC_CLK) += \
> > > >
> > > > Because this changes to obj-$(CONFIG) we should change the
> > > > drivers/clk/Makefile to have obj-y for this Makefile instead of
> > > > depending on ARCH_MXC.
> > >
> > > We also use ARCH_MXC for ARMv8 SoC clocks.
> >
> > Yes, and? I'm suggesting drivers/clk/Makefile have an obj-y +=
> > drivers/clk/imx/ and then decide to compile or not compile the MXC_CLK
> > "core" bits based on CONFIG_MXC_CLK config option.
>
> Sorry for the missunderstanding before.
> I guess you point is have an ojb-y += drivrs/clk/imx/ Then in
> drivers/clk/imx/Kconfig config MXC_CLK
> def_bool ARCH_MXC && !ARM64
> select MXC_clk bits
> config MXC_CLK_SCU
> def_bool ARCH_MXC && ARM64
> select SCU clock bits
>
> If wrong please let me know.
>
> Will update the patch series and re-send.
> Thanks for the suggestion.
>
I tried and met another problem that MX8MQ (ARM64) is also
using legacy MXC_CLK. (And 3 more MX8M series based chips.)
That means I have to write something like:
config MXC_CLK
bool
def_bool (ARCH_MXC && !ARM64) || (ARCH_MXC && ARM64 && SOC_IMX8MQ)
config MXC_CLK_SCU
bool
def_bool (ARCH_MXC && ARM64 && !SOC_IMX8MQ)
But it can't work as ARM64 supports multiplatforms.
e.g. we have also SOC_IMX8QXP, SOC_IMX8QM, SOC_IMX8DM ...
Do you have a suggestion about this?
Regards
Dong Aisheng
> Regards
> Dong Aisheng
next prev parent reply other threads:[~2018-12-12 10:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 14:39 [PATCH V9 0/7] clk: imx: add imx8qxp clock support Aisheng DONG
2018-12-04 14:39 ` [PATCH V9 1/7] clk: imx: add configuration option for mmio clks Aisheng DONG
2018-12-10 20:55 ` Stephen Boyd
2018-12-11 2:36 ` Aisheng Dong
2018-12-11 19:29 ` Stephen Boyd
2018-12-12 1:09 ` Aisheng Dong
2018-12-12 10:27 ` Aisheng Dong [this message]
2018-12-12 22:23 ` Stephen Boyd
2018-12-13 0:32 ` Aisheng Dong
2018-12-04 14:39 ` [PATCH V9 2/7] clk: imx: add scu clock common part Aisheng DONG
2018-12-10 21:56 ` Stephen Boyd
2018-12-11 3:35 ` Aisheng Dong
2018-12-17 10:27 ` Lothar Waßmann
2018-12-17 10:30 ` Aisheng Dong
2018-12-04 14:39 ` [PATCH V9 3/7] dt-bindings: clock: imx8qxp: add SCU clock IDs Aisheng DONG
2018-12-04 14:39 ` [PATCH V9 4/7] clk: imx: add imx8qxp clk driver Aisheng DONG
2018-12-04 14:39 ` [PATCH V9 5/7] dt-bindings: clock: add imx8qxp lpcg clock binding Aisheng DONG
2018-12-04 14:39 ` [PATCH V9 6/7] clk: imx: add lpcg clock support Aisheng DONG
2018-12-04 14:39 ` [PATCH V9 7/7] clk: imx: add imx8qxp lpcg driver Aisheng DONG
2018-12-10 20:46 ` [PATCH V9 0/7] clk: imx: add imx8qxp clock support Stephen Boyd
2018-12-11 2:04 ` Aisheng Dong
2018-12-11 4:05 ` Aisheng Dong
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=AM0PR04MB4211C8B8DC2D5F2133D30B9F80A70@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).