From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Ghennadi Procopciuc" <ghennadi.procopciuc@oss.nxp.com>,
"Daniel Lezcano" <daniel.lezcano@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
Sashiko <sashiko-bot@kernel.org>
Subject: Re: [PATCH v1 1/1] iio: adc: nxp-sar-adc: Fix the delay calculation in nxp_sar_adc_wait_for()
Date: Fri, 3 Jul 2026 22:42:21 +0200 [thread overview]
Message-ID: <d04e0999-3598-45aa-bcee-d391ef6024cc@oss.qualcomm.com> (raw)
In-Reply-To: <20260703200626.40511970@jic23-huawei>
On 7/3/26 21:06, Jonathan Cameron wrote:
> On Tue, 26 May 2026 14:48:44 +0200
> Daniel Lezcano <daniel.lezcano@oss.qualcomm.com> wrote:
>
>> On 5/22/26 19:35, Jonathan Cameron wrote:
>>> On Tue, 19 May 2026 23:56:06 +0200
>>> Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
>>>
>>>> The original code was using ndelay() twice. In one case the delay
>>>> is calculated as 1/3 of ADC clock and in the other as 80 ADC clocks.
>>>> But according to the comments in all cases it should be a multiplier
>>>> of the ADC clock, and not a fraction of it. Inadvertently
>>>> nxp_sar_adc_wait_for() takes the wrong case and spread it over
>>>> the code make it wrong in all places. Fix this by modifying a helper
>>>> to correctly use the multiplier.
>>>>
>>>> Fixes: 7e5c0f97c66a ("iio: adc: nxp-sar-adc: Avoid division by zero")
>>>> Fixes: 4434072a893e ("iio: adc: Add the NXP SAR ADC support for the s32g2/3 platforms")
>>>> Reported-by: Sashiko <sashiko-bot@kernel.org>
>>>> Closes: https://sashiko.dev/#/patchset/20260416090122.758990-1-andriy.shevchenko%40linux.intel.com
>>>> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>>>
>>> Daniel, could you take a look at this one.
>>>
>>> Explanation seems fine but original patch was yours so I'd like
>>> some 'aware' eyes on it!
>>
>> Sounds like correct but let me loop in Ghenadi as I don't have the
>> platform anymore to check the change
>>
> Hi
>
> This one is still outstanding if anyone has a chance to look at it.
> If not I'll gamble and apply it :)
Yes sure, go ahead
Acked-by: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
next prev parent reply other threads:[~2026-07-03 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 21:56 Andy Shevchenko
2026-05-20 11:42 ` Stepan Ionichev
2026-05-22 17:35 ` Jonathan Cameron
2026-05-26 12:48 ` Daniel Lezcano
2026-07-03 19:06 ` Jonathan Cameron
2026-07-03 20:42 ` Daniel Lezcano [this message]
2026-07-03 22:55 ` 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=d04e0999-3598-45aa-bcee-d391ef6024cc@oss.qualcomm.com \
--to=daniel.lezcano@oss.qualcomm.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=daniel.lezcano@kernel.org \
--cc=dlechner@baylibre.com \
--cc=ghennadi.procopciuc@oss.nxp.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=sashiko-bot@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
all inboxes | Powered by JetHome®