From: Pengpeng Hou <hppiscas@163.com>
To: Bin Liu <b-liu@ti.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Pengpeng Hou <hppiscas@163.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Felipe Balbi <balbi@ti.com>,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org, Tony Lindgren <tony@atomide.com>
Subject: [PATCH 0/3] usb: musb: omap2430: propagate PHY setup errors
Date: Sun, 6 Sep 2026 11:41:46 +0800 [thread overview]
Message-ID: <20260906034149.85550-1-hppiscas@163.com> (raw)
The OMAP2430 glue ignores generic PHY initialization and power-on
failures during initial setup, runtime resume and system resume. The
callers can therefore access glue registers or publish resumed state
without a usable PHY.
Keep the three lifecycle transitions separate so each patch has one
failure state and one introducing commit. Each power-on failure exits a
PHY that was initialized by the same transition.
The issues were found by our static-analysis tool and manually reviewed.
Pengpeng Hou (3):
usb: musb: omap2430: Propagate PHY errors from init
usb: musb: omap2430: Propagate PHY errors from runtime resume
usb: musb: omap2430: Propagate PHY errors from system resume
drivers/usb/musb/omap2430.c | 35 +++++++++++++++++++++++++++++------
1 file changed, 29 insertions(+), 6 deletions(-)
--
2.50.1 (Apple Git-155)
next reply other threads:[~2026-09-06 3:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 3:41 Pengpeng Hou [this message]
2026-09-10 12:22 ` [PATCH 0/3] usb: musb: omap2430: propagate PHY setup errors Greg Kroah-Hartman
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=20260906034149.85550-1-hppiscas@163.com \
--to=hppiscas@163.com \
--cc=b-liu@ti.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.