From: Jonathan Cameron <jic23@kernel.org>
To: Philippe De Muyter <Philippe.DeMuyter@macq.eu>
Cc: linux-iio@vger.kernel.org, Philippe De Muyter <phdm@macqel.be>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>
Subject: Re: [PATCH] iio: dac: ad5446: Add ID of compatible Texas Instruments i2c dac121c*
Date: Sun, 7 May 2023 14:46:08 +0100 [thread overview]
Message-ID: <20230507144608.15e7aa8e@jic23-huawei> (raw)
In-Reply-To: <1683450625-28789-1-git-send-email-Philippe.DeMuyter@macq.eu>
On Sun, 7 May 2023 11:10:25 +0200
Philippe De Muyter <Philippe.DeMuyter@macq.eu> wrote:
> From: Philippe De Muyter <phdm@macqel.be>
>
> The Texas Instruments DAC121C* chips are the I2C counterparts of
> the DAC121S* SPI chips which are already supported by this ad5446 driver.
>
> Add them to the compatible list.
Hi Philippe,
DT binding should be updated and include the fallback to adi,ad5622.
Does this driver actually have a bindings doc? If not please add one
as a precursor patch then add binding for this new part on top.
>
> Signed-off-by: Philippe De Muyter <phdm@macqel.be>
> Cc: Lars-Peter Clausen <lars@metafoo.de>
> Cc: Michael Hennerich <Michael.Hennerich@analog.com>
> Cc: Jonathan Cameron <jic23@kernel.org>
> ---
> drivers/iio/dac/ad5446.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/iio/dac/ad5446.c b/drivers/iio/dac/ad5446.c
> index aa3130b33456..b95c0ccbb796 100644
> --- a/drivers/iio/dac/ad5446.c
> +++ b/drivers/iio/dac/ad5446.c
> @@ -587,6 +587,7 @@ static const struct i2c_device_id ad5446_i2c_ids[] = {
> {"ad5602", ID_AD5602},
> {"ad5612", ID_AD5612},
> {"ad5622", ID_AD5622},
> + {"dac121", ID_AD5622}, /* 'ti,' is dropped by 'of_modalias_node' */
True, but why is the comment needed?
Also, for consistency with the spi equivalent it should be dac121c101 or similar
I think.
I think this use of the driver with multiple vendor prefixes,
also indicates we should really add the of_device_id table for this
driver. To do that nicely will require more changes as we'd want to do
the same for the SPI side which has a single entry table (which is odd)
then deal with the data fields which should probably all be pointers
rather than enum values.
Still I'm fine with proper explicit DT support being left for a follow up patch.
I do want the missing binding doc fixed though (which is independent of the
question of how the driver binds based on the compatible values).
Thanks,
Jonathan
> {}
> };
> MODULE_DEVICE_TABLE(i2c, ad5446_i2c_ids);
next prev parent reply other threads:[~2023-05-07 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 9:10 [PATCH] iio: dac: ad5446: Add ID of compatible Texas Instruments i2c dac121c* Philippe De Muyter
2023-05-07 13:46 ` Jonathan Cameron [this message]
2023-05-08 8:37 ` Philippe De Muyter
2023-05-08 13:03 ` Philippe De Muyter
2023-05-13 18:00 ` Jonathan Cameron
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=20230507144608.15e7aa8e@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=Philippe.DeMuyter@macq.eu \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=phdm@macqel.be \
/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