From: Jonathan Cameron <jic23@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Marek Vasut" <marex@denx.de>,
linux-iio@vger.kernel.org,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Prabhakar Mahadev Lad" <prabhakar.mahadev-lad.rj@bp.renesas.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 2/2] iio: dac: mcp4725: Use i2c_get_match_data()
Date: Mon, 28 Aug 2023 13:45:27 +0100 [thread overview]
Message-ID: <20230828134527.412c18cf@jic23-huawei> (raw)
In-Reply-To: <20230818174905.324623-3-biju.das.jz@bp.renesas.com>
On Fri, 18 Aug 2023 18:49:05 +0100
Biju Das <biju.das.jz@bp.renesas.com> wrote:
> Replace local variable chip_id with struct iio_chan_spec for device data
> and use its .ext_info for chip identification. After this replace
> device_get_match_data() and id lookup for retrieving match data
> by i2c_get_match_data() by converting enum->pointer for data in the
> match table.
>
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
The use of ext_info on a channel is messy. Please just define
a clearly named flag in chip_info to make it simpler to maintain
and extend.
Jonathan
> ---
> v1->v2:
> * No change.
> ---
> drivers/iio/dac/mcp4725.c | 26 ++++++++++++--------------
> 1 file changed, 12 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/iio/dac/mcp4725.c b/drivers/iio/dac/mcp4725.c
> index 33a61f65bc25..f9ce01c4cc53 100644
> --- a/drivers/iio/dac/mcp4725.c
> +++ b/drivers/iio/dac/mcp4725.c
> @@ -386,7 +386,7 @@ static int mcp4725_probe(struct i2c_client *client)
> struct mcp4725_data *data;
> struct iio_dev *indio_dev;
> struct mcp4725_platform_data *pdata, pdata_dt;
> - int chip_id;
> + const struct iio_chan_spec *ch;
> u8 inbuf[4];
> u8 pd;
> u8 ref;
> @@ -398,10 +398,8 @@ static int mcp4725_probe(struct i2c_client *client)
> data = iio_priv(indio_dev);
> i2c_set_clientdata(client, indio_dev);
> data->client = client;
> - if (dev_fwnode(&client->dev))
> - chip_id = (uintptr_t)device_get_match_data(&client->dev);
> - else
> - chip_id = id->driver_data;
> + ch = i2c_get_match_data(client);
> +
> pdata = dev_get_platdata(&client->dev);
>
> if (!pdata) {
> @@ -414,7 +412,7 @@ static int mcp4725_probe(struct i2c_client *client)
> pdata = &pdata_dt;
> }
>
> - if (chip_id == MCP4725 && pdata->use_vref) {
> + if (ch->ext_info == mcp4725_ext_info && pdata->use_vref) {
I think this will end up being hard to maintain.
Please define a mcp4725_chip_info structure and put the channels in there
+ a flag that says if the device in question supports an external reference.
> dev_err(&client->dev,
> "external reference is unavailable on MCP4725");
> return -EINVAL;
> @@ -455,12 +453,12 @@ static int mcp4725_probe(struct i2c_client *client)
>
> indio_dev->name = id->name;
> indio_dev->info = &mcp4725_info;
> - indio_dev->channels = &mcp472x_channel[chip_id];
> + indio_dev->channels = ch;
> indio_dev->num_channels = 1;
> indio_dev->modes = INDIO_DIRECT_MODE;
>
> /* read current DAC value and settings */
> - err = i2c_master_recv(client, inbuf, chip_id == MCP4725 ? 3 : 4);
> + err = i2c_master_recv(client, inbuf, ch->ext_info == mcp4725_ext_info ? 3 : 4);
>
> if (err < 0) {
> dev_err(&client->dev, "failed to read DAC value");
> @@ -470,10 +468,10 @@ static int mcp4725_probe(struct i2c_client *client)
> data->powerdown = pd > 0;
> data->powerdown_mode = pd ? pd - 1 : 2; /* largest resistor to gnd */
> data->dac_value = (inbuf[1] << 4) | (inbuf[2] >> 4);
> - if (chip_id == MCP4726)
> + if (ch->ext_info == mcp4726_ext_info)
> ref = (inbuf[3] >> 3) & 0x3;
Add a flag to the chip_info structure for whatever we are controlling here
and then have
if (info->x_is_supported)
...
>
> - if (chip_id == MCP4726 && ref != data->ref_mode) {
> + if (ch->ext_info == mcp4726_ext_info && ref != data->ref_mode) {
I think this can also use the vref bool I suggest adding above.
> dev_info(&client->dev,
> "voltage reference mode differs (conf: %u, eeprom: %u), setting %u",
> data->ref_mode, ref, data->ref_mode);
> @@ -511,8 +509,8 @@ static void mcp4725_remove(struct i2c_client *client)
> }
>
> static const struct i2c_device_id mcp4725_id[] = {
> - { "mcp4725", MCP4725 },
> - { "mcp4726", MCP4726 },
> + { "mcp4725", (kernel_ulong_t)&mcp472x_channel[MCP4725] },
> + { "mcp4726", (kernel_ulong_t)&mcp472x_channel[MCP4726] },
> { }
> };
> MODULE_DEVICE_TABLE(i2c, mcp4725_id);
> @@ -520,11 +518,11 @@ MODULE_DEVICE_TABLE(i2c, mcp4725_id);
> static const struct of_device_id mcp4725_of_match[] = {
> {
> .compatible = "microchip,mcp4725",
> - .data = (void *)MCP4725
> + .data = &mcp472x_channel[MCP4725]
> },
> {
> .compatible = "microchip,mcp4726",
> - .data = (void *)MCP4726
> + .data = &mcp472x_channel[MCP4726]
> },
> { }
> };
next prev parent reply other threads:[~2023-08-28 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 17:49 [PATCH v2 0/2] Use i2c_get_match_data() for mcp4725 DAC Biju Das
2023-08-18 17:49 ` [PATCH v2 1/2] iio: dac: mcp4725: Replace variable 'id' from struct mcp4725_data Biju Das
2023-08-18 17:49 ` [PATCH v2 2/2] iio: dac: mcp4725: Use i2c_get_match_data() Biju Das
2023-08-28 12:45 ` Jonathan Cameron [this message]
2023-08-29 14:35 ` Biju Das
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=20230828134527.412c18cf@jic23-huawei \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marex@denx.de \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=u.kleine-koenig@pengutronix.de \
/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