From: Myeonghun Pak <mhun512@gmail.com>
To: stern@rowland.harvard.edu, gregkh@linuxfoundation.org
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
krzk@kernel.org, peter.griffin@linaro.org,
alim.akhtar@samsung.com, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: [PATCH 0/3] usb: host: Disable controller wakeup on removal
Date: Sun, 13 Sep 2026 18:37:29 -0400 [thread overview]
Message-ID: <20260913223732.92882-1-mhun512@gmail.com> (raw)
These three independent patches balance the controller wakeup enable in
the generic EHCI, generic OHCI and Exynos OHCI drivers. Each disables
controller wakeup after usb_remove_hcd(), before releasing the remaining
driver-owned resources. No shared USB core behavior is changed.
For generic EHCI, a wakeup-capable ACPI companion provides the capability
setting through acpi_bind_one(). For the two OHCI drivers, ohci_run() sets
controller capability when OHCI_CTRL_RWC is present. If probe successfully
enables wakeup, the attached source otherwise survives ordinary driver
unbind because the controller device itself remains registered.
This issue was identified during our ongoing static-analysis research while
reviewing kernel code. The patches and explanations were prepared with LLM
assistance.
Compile-tested only; no hardware runtime testing was performed.
Myeonghun Pak (3):
usb: ehci-platform: Disable controller wakeup on removal
usb: ohci-platform: Disable controller wakeup on removal
usb: ohci-exynos: Disable controller wakeup on removal
drivers/usb/host/ehci-platform.c | 1 +
drivers/usb/host/ohci-exynos.c | 1 +
drivers/usb/host/ohci-platform.c | 1 +
3 files changed, 3 insertions(+)
base-commit: fd73f4a6659897191fa0d40695fe370925dd3780
next reply other threads:[~2026-09-13 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 22:37 Myeonghun Pak [this message]
2026-09-13 22:37 ` [PATCH 3/3] usb: ohci-exynos: Disable controller wakeup on removal Myeonghun Pak
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=20260913223732.92882-1-mhun512@gmail.com \
--to=mhun512@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=stern@rowland.harvard.edu \
/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