From: Vinod Koul <vkoul@kernel.org>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Jun Li <jun.li@nxp.com>,
Xu Yang <xu.yang_2@oss.nxp.com>
Cc: linux-phy@lists.infradead.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Felix Gu <ustc.gu@gmail.com>,
stable@vger.kernel.org, Xu Yang <xu.yang_2@nxp.com>
Subject: Re: [PATCH v8 0/6] phy: fsl-imx8mq-usb: few improvements
Date: Thu, 06 Aug 2026 21:56:17 +0530 [thread overview]
Message-ID: <178603357786.674490.1895923542917045365.b4-ty@kernel.org> (raw)
In-Reply-To: <20260731-imx8mp-usb-phy-improvement-v8-0-2ec8d6b3854d@nxp.com>
On Fri, 31 Jul 2026 16:11:18 +0800, Xu Yang wrote:
> Patch #1 fix Type-C switch resource leak if probe() fails.
> Patch #3 add runtime PM support to avoid register access issue if the
> USB controller enters into runtime suspended state, in this state
> accessing USB PHY register may lack some resources. This will also
> avoid regulator leak if power_on() fails.
> Patch #4 add debug control register regmap
> Patch #5 add imx8mq_usb_phy_drvdata drvdata for better extension
> Patch #6 correct i.MX8MP USB runtime wakeup issue after introduce runtime
> PM support.
>
> [...]
Applied, thanks!
[1/6] phy: fsl-imx8mq-usb: fix typec switch leak on probe error path
commit: 87a1805b1c346b092c34f96f3806f207792910e1
[2/6] phy: fsl-imx8mq-usb: set usb phy to be wakeup capable
commit: 2602012b8c625e63493647356d7290ee7c8fef2b
[3/6] phy: fsl-imx8mq-usb: add runtime PM support
commit: 56eec5d9665cebe580d41cdf2ea7abb52d23e122
[4/6] phy: fsl-imx8mq-usb: add control register regmap
commit: 01e9e84a43a1b4e9f67b5bd36be3d127d773a223
[5/6] phy: fsl-imx8mq-usb: introduce per-variant driver data structure
commit: 2d9dcffd5d3995ba04feeeebe800cbf1c0d4bbbe
[6/6] phy: fsl-imx8mq-usb: keep PHY power domain runtime always-on for i.MX8MP
commit: ee9e2b39ea4890f804b0c75c8a40a0f68ecd8d0a
Best regards,
--
~Vinod
prev parent reply other threads:[~2026-08-06 16:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 8:11 [PATCH v8 0/6] phy: fsl-imx8mq-usb: few improvements Xu Yang
2026-07-31 8:11 ` [PATCH v8 1/6] phy: fsl-imx8mq-usb: fix typec switch leak on probe error path Xu Yang
2026-07-31 8:11 ` [PATCH v8 2/6] phy: fsl-imx8mq-usb: set usb phy to be wakeup capable Xu Yang
2026-07-31 8:11 ` [PATCH v8 3/6] phy: fsl-imx8mq-usb: add runtime PM support Xu Yang
2026-07-31 14:42 ` Frank Li
2026-08-04 10:41 ` Xu Yang
2026-08-04 15:08 ` Frank Li
2026-07-31 8:11 ` [PATCH v8 4/6] phy: fsl-imx8mq-usb: add control register regmap Xu Yang
2026-07-31 8:11 ` [PATCH v8 5/6] phy: fsl-imx8mq-usb: introduce per-variant driver data structure Xu Yang
2026-07-31 8:11 ` [PATCH v8 6/6] phy: fsl-imx8mq-usb: keep PHY power domain runtime always-on for i.MX8MP Xu Yang
2026-07-31 14:44 ` Frank Li
2026-08-06 16:26 ` Vinod Koul [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=178603357786.674490.1895923542917045365.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=jun.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=s.hauer@pengutronix.de \
--cc=stable@vger.kernel.org \
--cc=ustc.gu@gmail.com \
--cc=xu.yang_2@nxp.com \
--cc=xu.yang_2@oss.nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox