Linux USB
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Orgad Shaneh" <orgads@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH v2] usb: octeon-hcd: keep SOF interrupts while a pipe needs them
Date: Sun, 11 Oct 2026 08:12:39 +0000	[thread overview]
Message-ID: <sashiko-outbox-167120@kernel.org> (raw)
In-Reply-To: <20261011080506.2394708-1-orgads@gmail.com>

> cvmx_usb_schedule() now sleeps on an hrtimer until the nearest future
> periodic deadline instead of counting frames down on every SOF. The scan
> that finds that deadline only looks at pipes with
> 
> 	next_tx_frame > usb->frame_number
> 
> which is right for picking the deadline, but two kinds of pipe that
> need a SOF to make progress are invisible to the decision:
> 
> - A periodic pipe that is due and was *not* started: no idle hardware
>   channel this round, its split window is closed
>   (cvmx_usb_find_ready_pipe() rejects both), or another pipe owns
>   usb->active_split. cvmx_usb_next_pipe() looks at the isochronous and
>   interrupt lists only when is_sof is true.
> 
> [ ... ]
> "due" and would keep SOF enabled permanently.
> 
> Fixes: aebbc7d63407 ("usb: octeon-hcd: sleep on an hrtimer for far-off periodic transfers")
> Assisted-by: LLM
> Signed-off-by: Orgad Shaneh <orgads@gmail.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261011080506.2394708-1-orgads@gmail.com?part=1


      reply	other threads:[~2026-10-11  8:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-11  7:22 [PATCH RESEND] usb: octeon-hcd: keep SOF interrupts while a periodic pipe is due Orgad Shaneh
2026-10-11  7:33 ` sashiko-bot
2026-10-11  8:05 ` [PATCH v2] usb: octeon-hcd: keep SOF interrupts while a pipe needs them Orgad Shaneh
2026-10-11  8:12   ` sashiko-bot [this message]

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=sashiko-outbox-167120@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=orgads@gmail.com \
    --cc=sashiko-reviews@lists.linux.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