public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Daniel Scally <djrscally@gmail.com>,
	linux-acpi@vger.kernel.org, linux-clk@vger.kernel.org,
	platform-driver-x86@vger.kernel.org
Cc: rafael@kernel.org, lenb@kernel.org, mturquette@baylibre.com,
	sboyd@kernel.org, markgross@kernel.org, robert.moore@intel.com
Subject: Re: [PATCH 5/6] platform/x86: int3472: Support multiple gpio lookups in board data
Date: Mon, 21 Feb 2022 11:03:34 +0100	[thread overview]
Message-ID: <922e686e-26df-a07b-1c82-860127e8403b@redhat.com> (raw)
In-Reply-To: <20220216225304.53911-6-djrscally@gmail.com>

Hi,

On 2/16/22 23:53, Daniel Scally wrote:
> Currently, we only support passing a single gpiod_lookup_table as part
> of the board data for the tps68470 driver. This carries the implicit
> assumption that each TPS68470 device will only support a single
> sensor, which does not hold true.
> 
> Extend the code to support the possibility of multiple sensors each
> having a gpiod_lookup_table, and opportunistically add the lookup
> table for the Surface Go line's IR camera.
> 
> Signed-off-by: Daniel Scally <djrscally@gmail.com>
> ---
>  drivers/platform/x86/intel/int3472/tps68470.c | 18 ++++++++++-----
>  drivers/platform/x86/intel/int3472/tps68470.h |  3 ++-
>  .../x86/intel/int3472/tps68470_board_data.c   | 22 ++++++++++++++++---
>  3 files changed, 33 insertions(+), 10 deletions(-)
> 
> diff --git a/drivers/platform/x86/intel/int3472/tps68470.c b/drivers/platform/x86/intel/int3472/tps68470.c
> index b535564712bb..736480961ec3 100644
> --- a/drivers/platform/x86/intel/int3472/tps68470.c
> +++ b/drivers/platform/x86/intel/int3472/tps68470.c
> @@ -150,6 +150,7 @@ static int skl_int3472_tps68470_probe(struct i2c_client *client)
>  	struct regmap *regmap;
>  	int device_type;
>  	int ret;
> +	int i;
>  
>  	n_consumers = skl_int3472_fill_clk_pdata(&client->dev, &clk_pdata);
>  	if (n_consumers < 0)
> @@ -194,15 +195,18 @@ static int skl_int3472_tps68470_probe(struct i2c_client *client)
>  		cells[1].pdata_size = sizeof(struct tps68470_regulator_platform_data);
>  		cells[2].name = "tps68470-gpio";
>  
> -		gpiod_add_lookup_table(board_data->tps68470_gpio_lookup_table);
> +		for (i = 0; i < board_data->n_gpiod_lookups; i++)
> +			gpiod_add_lookup_table(board_data->tps68470_gpio_lookup_tables[i]);
>  
>  		ret = devm_mfd_add_devices(&client->dev, PLATFORM_DEVID_NONE,
>  					   cells, TPS68470_WIN_MFD_CELL_COUNT,
>  					   NULL, 0, NULL);
>  		kfree(cells);
>  
> -		if (ret)
> -			gpiod_remove_lookup_table(board_data->tps68470_gpio_lookup_table);
> +		if (ret) {
> +			for (i = 0; i < board_data->n_gpiod_lookups; i++)
> +				gpiod_remove_lookup_table(board_data->tps68470_gpio_lookup_tables[i]);
> +		}
>  
>  		break;
>  	case DESIGNED_FOR_CHROMEOS:
> @@ -226,10 +230,12 @@ static int skl_int3472_tps68470_probe(struct i2c_client *client)
>  static int skl_int3472_tps68470_remove(struct i2c_client *client)
>  {
>  	const struct int3472_tps68470_board_data *board_data;
> -
> +	int i;

Please keep an empty line between variable declarations and statements
(I believe checkpatch should have warned about this?)

>  	board_data = int3472_tps68470_get_board_data(dev_name(&client->dev));
> -	if (board_data)
> -		gpiod_remove_lookup_table(board_data->tps68470_gpio_lookup_table);
> +	if (board_data) {
> +		for (i = 0; i < board_data->n_gpiod_lookups; i++)
> +			gpiod_remove_lookup_table(board_data->tps68470_gpio_lookup_tables[i]);
> +	}
>  
>  	return 0;
>  }
> diff --git a/drivers/platform/x86/intel/int3472/tps68470.h b/drivers/platform/x86/intel/int3472/tps68470.h
> index cfd33eb62740..35915e701593 100644
> --- a/drivers/platform/x86/intel/int3472/tps68470.h
> +++ b/drivers/platform/x86/intel/int3472/tps68470.h
> @@ -16,8 +16,9 @@ struct tps68470_regulator_platform_data;
>  
>  struct int3472_tps68470_board_data {
>  	const char *dev_name;
> -	struct gpiod_lookup_table *tps68470_gpio_lookup_table;
>  	const struct tps68470_regulator_platform_data *tps68470_regulator_pdata;
> +	unsigned int n_gpiod_lookups;
> +	struct gpiod_lookup_table *tps68470_gpio_lookup_tables[];
>  };
>  
>  const struct int3472_tps68470_board_data *int3472_tps68470_get_board_data(const char *dev_name);
> diff --git a/drivers/platform/x86/intel/int3472/tps68470_board_data.c b/drivers/platform/x86/intel/int3472/tps68470_board_data.c
> index 525f09a3b5ff..442a8a2de224 100644
> --- a/drivers/platform/x86/intel/int3472/tps68470_board_data.c
> +++ b/drivers/platform/x86/intel/int3472/tps68470_board_data.c
> @@ -96,7 +96,7 @@ static const struct tps68470_regulator_platform_data surface_go_tps68470_pdata =
>  	},
>  };
>  
> -static struct gpiod_lookup_table surface_go_tps68470_gpios = {
> +static struct gpiod_lookup_table surface_go_int347a_gpios = {
>  	.dev_id = "i2c-INT347A:00",
>  	.table = {
>  		GPIO_LOOKUP("tps68470-gpio", 9, "reset", GPIO_ACTIVE_LOW),
> @@ -105,16 +105,32 @@ static struct gpiod_lookup_table surface_go_tps68470_gpios = {
>  	}
>  };
>  
> +static struct gpiod_lookup_table surface_go_int347e_gpios = {
> +	.dev_id = "i2c-INT347E:00",
> +	.table = {
> +		GPIO_LOOKUP("tps68470-gpio", 5, "enable", GPIO_ACTIVE_HIGH),
> +		{ }
> +	}
> +};
> +
>  static const struct int3472_tps68470_board_data surface_go_tps68470_board_data = {
>  	.dev_name = "i2c-INT3472:05",
> -	.tps68470_gpio_lookup_table = &surface_go_tps68470_gpios,
>  	.tps68470_regulator_pdata = &surface_go_tps68470_pdata,
> +	.n_gpiod_lookups = 2,
> +	.tps68470_gpio_lookup_tables = {
> +		&surface_go_int347a_gpios,
> +		&surface_go_int347e_gpios,
> +	}
>  };
>  
>  static const struct int3472_tps68470_board_data surface_go3_tps68470_board_data = {
>  	.dev_name = "i2c-INT3472:01",
> -	.tps68470_gpio_lookup_table = &surface_go_tps68470_gpios,
>  	.tps68470_regulator_pdata = &surface_go_tps68470_pdata,
> +	.n_gpiod_lookups = 2,
> +	.tps68470_gpio_lookup_tables = {
> +		&surface_go_int347a_gpios,
> +		&surface_go_int347e_gpios,
> +	}
>  };
>  
>  static const struct dmi_system_id int3472_tps68470_board_data_table[] = {

Otherwise this looks good to me:

Reviewed-by: Hans de Goede <hdegoede@redhat.com>

Regards,

Hans



  reply	other threads:[~2022-02-21 10:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 22:52 [PATCH 0/6] Add multiple-consumer support to int3472-tps68470 driver Daniel Scally
2022-02-16 22:52 ` [PATCH 1/6] ACPI: scan: Add acpi_dev_get_next_consumer_dev() Daniel Scally
2022-02-21  9:50   ` Hans de Goede
2022-02-21  9:51     ` Hans de Goede
2022-02-16 22:53 ` [PATCH 2/6] ACPI: bus: Add iterator for dependent devices Daniel Scally
2022-02-21  9:52   ` Hans de Goede
2022-02-16 22:53 ` [PATCH 3/6] platform/x86: int3472: Support multiple clock consumers Daniel Scally
2022-02-17  3:22   ` kernel test robot
2022-02-22 14:44     ` Hans de Goede
2022-02-22 14:47       ` Daniel Scally
2022-02-21  9:59   ` Hans de Goede
2022-02-25  0:49     ` Stephen Boyd
2022-02-25  9:22       ` Hans de Goede
2022-02-16 22:53 ` [PATCH 4/6] platform/x86: int3472: Add terminator to gpiod_lookup_table Daniel Scally
2022-02-21 10:00   ` Hans de Goede
2022-02-21 13:46   ` Hans de Goede
2022-02-16 22:53 ` [PATCH 5/6] platform/x86: int3472: Support multiple gpio lookups in board data Daniel Scally
2022-02-21 10:03   ` Hans de Goede [this message]
2022-02-16 22:53 ` [PATCH 6/6] platform/x86: int3472: Add board data for Surface Go2 IR camera Daniel Scally
2022-02-21 10:05   ` Hans de Goede
2022-02-17  9:55 ` [PATCH 0/6] Add multiple-consumer support to int3472-tps68470 driver Hans de Goede
2022-02-18  8:45   ` Daniel Scally
2022-02-21 10:07 ` 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=922e686e-26df-a07b-1c82-860127e8403b@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=djrscally@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=markgross@kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=robert.moore@intel.com \
    --cc=sboyd@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