Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Mugilraj Dhavachelvan <dmugil2000@gmail.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	linux-iio@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] iio: potentiometer: ad5110: Use i2c_get_match_data()
Date: Mon, 28 Aug 2023 17:21:41 +0100	[thread overview]
Message-ID: <20230828172141.47f61baf@jic23-huawei> (raw)
In-Reply-To: <20230812150838.185055-1-biju.das.jz@bp.renesas.com>

On Sat, 12 Aug 2023 16:08:38 +0100
Biju Das <biju.das.jz@bp.renesas.com> wrote:

> Replace device_get_match_data()->i2c_get_match_data by making similar I2C
> and DT-based matching table to extend matching support for ID table.
> 
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>

Could have been a little clearer on the reasoning for doign this, but meh there
are a lot of them and this is moving things forwards.

Applied.

Thanks,

Jonathan

> ---
>  drivers/iio/potentiometer/ad5110.c | 21 +++++++++++++--------
>  1 file changed, 13 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/iio/potentiometer/ad5110.c b/drivers/iio/potentiometer/ad5110.c
> index 991e745c4f93..aaf02cc7aeba 100644
> --- a/drivers/iio/potentiometer/ad5110.c
> +++ b/drivers/iio/potentiometer/ad5110.c
> @@ -278,14 +278,19 @@ static const struct of_device_id ad5110_of_match[] = {
>  };
>  MODULE_DEVICE_TABLE(of, ad5110_of_match);
>  
> +#define AD5110_ID_TABLE(_name, cfg) {				\
> +	.name = _name,						\
> +	.driver_data = (kernel_ulong_t)&ad5110_cfg[cfg],	\
> +}
> +
>  static const struct i2c_device_id ad5110_id[] = {
> -	{ "ad5110-10", AD5110_10 },
> -	{ "ad5110-80", AD5110_80 },
> -	{ "ad5112-05", AD5112_05 },
> -	{ "ad5112-10", AD5112_10 },
> -	{ "ad5112-80", AD5112_80 },
> -	{ "ad5114-10", AD5114_10 },
> -	{ "ad5114-80", AD5114_80 },
> +	AD5110_ID_TABLE("ad5110-10", AD5110_10),
> +	AD5110_ID_TABLE("ad5110-80", AD5110_80),
> +	AD5110_ID_TABLE("ad5112-05", AD5112_05),
> +	AD5110_ID_TABLE("ad5112-10", AD5112_10),
> +	AD5110_ID_TABLE("ad5112-80", AD5112_80),
> +	AD5110_ID_TABLE("ad5114-10", AD5114_10),
> +	AD5110_ID_TABLE("ad5114-80", AD5114_80),
>  	{ }
>  };
>  MODULE_DEVICE_TABLE(i2c, ad5110_id);
> @@ -305,7 +310,7 @@ static int ad5110_probe(struct i2c_client *client)
>  	data->client = client;
>  	mutex_init(&data->lock);
>  	data->enable = 1;
> -	data->cfg = device_get_match_data(dev);
> +	data->cfg = i2c_get_match_data(client);
>  
>  	/* refresh RDAC register with EEPROM */
>  	ret = ad5110_write(data, AD5110_RESET, 0);


      reply	other threads:[~2023-08-28 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-12 15:08 [PATCH] iio: potentiometer: ad5110: Use i2c_get_match_data() Biju Das
2023-08-28 16:21 ` Jonathan Cameron [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=20230828172141.47f61baf@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=dmugil2000@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-renesas-soc@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