Linux Serial subsystem development
 help / color / mirror / Atom feed
From: FUJITA Tomonori <tomo@flapping.org>
To: gary@garyguo.net, markus.probst@posteo.de, aliceryhl@google.com
Cc: tomo@flapping.org, dakr@kernel.org, ojeda@kernel.org,
	a.hindborg@kernel.org, acourbot@nvidia.com,
	bjorn3_gh@protonmail.com, boqun@kernel.org,
	daniel.almeida@collabora.com, lossin@kernel.org,
	tamird@kernel.org, tmgross@umich.edu, work@onurozkan.dev,
	linux-serial@vger.kernel.org, rust-for-linux@vger.kernel.org,
	fujita.tomonori@gmail.com
Subject: Re: [PATCH v1] rust: serdev: use Delta<Jiffy> for timeouts
Date: Thu, 01 Oct 2026 09:29:31 +0900 (JST)	[thread overview]
Message-ID: <20261001.092931.734162860031900892.tomo@flapping.org> (raw)
In-Reply-To: <DLSP8RHJMYFZ.3II53ESHY15IL@garyguo.net>

On Wed, 30 Sep 2026 14:52:50 +0100
"Gary Guo" <gary@garyguo.net> wrote:

>>> diff --git a/rust/kernel/serdev.rs b/rust/kernel/serdev.rs
>>> index 17ca504b7f8d..094503f059ff 100644
>>> --- a/rust/kernel/serdev.rs
>>> +++ b/rust/kernel/serdev.rs

(snip)

>>>      #[inline]
>>> -    pub fn write_all(&self, data: &[u8], timeout: Jiffies) -> Result<usize> {
>>> +    pub fn write_all(&self, data: &[u8], timeout: Delta<Jiffy>) -> Result<usize> {
>>>          if data.len() > i32::MAX as usize {
>>>              return Err(EINVAL);
>>>          }
>>>  
>>> +        let timeout = isize::max(timeout.as_jiffies(), 0);
>>> +

(snip)

>>>      /// Use a timeout of 0 to wait indefinitely.
>>>      #[inline]
>>> -    pub fn wait_until_sent(&self, timeout: Jiffies) {
>>> +    pub fn wait_until_sent(&self, timeout: Delta<Jiffy>) {
>>> +        let timeout = isize::max(timeout.as_jiffies(), 0);
>>> +
>>>          // SAFETY: `self.as_raw()` is guaranteed to be a pointer to a valid `serdev_device`.
>>> -        unsafe {
>>> -            bindings::serdev_device_wait_until_sent(
>>> -                self.as_raw(),
>>> -                isize::try_from(timeout).unwrap_or_default(),
>>> -            )
>>> -        };
>>> +        unsafe { bindings::serdev_device_wait_until_sent(self.as_raw(), timeout) };
>>>      }
>>>  }
>>>  
>>> 
>>> base-commit: f1850e443b0e4f2429ddf42a8d5033ea54ae8a90
>>
>> Both functions have "Use a timeout of 0 to wait indefinitely." inside
>> the rustdoc.
>>
>> Make sure `Delta::ZERO` is also usable for `Delta<Jiffy>` and replace
>> the 0 in the rustdoc with "[`Delta::<Jiffy>::ZERO`]". You might also
>> remove the "timeout of" part, but I don't mind if it stays.
> 
> I think the API should ideally use `Option<Delta<Jiffies>>` for this case, and
> use `None` to represent indefinite wait.

For read_poll_timeout(), where a timeout of 0 means "never time out"
in C, we did not take Option for the timeout. Alice's comment [1]:

| Another thing is the `timeout_delta` option. I would just have
| written it as two methods, one that takes a timeout and one that
| doesn't. That way, callers that don't need a timeout do not need to
| handle timeout errors. (Do we have any users without a timeout? If
| not, maybe just remove the Option.)

serdev is in the same situation. Do we want an API that uses None for
"never" here?

[1] https://lore.kernel.org/rust-for-linux/aJm9A_D-zlJtbV6X@google.com/

  parent reply	other threads:[~2026-10-01  0:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  4:13 [PATCH v1] rust: serdev: use Delta<Jiffy> for timeouts FUJITA Tomonori
2026-09-30  4:21 ` sashiko-bot
2026-09-30 12:59 ` Markus Probst
2026-09-30 13:52   ` Gary Guo
2026-09-30 14:07     ` Markus Probst
2026-10-01  0:29     ` FUJITA Tomonori [this message]
2026-10-01  0:39       ` Gary Guo
2026-10-01  1:28         ` FUJITA Tomonori
2026-10-01  2:27           ` Gary Guo
2026-10-01  4:26             ` FUJITA Tomonori

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=20261001.092931.734162860031900892.tomo@flapping.org \
    --to=tomo@flapping.org \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=fujita.tomonori@gmail.com \
    --cc=gary@garyguo.net \
    --cc=linux-serial@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=markus.probst@posteo.de \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tamird@kernel.org \
    --cc=tmgross@umich.edu \
    --cc=work@onurozkan.dev \
    /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