From: Hans de Goede <hansg@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Lee Jones <lee@kernel.org>, Andy Shevchenko <andy@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] mfd: intel_soc_pmic_chtdc_ti: Set use_single_read regmap_config flag
Date: Mon, 4 Aug 2025 10:51:42 +0200 [thread overview]
Message-ID: <592e9a1e-a58f-435d-aff7-13c13fe0598a@kernel.org> (raw)
In-Reply-To: <CAHp75VdfJvKb6VegNWCiiKoQkMBf0dQPs5yP3XfPM1icgtuyeg@mail.gmail.com>
Hi Andy,
On 4-Aug-25 10:47 AM, Andy Shevchenko wrote:
> On Mon, Aug 4, 2025 at 10:34 AM Hans de Goede <hansg@kernel.org> wrote:
>>
>> Testing has shown that reading multiple registers at once (for 10 bit
>> adc values) does not work. Set the use_single_read regmap_config flag
>> to make regmap split these for is.
>>
>> This should fix temperature opregion accesses done by
>> drivers/acpi/pmic/intel_pmic_chtdc_ti.c and is also necessary for
>> the upcoming drivers for the ADC and battery MFD cells.
>
> ...
>
>> + /* Reading multiple registers at once is not supported */
>> + .use_single_read = true,
>
> By HW or by problem in regmap as being suggested here:
> https://lore.kernel.org/linux-gpio/CALNFmy1ZRqHz6_DD_2qamm-iLQ51AOFQH=ahCWRN7SAk3pfZ_A@mail.gmail.com/
> ?
This is a hw limitation. I tried with i2ctransfer to directly
access the chip and it returns invalid values (1) after
the first byte read.
> As a quick fix I am fine with this.
> Reviewed-by: Andy Shevchenko <andy@kernel.org>
Thank you.
Regards,
Hans
1) I don't remember if it was 0, 0xff or repeating
of the first byte. But it definitely did not work.
next prev parent reply other threads:[~2025-08-04 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 8:34 [PATCH] mfd: intel_soc_pmic_chtdc_ti: Set use_single_read regmap_config flag Hans de Goede
2025-08-04 8:47 ` Andy Shevchenko
2025-08-04 8:51 ` Hans de Goede [this message]
2025-08-04 8:57 ` Andy Shevchenko
2025-08-04 12:08 ` 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=592e9a1e-a58f-435d-aff7-13c13fe0598a@kernel.org \
--to=hansg@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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