From: Jules Maselbas <jmaselbas@kalray.eu> To: linux-phy@lists.infradead.org Cc: linux-usb@vger.kernel.org, Kishon Vijay Abraham I <kishon@ti.com>, Vinod Koul <vkoul@kernel.org>, Ahmad Fatoum <a.fatoum@pengutronix.de>, Minas Harutyunyan <hminas@synopsys.com>, Amelie DELAUNAY <amelie.delaunay@foss.st.com>, Yann Sionneau <ysionneau@kalray.eu>, Michael Grzeschik <mgr@pengutronix.de>, Randy Dunlap <rdunlap@infradead.org>, Arnd Bergmann <arnd@arndb.de>, Jules Maselbas <jmaselbas@kalray.eu> Subject: [PATCH RESEND v3 3/3] phy: core: Warn when phy_power_on is called before phy_init Date: Thu, 7 Apr 2022 12:21:08 +0200 [thread overview] Message-ID: <20220407102108.24211-4-jmaselbas@kalray.eu> (raw) In-Reply-To: <20220407102108.24211-1-jmaselbas@kalray.eu> A warning when the order of phy operation is mixed up by drivers, this is an atempt to make the phy usage more uniform across (usb) drivers. Signed-off-by: Jules Maselbas <jmaselbas@kalray.eu> Cc: Ahmad Fatoum <a.fatoum@pengutronix.de> Cc: Amelie DELAUNAY <amelie.delaunay@foss.st.com> Cc: Minas Harutyunyan <hminas@synopsys.com> Cc: Kishon Vijay Abraham I <kishon@ti.com> --- drivers/phy/phy-core.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c index d11b517e283a..90f589563a60 100644 --- a/drivers/phy/phy-core.c +++ b/drivers/phy/phy-core.c @@ -253,6 +253,9 @@ int phy_init(struct phy *phy) ret = 0; /* Override possible ret == -ENOTSUPP */ mutex_lock(&phy->mutex); + if (phy->power_count > phy->init_count) + dev_warn(&phy->dev, "phy_power_on was called before phy_init\n"); + if (phy->init_count == 0 && phy->ops->init) { ret = phy->ops->init(phy); if (ret < 0) { -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Jules Maselbas <jmaselbas@kalray.eu> To: linux-phy@lists.infradead.org Cc: linux-usb@vger.kernel.org, Kishon Vijay Abraham I <kishon@ti.com>, Vinod Koul <vkoul@kernel.org>, Ahmad Fatoum <a.fatoum@pengutronix.de>, Minas Harutyunyan <hminas@synopsys.com>, Amelie DELAUNAY <amelie.delaunay@foss.st.com>, Yann Sionneau <ysionneau@kalray.eu>, Michael Grzeschik <mgr@pengutronix.de>, Randy Dunlap <rdunlap@infradead.org>, Arnd Bergmann <arnd@arndb.de>, Jules Maselbas <jmaselbas@kalray.eu> Subject: [PATCH RESEND v3 3/3] phy: core: Warn when phy_power_on is called before phy_init Date: Thu, 7 Apr 2022 12:21:08 +0200 [thread overview] Message-ID: <20220407102108.24211-4-jmaselbas@kalray.eu> (raw) In-Reply-To: <20220407102108.24211-1-jmaselbas@kalray.eu> A warning when the order of phy operation is mixed up by drivers, this is an atempt to make the phy usage more uniform across (usb) drivers. Signed-off-by: Jules Maselbas <jmaselbas@kalray.eu> Cc: Ahmad Fatoum <a.fatoum@pengutronix.de> Cc: Amelie DELAUNAY <amelie.delaunay@foss.st.com> Cc: Minas Harutyunyan <hminas@synopsys.com> Cc: Kishon Vijay Abraham I <kishon@ti.com> --- drivers/phy/phy-core.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c index d11b517e283a..90f589563a60 100644 --- a/drivers/phy/phy-core.c +++ b/drivers/phy/phy-core.c @@ -253,6 +253,9 @@ int phy_init(struct phy *phy) ret = 0; /* Override possible ret == -ENOTSUPP */ mutex_lock(&phy->mutex); + if (phy->power_count > phy->init_count) + dev_warn(&phy->dev, "phy_power_on was called before phy_init\n"); + if (phy->init_count == 0 && phy->ops->init) { ret = phy->ops->init(phy); if (ret < 0) { -- 2.17.1 -- linux-phy mailing list linux-phy@lists.infradead.org https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2022-04-07 10:21 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-07 10:21 [PATCH RESEND v3 0/3] Cleanup the call ordering of phy_init and phy_power_on Jules Maselbas 2022-04-07 10:21 ` Jules Maselbas 2022-04-07 10:21 ` [PATCH RESEND v3 1/3] phy: core: Add documentation of phy operation order Jules Maselbas 2022-04-07 10:21 ` Jules Maselbas 2022-04-07 10:21 ` [PATCH RESEND v3 2/3] phy: core: Update documentation syntax Jules Maselbas 2022-04-07 10:21 ` Jules Maselbas 2022-04-13 6:02 ` Vinod Koul 2022-04-13 6:02 ` Vinod Koul 2022-04-13 9:53 ` Jules Maselbas 2022-04-13 9:53 ` Jules Maselbas 2022-04-13 9:59 ` Vinod Koul 2022-04-13 9:59 ` Vinod Koul 2022-04-13 11:13 ` Jules Maselbas 2022-04-13 11:13 ` Jules Maselbas 2022-04-07 10:21 ` Jules Maselbas [this message] 2022-04-07 10:21 ` [PATCH RESEND v3 3/3] phy: core: Warn when phy_power_on is called before phy_init Jules Maselbas 2022-04-20 9:15 ` [PATCH RESEND v3 0/3] Cleanup the call ordering of phy_init and phy_power_on Vinod Koul 2022-04-20 9:15 ` Vinod Koul
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=20220407102108.24211-4-jmaselbas@kalray.eu \ --to=jmaselbas@kalray.eu \ --cc=a.fatoum@pengutronix.de \ --cc=amelie.delaunay@foss.st.com \ --cc=arnd@arndb.de \ --cc=hminas@synopsys.com \ --cc=kishon@ti.com \ --cc=linux-phy@lists.infradead.org \ --cc=linux-usb@vger.kernel.org \ --cc=mgr@pengutronix.de \ --cc=rdunlap@infradead.org \ --cc=vkoul@kernel.org \ --cc=ysionneau@kalray.eu \ /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: linkBe 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.