[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YZLWOFGFs4g6gh5l@rocinante>
Date: Mon, 15 Nov 2021 22:50:48 +0100
From: Krzysztof WilczyĆski <kw@...ux.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: Sergio Paracuellos <sergio.paracuellos@...il.com>,
linux-pci <linux-pci@...r.kernel.org>,
"open list:BROADCOM NVRAM DRIVER" <linux-mips@...r.kernel.org>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
John Crispin <john@...ozen.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Yanteng Si <siyanteng@...ngson.cn>
Subject: Re: [PATCH 4/5] PCI: mt7621: Add missing 'MODULE_LICENSE()'
definition
Hi Arnd,
[...]
> > > builtin_platform_driver(mt7621_pci_driver);
> > > +
> > > +MODULE_LICENSE("GPL v2");
> >
> > A question here about the builtin_platform_driver() use in this driver,
> > especially since it's set as tristate in Kconfig, thus I am not sure if
> > using builtin_platform_driver() over module_platform_driver() is correct?
> >
> > Unless this is more because you need to reply on device_initcall() for the
> > driver to properly initialise?
>
> builtin_platform_driver() does the right thing for loadable modules that
> have no module-unload and are not intended to be removable.
>
> This is often use for PCI drivers, but after Rob reworked this code a while
> back, it should actually be possible to reliably remove and reload PCI
> host bridge drivers, and it would be good to eventually lift the restriction
> here as well.
Thank you for letting me know. Much appreciated. I assumed in the past
that with tristate in Kconfig the module_platform_driver() would be the
preferred route.
Krzysztof
Powered by blists - more mailing lists