linux-kernel - RE: [PATCH V2] firmware: imx: Move i.MX SCU soc driver into imx firmware folder

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 25 Jun 2020 12:54:38 +0000
From:   Anson Huang <anson.huang@....com>
To:     Arnd Bergmann <arnd@...db.de>
CC:     Catalin Marinas <catalin.marinas@....com>,
        Will Deacon <will@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
        Sascha Hauer <s.hauer@...gutronix.de>,
        Sascha Hauer <kernel@...gutronix.de>,
        Fabio Estevam <festevam@...il.com>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Leo Li <leoyang.li@....com>, Vinod Koul <vkoul@...nel.org>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Olof Johansson <olof@...om.net>, Peng Fan <peng.fan@....com>,
        Aisheng Dong <aisheng.dong@....com>,
        Daniel Baluta <daniel.baluta@....com>,
        Franck Lenormand <franck.lenormand@....com>,
        Krzysztof Kozlowski <krzk@...nel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        dl-linux-imx <linux-imx@....com>
Subject: RE: [PATCH V2] firmware: imx: Move i.MX SCU soc driver into imx
 firmware folder

Hi, Arnd


> Subject: Re: [PATCH V2] firmware: imx: Move i.MX SCU soc driver into imx
> firmware folder
> 
> On Thu, Jun 25, 2020 at 2:27 AM Anson Huang <Anson.Huang@....com>
> wrote:
> >
> > The i.MX SCU soc driver depends on SCU firmware driver, so it has to
> > use platform driver model for proper defer probe operation, since it
> > has no device binding in DT file, a simple platform device is created
> > together inside the platform driver. To make it more clean, we can
> > just move the entire SCU soc driver into imx firmware folder and
> > initialized by i.MX SCU firmware driver.
> >
> > Signed-off-by: Anson Huang <Anson.Huang@....com>
> 
> Looks good except for one irritating issue:
> 
> > index 17ea361..b76acba 100644
> > --- a/drivers/firmware/imx/Makefile
> > +++ b/drivers/firmware/imx/Makefile
> > @@ -1,4 +1,4 @@
> >  # SPDX-License-Identifier: GPL-2.0
> >  obj-$(CONFIG_IMX_DSP)          += imx-dsp.o
> > -obj-$(CONFIG_IMX_SCU)          += imx-scu.o misc.o imx-scu-irq.o rm.o
> > +obj-$(CONFIG_IMX_SCU)          += imx-scu.o misc.o imx-scu-irq.o rm.o
> imx-scu-soc.o
> >  obj-$(CONFIG_IMX_SCU_PD)       += scu-pd.o
> 
> This makes separate loadable modules out of the driver when
> CONFIG_IMX_SCU=m, including the badly named misc.ko and rm.ko modules
> that might conflict with other modules of the same name (module names are a
> global namespace for modprobe).
> 
> The way to make this a single module from four files is
> 
> obj-$(CONFIG_IMX_SCU)          += imx-scu-mod.o
> imx-scu-mod-y := imx-scu.o misc.o imx-scu-irq.o rm.o imx-scu-soc.o

I haven't considered the support for loadable module of i.MX SCU firmware yet,
plan to have another patch to do it, so do you think it is good to add the loadable
module support together in this patch?

> 
> > +EXPORT_SYMBOL(imx_scu_soc_init);
> 
> Consequently, there should not be an EXPORT_SYMBOL here.

Will remove it.

Thanks,
Anson