From: Anson Huang <anson.huang@nxp.com>
To: Aisheng Dong <aisheng.dong@nxp.com>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"sboyd@kernel.org" <sboyd@kernel.org>,
"oleksandr.suvorov@toradex.com" <oleksandr.suvorov@toradex.com>,
Stefan Agner <stefan.agner@toradex.com>,
"arnd@arndb.de" <arnd@arndb.de>, Peng Fan <peng.fan@nxp.com>,
Abel Vesa <abel.vesa@nxp.com>, Andy Duan <fugang.duan@nxp.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
"yuehaibing@huawei.com" <yuehaibing@huawei.com>,
"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>
Cc: dl-linux-imx <linux-imx@nxp.com>
Subject: RE: [PATCH V3 03/10] ARM: imx: Select MXC_CLK for each SoC
Date: Mon, 29 Jun 2020 08:21:46 +0000 [thread overview]
Message-ID: <DB3PR0402MB3916A4DF80C182319F79BB21F56E0@DB3PR0402MB3916.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <AM6PR04MB49662FB8227AEE678F55C116806E0@AM6PR04MB4966.eurprd04.prod.outlook.com>
> Subject: RE: [PATCH V3 03/10] ARM: imx: Select MXC_CLK for each SoC
>
> > From: Anson Huang <Anson.Huang@nxp.com>
> > Sent: Monday, June 29, 2020 1:54 PM
> >
> > i.MX common clock drivers may support module build, so it is NOT
> > selected by default, for ARCH_MXC ARMv7 platforms, need to select it
> > manually in each SoC to make build pass.
> >
> > Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
> > ---
> > Changes since V2:
> > - manually select the MXC_CLK in each SoC instead of selecting it
> > for ARCH_MXC.
>
> Any reason to do this?
Form the discussion, looks like selecting it for each SoC make more sense, as there is
no CLK_IMX* for i.MX6/7, or am I misunderstanding Stephen's comment? Just use
previous implementation of selecting it once in ARCH_MXC?
Anson
next prev parent reply other threads:[~2020-06-29 21:04 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 5:53 [PATCH V3 00/10] Support building i.MX8 SoCs clock driver as module Anson Huang
2020-06-29 5:53 ` [PATCH V3 01/10] clk: composite: Export clk_hw_register_composite() Anson Huang
2020-06-29 5:53 ` [PATCH V3 02/10] init.h: Fix the __setup_param() macro for module build Anson Huang
2020-06-29 11:33 ` Arnd Bergmann
2020-06-29 11:40 ` Anson Huang
2020-06-29 11:58 ` Arnd Bergmann
2020-07-01 5:14 ` Anson Huang
2020-07-01 8:37 ` Arnd Bergmann
2020-07-01 9:27 ` Anson Huang
2020-07-01 9:53 ` Arnd Bergmann
2020-07-01 10:02 ` Anson Huang
2020-07-01 10:13 ` Arnd Bergmann
2020-07-01 10:20 ` Anson Huang
2020-06-29 5:53 ` [PATCH V3 03/10] ARM: imx: Select MXC_CLK for each SoC Anson Huang
2020-06-29 7:27 ` Aisheng Dong
2020-06-29 8:21 ` Anson Huang [this message]
2020-06-29 5:53 ` [PATCH V3 04/10] clk: imx: Support building SCU clock driver as module Anson Huang
2020-06-29 11:37 ` Arnd Bergmann
2020-06-29 12:53 ` Anson Huang
2020-06-29 13:20 ` Arnd Bergmann
2020-06-29 14:52 ` Anson Huang
2020-06-29 15:08 ` Arnd Bergmann
2020-06-29 15:19 ` Anson Huang
2020-06-30 3:55 ` Dong Aisheng
2020-07-01 7:19 ` Anson Huang
2020-07-01 8:46 ` Arnd Bergmann
2020-07-01 9:28 ` Anson Huang
2020-07-01 9:40 ` Anson Huang
2020-07-01 9:54 ` Arnd Bergmann
2020-06-30 3:36 ` Dong Aisheng
2020-06-29 5:53 ` [PATCH V3 05/10] clk: imx: Support building i.MX common " Anson Huang
2020-06-29 5:53 ` [PATCH V3 06/10] clk: imx8mm: Support module build Anson Huang
2020-06-29 5:53 ` [PATCH V3 07/10] clk: imx8mn: " Anson Huang
2020-06-29 5:54 ` [PATCH V3 08/10] clk: imx8mp: " Anson Huang
2020-06-29 5:54 ` [PATCH V3 09/10] clk: imx8mq: " Anson Huang
2020-06-29 5:54 ` [PATCH V3 10/10] clk: imx8qxp: " Anson Huang
2020-06-29 11:40 ` Arnd Bergmann
2020-06-29 11:43 ` Anson Huang
2020-06-29 11:58 ` Arnd Bergmann
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=DB3PR0402MB3916A4DF80C182319F79BB21F56E0@DB3PR0402MB3916.eurprd04.prod.outlook.com \
--to=anson.huang@nxp.com \
--cc=abel.vesa@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=arnd@arndb.de \
--cc=daniel.baluta@nxp.com \
--cc=festevam@gmail.com \
--cc=fugang.duan@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=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mturquette@baylibre.com \
--cc=oleksandr.suvorov@toradex.com \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shawnguo@kernel.org \
--cc=stefan.agner@toradex.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yuehaibing@huawei.com \
/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).