From: Li Jun <jun.li@nxp.com>
To: shawnguo@kernel.org
Cc: l.stach@pengutronix.de, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
aford173@gmail.com, tharvey@gateworks.com,
frieder.schrempf@kontron.de, marex@denx.de,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
xu.yang_2@nxp.com, jun.li@nxp.com
Subject: [PATCH 0/4] Split usb otg1/2 power domain from hsio for imx8mm/n
Date: Mon, 26 Sep 2022 19:45:31 +0800 [thread overview]
Message-ID: <1664192735-14313-1-git-send-email-jun.li@nxp.com> (raw)
Actually otg1/2 power domain is for usb phy, which is required
to be powered up for usb remote up(e.g usb runtime suspended),
this patch set is to split the otg1/2 power domain from hsio,
so hsio power domain can be off but otg1/2 is on for runtime
PM.
Li Jun (4):
arm64: dts: imx8mm: remove otg1/2 power domain dependency on hsio
arm64: dts: imx8mm: correct usb power domains
arm64: dts: imx8mn: remove otg1 power domain dependency on hsio
arm64: dts: imx8mn: Correct the usb power domain
arch/arm64/boot/dts/freescale/imx8mm.dtsi | 8 ++++----
arch/arm64/boot/dts/freescale/imx8mn.dtsi | 4 ++--
2 files changed, 6 insertions(+), 6 deletions(-)
--
2.34.1
next reply other threads:[~2022-09-26 13:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 11:45 Li Jun [this message]
2022-09-26 11:45 ` [PATCH 1/4] arm64: dts: imx8mm: remove otg1/2 power domain dependency on hsio Li Jun
2022-09-26 11:45 ` [PATCH 2/4] arm64: dts: imx8mm: correct usb power domains Li Jun
2022-09-26 11:45 ` [PATCH 3/4] arm64: dts: imx8mn: remove otg1 power domain dependency on hsio Li Jun
2022-09-26 11:45 ` [PATCH 4/4] arm64: dts: imx8mn: Correct the usb power domain Li Jun
2022-10-24 1:37 ` [PATCH 0/4] Split usb otg1/2 power domain from hsio for imx8mm/n Shawn Guo
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=1664192735-14313-1-git-send-email-jun.li@nxp.com \
--to=jun.li@nxp.com \
--cc=aford173@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=marex@denx.de \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tharvey@gateworks.com \
--cc=xu.yang_2@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).