From: Vinod Koul <vkoul@kernel.org>
To: jonathanh@nvidia.com, thierry.reding@gmail.com, jckuo@nvidia.com,
kishon@kernel.org, Wayne Chang <waynec@nvidia.com>
Cc: linux-phy@lists.infradead.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH V3 1/1] phy: tegra: xusb: Use a bitmask for UTMI pad power state tracking
Date: Fri, 11 Apr 2025 17:40:14 +0530 [thread overview]
Message-ID: <174437341497.673813.4496801277326172956.b4-ty@kernel.org> (raw)
In-Reply-To: <20250408030905.990474-1-waynec@nvidia.com>
On Tue, 08 Apr 2025 11:09:05 +0800, Wayne Chang wrote:
> The current implementation uses bias_pad_enable as a reference count to
> manage the shared bias pad for all UTMI PHYs. However, during system
> suspension with connected USB devices, multiple power-down requests for
> the UTMI pad result in a mismatch in the reference count, which in turn
> produces warnings such as:
>
> [ 237.762967] WARNING: CPU: 10 PID: 1618 at tegra186_utmi_pad_power_down+0x160/0x170
> [ 237.763103] Call trace:
> [ 237.763104] tegra186_utmi_pad_power_down+0x160/0x170
> [ 237.763107] tegra186_utmi_phy_power_off+0x10/0x30
> [ 237.763110] phy_power_off+0x48/0x100
> [ 237.763113] tegra_xusb_enter_elpg+0x204/0x500
> [ 237.763119] tegra_xusb_suspend+0x48/0x140
> [ 237.763122] platform_pm_suspend+0x2c/0xb0
> [ 237.763125] dpm_run_callback.isra.0+0x20/0xa0
> [ 237.763127] __device_suspend+0x118/0x330
> [ 237.763129] dpm_suspend+0x10c/0x1f0
> [ 237.763130] dpm_suspend_start+0x88/0xb0
> [ 237.763132] suspend_devices_and_enter+0x120/0x500
> [ 237.763135] pm_suspend+0x1ec/0x270
>
> [...]
Applied, thanks!
[1/1] phy: tegra: xusb: Use a bitmask for UTMI pad power state tracking
commit: b47158fb42959c417ff2662075c0d46fb783d5d1
Best regards,
--
~Vinod
prev parent reply other threads:[~2025-04-11 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 3:09 [PATCH V3 1/1] phy: tegra: xusb: Use a bitmask for UTMI pad power state tracking Wayne Chang
2025-04-08 10:46 ` Jon Hunter
2025-04-11 12:10 ` 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=174437341497.673813.4496801277326172956.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=jckuo@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=waynec@nvidia.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