From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Andy Shevchenko <andy@kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Linus Walleij <linus.walleij@linaro.org>,
platform-driver-x86@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2] gpio: tps68470: Allow building as module
Date: Tue, 11 Jan 2022 14:06:12 +0200 [thread overview]
Message-ID: <Yd1ytDROGGbk2TNi@smile.fi.intel.com> (raw)
In-Reply-To: <20220111105632.219581-1-hdegoede@redhat.com>
On Tue, Jan 11, 2022 at 11:56:32AM +0100, Hans de Goede wrote:
> The gpio-tps68470 driver binds to a tps68470-gpio platform-device which
> itself gets instantiated by a special MFD driver from
> drivers/platform/x86/intel/int3472/tps68470.c
>
> This MFD driver itself can be built as a module, so it makes no sense to
> force the gpio-tps68470 driver to always be built-in.
Pushed (along with patch 2/2 from v1) to my review and testing queue, thanks!
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
> Changes in v2:
> - Fix some spelling errors in the commit msg
> - Remove blank line between tps68470_gpio_driver decleration and
> module_platform_driver(tps68470_gpio_driver)
> ---
> drivers/gpio/Kconfig | 6 +-----
> drivers/gpio/gpio-tps68470.c | 5 ++++-
> 2 files changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
> index 60d9374c72c0..3ac5860e0aeb 100644
> --- a/drivers/gpio/Kconfig
> +++ b/drivers/gpio/Kconfig
> @@ -1393,7 +1393,7 @@ config GPIO_TPS65912
> This driver supports TPS65912 GPIO chip.
>
> config GPIO_TPS68470
> - bool "TPS68470 GPIO"
> + tristate "TPS68470 GPIO"
> depends on INTEL_SKL_INT3472
> help
> Select this option to enable GPIO driver for the TPS68470
> @@ -1403,10 +1403,6 @@ config GPIO_TPS68470
> input or output as appropriate, the sensor related GPIOs
> are "output only" GPIOs.
>
> - This driver config is bool, as the GPIO functionality
> - of the TPS68470 must be available before dependent
> - drivers are loaded.
> -
> config GPIO_TQMX86
> tristate "TQ-Systems QTMX86 GPIO"
> depends on MFD_TQMX86 || COMPILE_TEST
> diff --git a/drivers/gpio/gpio-tps68470.c b/drivers/gpio/gpio-tps68470.c
> index 423b7bc30ae8..aaddcabe9b35 100644
> --- a/drivers/gpio/gpio-tps68470.c
> +++ b/drivers/gpio/gpio-tps68470.c
> @@ -154,5 +154,8 @@ static struct platform_driver tps68470_gpio_driver = {
> },
> .probe = tps68470_gpio_probe,
> };
> +module_platform_driver(tps68470_gpio_driver);
>
> -builtin_platform_driver(tps68470_gpio_driver)
> +MODULE_ALIAS("platform:tps68470-gpio");
> +MODULE_DESCRIPTION("GPIO driver for TPS68470 PMIC");
> +MODULE_LICENSE("GPL v2");
> --
> 2.33.1
>
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2022-01-11 12:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 10:56 [PATCH v2] gpio: tps68470: Allow building as module Hans de Goede
2022-01-11 11:31 ` Andy Shevchenko
2022-01-11 11:46 ` Hans de Goede
2022-01-11 12:02 ` Andy Shevchenko
2022-01-11 12:03 ` Andy Shevchenko
2022-01-11 12:13 ` Hans de Goede
2022-01-11 12:06 ` Andy Shevchenko [this message]
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=Yd1ytDROGGbk2TNi@smile.fi.intel.com \
--to=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=bgolaszewski@baylibre.com \
--cc=hdegoede@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=platform-driver-x86@vger.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