Linux USB
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 221721] prom21-xhci does not allow to use USB keyboard in plymouth
Date: Mon, 13 Jul 2026 06:44:25 +0000	[thread overview]
Message-ID: <bug-221721-208809-On8WcF8pGN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221721-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=221721

--- Comment #9 from Jihong Min (hurryman2212@gmail.com) ---
(In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from
comment #8)
> > I may end up doing PR to that as well.
> 
> Well, fixing this is nice, but do you plan to fix this on the kernel level,
> too? This is maybe a borderline thing wrt to the "no regressions" rule, but
> still would be nice to prevent problems for users that do update their
> kernels without updating their initramfs tool.

Currently, there is no plan to address this in the kernel.

During the patch review series, it was concluded to implement this in the
Renesas way, which does not "pollute" the generic "xhci-pci.c", and requires
the very same approach (initramfs building tools must address this issue to
explicitly include `xhci-pci-prom21` same as `xhci-pci-renesas` (for dracut),
or "correctly" detects the module tree for system-available devices in so
called "dep" or "hostonly" mode (it seems dracut fails in this point but others
look better in the handling routine).

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2026-07-13  6:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-04 15:41 [Bug 221721] New: prom21-xhci does not allow to use USB keyboard in plymouth bugzilla-daemon
2026-07-05 10:11 ` [Bug 221721] " bugzilla-daemon
2026-07-07  8:03 ` [Bug 221721] New: " Thorsten Leemhuis
2026-07-07  9:24   ` Jihong Min
2026-07-07  9:53   ` Jihong Min
2026-07-07 22:19     ` Jihong Min
2026-07-07  8:04 ` [Bug 221721] " bugzilla-daemon
2026-07-07  9:24 ` bugzilla-daemon
2026-07-07  9:54 ` bugzilla-daemon
2026-07-07 22:20 ` bugzilla-daemon
2026-07-10 15:22 ` bugzilla-daemon
2026-07-11 21:01 ` bugzilla-daemon
2026-07-13  6:38 ` bugzilla-daemon
2026-07-13  6:44 ` bugzilla-daemon [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=bug-221721-208809-On8WcF8pGN@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@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