Linux LED subsystem development
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Kate Hsuan <hpa@redhat.com>
Cc: Pavel Machek <pavel@ucw.cz>,
	linux-leds@vger.kernel.org, platform-driver-x86@vger.kernel.org,
	Hans de Goede <hdegoede@redhat.com>,
	Daniel Scally <djrscally@gmail.com>,
	Mark Gross <markgross@kernel.org>,
	Daniel Scally <dan.scally@ideasonboard.com>
Subject: Re: [PATCH v3 1/3] platform: x86: int3472: Add MFD cell for tps68470 LED
Date: Thu, 23 Mar 2023 12:23:27 +0000	[thread overview]
Message-ID: <20230323122327.GJ2673958@google.com> (raw)
In-Reply-To: <20230321153718.1355511-2-hpa@redhat.com>

On Tue, 21 Mar 2023, Kate Hsuan wrote:

> Add MFD cell for tps68470-led.
>
> Reviewed-by: Daniel Scally <dan.scally@ideasonboard.com>
> Signed-off-by: Kate Hsuan <hpa@redhat.com>
> ---
>  drivers/platform/x86/intel/int3472/tps68470.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/platform/x86/intel/int3472/tps68470.c b/drivers/platform/x86/intel/int3472/tps68470.c
> index 5b8d1a9620a5..82ef022f8916 100644
> --- a/drivers/platform/x86/intel/int3472/tps68470.c
> +++ b/drivers/platform/x86/intel/int3472/tps68470.c
> @@ -17,7 +17,7 @@
>  #define DESIGNED_FOR_CHROMEOS		1
>  #define DESIGNED_FOR_WINDOWS		2
>
> -#define TPS68470_WIN_MFD_CELL_COUNT	3
> +#define TPS68470_WIN_MFD_CELL_COUNT	4
>
>  static const struct mfd_cell tps68470_cros[] = {
>  	{ .name = "tps68470-gpio" },
> @@ -193,7 +193,8 @@ static int skl_int3472_tps68470_probe(struct i2c_client *client)
>  		cells[1].name = "tps68470-regulator";
>  		cells[1].platform_data = (void *)board_data->tps68470_regulator_pdata;
>  		cells[1].pdata_size = sizeof(struct tps68470_regulator_platform_data);
> -		cells[2].name = "tps68470-gpio";
> +		cells[2].name = "tps68470-led";
> +		cells[3].name = "tps68470-gpio";

The question is, why is the MFD API being used out side of drivers/mfd?

>  		for (i = 0; i < board_data->n_gpiod_lookups; i++)
>  			gpiod_add_lookup_table(board_data->tps68470_gpio_lookup_tables[i]);
> --
> 2.39.2
>

--
Lee Jones [李琼斯]

  parent reply	other threads:[~2023-03-23 12:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 15:37 [PATCH v3 0/3] leds: tps68470: LED driver for TPS68470 Kate Hsuan
2023-03-21 15:37 ` [PATCH v3 1/3] platform: x86: int3472: Add MFD cell for tps68470 LED Kate Hsuan
2023-03-22 16:46   ` Hans de Goede
2023-03-23 12:23   ` Lee Jones [this message]
2023-03-23 12:31     ` Hans de Goede
2023-03-23 14:57       ` Lee Jones
2023-03-21 15:37 ` [PATCH v3 2/3] include: mfd: tps68470: Add masks for LEDA and LEDB Kate Hsuan
2023-03-21 15:37 ` [PATCH v3 3/3] leds: tps68470: Add LED control for tps68470 Kate Hsuan
2023-03-22 16:46   ` Hans de Goede
2023-03-23  7:36   ` Dan Scally
2023-03-23 11:15   ` Pavel Machek
2023-03-23 11:24     ` Hans de Goede
2023-03-23 11:26       ` Pavel Machek
2023-03-23 11:29         ` Hans de Goede
2023-03-23 11:31           ` Hans de Goede
2023-03-23 11:36           ` Pavel Machek
2023-03-23 12:36             ` Hans de Goede

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=20230323122327.GJ2673958@google.com \
    --to=lee@kernel.org \
    --cc=dan.scally@ideasonboard.com \
    --cc=djrscally@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=hpa@redhat.com \
    --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