Re: [PATCH v5 phy-next 10/27] scsi: ufs: qcom: keep parallel track of PHY power state
From: Vladimir Oltean <vladimir.oltean@nxp.com>
Date: 2026-03-25 11:57:40
Also in:
dri-devel, linux-arm-kernel, linux-arm-msm, linux-can, linux-gpio, linux-ide, linux-media, linux-pci, linux-phy, linux-renesas-soc, linux-riscv, linux-rockchip, linux-samsung-soc, linux-scsi, linux-sunxi, linux-tegra, linux-usb, lkml, spacemit
On Wed, Mar 25, 2026 at 05:21:14PM +0530, Manivannan Sadhasivam wrote:
I believe I added the power_count check for phy_exit(). But since that got moved, the check becomes no longer necessary.
FYI, the power_count keeps track of the balance of phy_power_on() and phy_power_off() calls, whereas it is the init_count keeps track of phy_init() and phy_exit() calls. They are only related to the extent that you must respect the phy_init() -> phy_power_on() -> phy_power_off() -> phy_exit() sequence. But in any case, both should be considered PHY-internal fields. The "Order of API calls" section from Documentation/driver-api/phy/phy.rst mentions the order that I just described above, and consumers should just ensure they follow that.