From: Hans de Goede <hdegoede@redhat.com>
To: Henning Schild <henning.schild@siemens.com>,
Pavel Machek <pavel@ucw.cz>, Lee Jones <lee@kernel.org>,
Mark Gross <markgross@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v2 3/3] leds: simatic-ipc-leds-gpio: introduce more Kconfig switches
Date: Wed, 1 Mar 2023 19:04:01 +0100 [thread overview]
Message-ID: <a6281345-95e1-3e8d-b6fb-146c1852373f@redhat.com> (raw)
In-Reply-To: <20230301170215.23382-4-henning.schild@siemens.com>
Hi,
On 3/1/23 18:02, Henning Schild wrote:
> To describe the dependency chain better and allow for potential
> fine-grained config tuning, introduce Kconfig switch for the individual
> GPIO based drivers.
>
> Signed-off-by: Henning Schild <henning.schild@siemens.com>
> ---
> drivers/leds/simple/Kconfig | 31 ++++++++++++++++++++++++++++---
> drivers/leds/simple/Makefile | 7 +++----
> 2 files changed, 31 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/leds/simple/Kconfig b/drivers/leds/simple/Kconfig
> index fd2b8225d926..44fa0f93cb3b 100644
> --- a/drivers/leds/simple/Kconfig
> +++ b/drivers/leds/simple/Kconfig
> @@ -1,11 +1,36 @@
> # SPDX-License-Identifier: GPL-2.0-only
> config LEDS_SIEMENS_SIMATIC_IPC
> tristate "LED driver for Siemens Simatic IPCs"
> - depends on LEDS_GPIO
Since it is simatic-ipc-leds-gpio-core.c which actually registers
the LEDs GPIO platform device, this one should stay IMHO.
> depends on SIEMENS_SIMATIC_IPC
> help
> This option enables support for the LEDs of several Industrial PCs
> from Siemens.
>
> - To compile this driver as a module, choose M here: the modules
> - will be called simatic-ipc-leds and simatic-ipc-leds-gpio.
> + To compile this driver as a module, choose M here: the module
> + will be called simatic-ipc-leds.
> +
> +config LEDS_SIEMENS_SIMATIC_IPC_APOLLOLAKE
> + tristate "LED driver for Siemens Simatic IPCs based on Intel Apollo Lake GPIO"
> + depends on LEDS_GPIO
And then it can be dropped here.
> + depends on PINCTRL_BROXTON
> + depends on SIEMENS_SIMATIC_IPC
This should be "depends on LEDS_SIEMENS_SIMATIC_IPC" since it
actually uses symbol from that module.
> + default LEDS_SIEMENS_SIMATIC_IPC
> + help
> + This option enables support for the LEDs of several Industrial PCs
> + from Siemens based on Apollo Lake GPIO i.e. IPC127E.
> +
> + To compile this driver as a module, choose M here: the module
> + will be called simatic-ipc-leds-gpio-apollolake.
> +
> +config LEDS_SIEMENS_SIMATIC_IPC_F7188X
> + tristate "LED driver for Siemens Simatic IPCs based on Nuvoton GPIO"
> + depends on LEDS_GPIO
Idem.
> + depends on GPIO_F7188X
> + depends on SIEMENS_SIMATIC_IPC
Idem.
> + default LEDS_SIEMENS_SIMATIC_IPC
> + help
> + This option enables support for the LEDs of several Industrial PCs
> + from Siemens based on Nuvoton GPIO i.e. IPC227G.
> +
> + To compile this driver as a module, choose M here: the module
> + will be called simatic-ipc-leds-gpio-f7188x.
> diff --git a/drivers/leds/simple/Makefile b/drivers/leds/simple/Makefile
> index ed9057f7b6da..e3e840cea275 100644
> --- a/drivers/leds/simple/Makefile
> +++ b/drivers/leds/simple/Makefile
> @@ -1,5 +1,4 @@
> # SPDX-License-Identifier: GPL-2.0
> -obj-$(CONFIG_LEDS_SIEMENS_SIMATIC_IPC) += simatic-ipc-leds.o
> -obj-$(CONFIG_LEDS_SIEMENS_SIMATIC_IPC) += simatic-ipc-leds-gpio-core.o
> -obj-$(CONFIG_LEDS_SIEMENS_SIMATIC_IPC) += simatic-ipc-leds-gpio-apollolake.o
> -obj-$(CONFIG_LEDS_SIEMENS_SIMATIC_IPC) += simatic-ipc-leds-gpio-f7188x.o
> +obj-$(CONFIG_LEDS_SIEMENS_SIMATIC_IPC) += simatic-ipc-leds.o
> +obj-$(CONFIG_LEDS_SIEMENS_SIMATIC_IPC_APOLLOLAKE) += simatic-ipc-leds-gpio-core.o simatic-ipc-leds-gpio-apollolake.o
> +obj-$(CONFIG_LEDS_SIEMENS_SIMATIC_IPC_F7188X) += simatic-ipc-leds-gpio-core.o simatic-ipc-leds-gpio-f7188x.o
Regards,
Hans
next prev parent reply other threads:[~2023-03-01 18:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 17:02 [PATCH v2 0/3] leds: simatic-ipc-leds-gpio: split up Henning Schild
2023-03-01 17:02 ` [PATCH v2 1/3] leds: simatic-ipc-leds-gpio: move two extra gpio pins into another table Henning Schild
2023-03-01 17:21 ` Andy Shevchenko
2023-03-02 8:33 ` Henning Schild
2023-03-01 17:02 ` [PATCH v2 2/3] leds: simatic-ipc-leds-gpio: split up into multiple drivers Henning Schild
2023-03-01 17:28 ` Andy Shevchenko
2023-03-02 8:40 ` Henning Schild
2023-03-02 15:46 ` Andy Shevchenko
2023-03-02 15:58 ` Henning Schild
2023-03-02 16:21 ` Andy Shevchenko
2023-03-02 17:06 ` Henning Schild
2023-05-15 11:14 ` Henning Schild
2023-03-01 17:02 ` [PATCH v2 3/3] leds: simatic-ipc-leds-gpio: introduce more Kconfig switches Henning Schild
2023-03-01 17:29 ` Andy Shevchenko
2023-03-02 8:31 ` Henning Schild
2023-03-01 18:04 ` Hans de Goede [this message]
2023-03-02 8:47 ` Henning Schild
2023-03-02 9:02 ` Hans de Goede
2023-03-02 10:14 ` Henning Schild
2023-05-15 10:41 ` Henning Schild
2023-05-15 11:24 ` Hans de Goede
2023-03-01 17:30 ` [PATCH v2 0/3] leds: simatic-ipc-leds-gpio: split up Andy Shevchenko
2023-03-02 10:19 ` Henning Schild
2023-05-13 10:08 ` Henning Schild
2023-05-15 9:50 ` Lee Jones
2023-05-15 10:01 ` Henning Schild
2023-05-15 12:12 ` Lee Jones
2023-05-15 15:06 ` Henning Schild
2023-05-15 15:40 ` Lee Jones
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=a6281345-95e1-3e8d-b6fb-146c1852373f@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=henning.schild@siemens.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=pavel@ucw.cz \
--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;
as well as URLs for NNTP newsgroup(s).