[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAK8P3a0hrDs-PXHaCfBx1As0BP8GwSZ+7zPLCMgxXOAhk=4CMQ@mail.gmail.com>
Date: Thu, 2 Jul 2020 09:43:04 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Anson Huang <anson.huang@....com>
Cc: Dong Aisheng <dongas86@...il.com>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Sascha Hauer <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>,
Peng Fan <peng.fan@....com>, Abel Vesa <abel.vesa@....com>,
Aisheng Dong <aisheng.dong@....com>,
Andy Duan <fugang.duan@....com>,
Daniel Baluta <daniel.baluta@....com>,
YueHaibing <yuehaibing@...wei.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-clk <linux-clk@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
dl-linux-imx <linux-imx@....com>
Subject: Re: [PATCH V4 3/5] clk: imx: Support building i.MX common clock
driver as module
On Thu, Jul 2, 2020 at 9:12 AM Anson Huang <anson.huang@....com> wrote:
> >
> > The question is whether the #ifdef check in the header to test for MODULE
> > (only calling it if this particular soc has a built-in clk driver, which is sufficient)
> > or for IS_MODULE(CONFIG_MXC_CLK) (call it if _any_ clk driver is built-in and
> > the function exists, which leaves extra code in the driver but is a more
> > conventional check).
> >
>
> So you prefer to add an empty inline function for imx_register_uart_clocks() with check
> of MODULE build?
Yes, I want the empty inline stub, but either symbol check would work
> Even with this, we still need to add MODULE build check to whole block
> of this earlycon uart clock handler in imx/clk.c.
Correct.
Arnd
Powered by blists - more mailing lists