From: "Guido Günther" <agx@sigxcpu.org>
To: Kishon Vijay Abraham I <kishon@ti.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Robert Chiras <robert.chiras@nxp.com>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Liu Ying <victor.liu@nxp.com>
Subject: [PATCH v5 0/2] phy: fsl-imx8-mipi-dphy: Hook into runtime pm
Date: Fri, 9 Apr 2021 13:40:19 +0200 [thread overview]
Message-ID: <cover.1617968250.git.agx@sigxcpu.org> (raw)
This allows us to shut down the mipi power domain on the imx8. The alternative
would be to drop the dphy from the mipi power domain in the SOCs device tree
and only have the DSI host controller visible there but since the PD is mostly
about the PHY that would defeat it's purpose.
This allows to shut off the power domain when blanking the LCD panel:
pm_genpd_summary before:
domain status slaves
/device runtime status
----------------------------------------------------------------------
mipi on
/devices/platform/soc@0/soc@0:bus@30800000/30a00300.dphy unsupported
/devices/platform/soc@0/soc@0:bus@30800000/30a00000.mipi_dsi suspended
after:
mipi off-0
/devices/platform/soc@0/soc@0:bus@30800000/30a00300.dphy suspended
/devices/platform/soc@0/soc@0:bus@30800000/30a00000.mipi_dsi suspended
Changes from v1:
- Tweak commit message slightly
Changes from v2:
- As per review comment by Lucas Stach
https://lore.kernel.org/linux-arm-kernel/ee22b072e0abe07559a3e6a63ccf6ece064a46cb.camel@pengutronix.de/
Check for pm_runtime_get_sync failure
Changes from v3:
- As per review comment by Liu Ying
https://lore.kernel.org/linux-arm-kernel/424af315b677934fe6a91cee5a0a7aee058245a9.camel@nxp.com/
https://lore.kernel.org/linux-arm-kernel/a98f7531b9d0293d3c89174446f742d4199cb27c.camel@nxp.com/
- Use phy layers runtime pm
- simplify mixel_dphy_remove
Chanes from v4:
- As per review comment by Liu Ying
https://lore.kernel.org/linux-arm-kernel/daef1299e43f0372a95c149b979441f8083f4b15.camel@nxp.com/
- Disable after probe errors
- core: increment device usage count on .configure as well
Guido Günther (2):
phy: core: Use runtime pm during configure too
phy: fsl-imx8-mipi-dphy: Hook into runtime pm
drivers/phy/freescale/phy-fsl-imx8-mipi-dphy.c | 13 +++++++++++++
drivers/phy/phy-core.c | 6 ++++++
2 files changed, 19 insertions(+)
--
2.30.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-04-09 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 11:40 Guido Günther [this message]
2021-04-09 11:40 ` [PATCH v5 1/2] phy: core: Use runtime pm during configure too Guido Günther
2021-04-12 8:40 ` Liu Ying
2021-04-12 9:41 ` Guido Günther
2021-04-09 11:40 ` [PATCH v5 2/2] phy: fsl-imx8-mipi-dphy: Hook into runtime pm Guido Günther
2021-04-12 9:11 ` Liu Ying
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=cover.1617968250.git.agx@sigxcpu.org \
--to=agx@sigxcpu.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.chiras@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=sam@ravnborg.org \
--cc=shawnguo@kernel.org \
--cc=victor.liu@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;
as well as URLs for NNTP newsgroup(s).