From: Hans de Goede <hansg@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: adc: Add Intel Dollar Cove TI PMIC ADC driver
Date: Sat, 19 Jul 2025 18:17:15 +0200 [thread overview]
Message-ID: <68cac85c-d19e-4de8-b06b-1b82d30906fd@kernel.org> (raw)
In-Reply-To: <20250719120417.7bef0731@jic23-huawei>
Hi Jonathan,
On 19-Jul-25 1:04 PM, Jonathan Cameron wrote:
>>>> + ret = wait_event_timeout(info->wait, info->conversion_done, 5 * HZ);
>>>> + if (ret == 0) {
>>>> + dev_err(info->dev, "Error sample timeout\n");
>>>> + ret = -ETIMEDOUT;
>>>> + goto disable_adc;
>>>> + }
>>>> +
>>>> + ret = regmap_read(info->regmap, chan->address, &msb);
>>>> + if (ret)
>>>> + goto disable_adc;
>>>> +
>>>> + ret = regmap_read(info->regmap, chan->address + 1, &lsb);
>>> bulk read and an endian conversion + mask?
>>
>> This chip only supports reading 1 register at a time, I'll add
>> a comment about this.
>
> Set regmap_config.use_single_read and bulk reads should be fine.
Interesting, I did not know about that flag.
But I'm afraid that I've already ending up spending more time
then planned on supporting this old PMIC. fixing all other remarks
from you and Linus W.
And I also hit an i2c-core regression which I've just finished
debugging...
So I'm going to keep the multiple reg-reads as is (it won't
matter for what happens on the I2C bus anyways) I hope this is ok.
I did also write an interesting iio-core patch to make
iio_read_channel_processed_scale() more precise :)
I plan to post a a new series including this tomorrow.
Regards,
Hans
next prev parent reply other threads:[~2025-07-19 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 23:00 [PATCH] iio: adc: Add Intel Dollar Cove TI PMIC ADC driver Hans de Goede
2024-12-20 19:42 ` Jonathan Cameron
2025-07-18 10:56 ` Hans de Goede
2025-07-18 11:05 ` Hans de Goede
2025-07-19 11:04 ` Jonathan Cameron
2025-07-19 16:17 ` Hans de Goede [this message]
2025-07-24 13:23 ` 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=68cac85c-d19e-4de8-b06b-1b82d30906fd@kernel.org \
--to=hansg@kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@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;
as well as URLs for NNTP newsgroup(s).