From: Alex Elder <elder@riscstar.com>
To: Andi Shyti <andi.shyti@kernel.org>,
Troy Mitchell <troy.mitchell@linux.spacemit.com>
Cc: Yixun Lan <dlan@gentoo.org>,
Aurelien Jarno <aurelien@aurel32.net>,
Michael Opdenacker <michael.opdenacker@rootcommit.com>,
Troy Mitchell <troymitchell988@gmail.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev
Subject: Re: [PATCH v6 2/2] i2c: spacemit: introduce pio for k1
Date: Thu, 15 Jan 2026 11:02:17 -0600 [thread overview]
Message-ID: <00f42b6c-857b-4eef-a0da-83053998135a@riscstar.com> (raw)
In-Reply-To: <aWeyT8gb8Z31S_V9@zenone.zhora.eu>
On 1/14/26 9:47 AM, Andi Shyti wrote:
> Hi Troy,
>
> ...
>
>> @@ -171,6 +176,16 @@ static int spacemit_i2c_handle_err(struct spacemit_i2c_dev *i2c)
>> return i2c->status & SPACEMIT_SR_ACKNAK ? -ENXIO : -EIO;
>> }
>>
>> +static inline void spacemit_i2c_delay(struct spacemit_i2c_dev *i2c,
>> + unsigned int min_us,
>> + unsigned int max_us)
>> +{
>> + if (i2c->use_pio)
>> + udelay(max_us);
>
> We need some control on how much we want to sleep in atomic. This
> can have effects on the whole system.
>
>> + else
>> + usleep_range(min_us, max_us);
>
> If we assume that max_us = min_us * 2 we don't need to pass it as
> a parameter. Even better you can use fsleep here which does it
> for you.
I agree with both of these comments/suggestions.
And if fsleep() were used, spacemit_i2c_delay() might be able
to just go away. (The range used in fsleep() isn't quite the
same as what you're using, but this is heuristic anyway.)
However the delay used in spacemit_i2c_check_bus_release() is
90-150 microseconds, which would lead to sleeping in fsleep().
Is there any chance 10 microseconds (or less) could be used
for all delays? Even if not, fsleep() might help here.
>> +}
>
> ...
. . .
>> - if (i2c->state != SPACEMIT_STATE_IDLE) {
>> - val |= SPACEMIT_CR_TB | SPACEMIT_CR_ALDIE;
>> -
>> - if (spacemit_i2c_is_last_msg(i2c)) {
>> - /* trigger next byte with stop */
>> - val |= SPACEMIT_CR_STOP;
>> -
>> - if (i2c->read)
>> - val |= SPACEMIT_CR_ACKNAK;
>> - }
>> - writel(val, i2c->base + SPACEMIT_ICR);
>> - }
>> + spacemit_i2c_handle_state(i2c);
>
> Next time this can be on a separate patch as a preparatory patch
> to make the review of this one a bit easier.
Yes! It's a next-level skill: beyond just changing the
code, breaking the change into good, independent pieces
that build on each other, to facilitate review.
Thanks!
-Alex
>
>>
>> -err_out:
>> - spacemit_i2c_err_check(i2c);
>> return IRQ_HANDLED;
>> }
>
> Thanks,
> Andi
next prev parent reply other threads:[~2026-01-15 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 7:52 [PATCH v6 0/2] " Troy Mitchell
2026-01-08 7:52 ` [PATCH v6 1/2] i2c: spacemit: move i2c_xfer_msg() Troy Mitchell
2026-01-08 7:52 ` [PATCH v6 2/2] i2c: spacemit: introduce pio for k1 Troy Mitchell
2026-01-14 15:47 ` Andi Shyti
2026-01-15 17:02 ` Alex Elder [this message]
2026-02-07 13:49 ` Troy Mitchell
2026-01-15 17:02 ` Alex Elder
2026-02-07 13:57 ` Troy Mitchell
2026-01-08 19:21 ` [PATCH v6 0/2] " Aurelien Jarno
2026-01-27 22:51 ` Aurelien Jarno
2026-01-29 9:58 ` Troy Mitchell
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=00f42b6c-857b-4eef-a0da-83053998135a@riscstar.com \
--to=elder@riscstar.com \
--cc=andi.shyti@kernel.org \
--cc=aurelien@aurel32.net \
--cc=dlan@gentoo.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=michael.opdenacker@rootcommit.com \
--cc=spacemit@lists.linux.dev \
--cc=troy.mitchell@linux.spacemit.com \
--cc=troymitchell988@gmail.com \
/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®