From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Chunfeng Yun <chunfeng.yun@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Chun-Jie Chen <chun-jie.chen@mediatek.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] soc: mediatek: Add support always on flag
Date: Thu, 11 Nov 2021 14:56:19 +0100 [thread overview]
Message-ID: <e6ebf764-b94a-7b77-df17-1cb8e4b14635@collabora.com> (raw)
In-Reply-To: <20211102072058.4107-1-chunfeng.yun@mediatek.com>
Il 02/11/21 08:20, Chunfeng Yun ha scritto:
> There is a t-phy shared by PCIe and USB3 on mt8195, if the t-phy is
> used by PCIe, when power off its mtcmos, need software reset it
> (workaround way, usually hardware do it, but has an issue on mt8195),
> but it has side effect to USB2 phy(works with USB3 phy to support
> USB3.2 Gen1), so add support GENPD_FLAG_ALWAYS_ON flag, and make its
> power always on;
> Another reason is that USB3.2 Gen1/2 need keep power always on when
> support runtime-pm due to hardware limitation until now;
>
> Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
> ---
> drivers/soc/mediatek/mt8195-pm-domains.h | 2 +-
> drivers/soc/mediatek/mtk-pm-domains.c | 2 ++
> drivers/soc/mediatek/mtk-pm-domains.h | 1 +
> 3 files changed, 4 insertions(+), 1 deletion(-)
>
Hello Chunfeng,
what are are the side effects on the USB2 PHY? Can you please expand?
Also, wouldn't it be possible to also reset the USB2 PHY when resetting the t-phy
in order to get it back up and running?
Moreover, as for the USB3.2 hardware limitation... I would say that this is more
like something that has to be accounted for in the USB driver, instead of the PM
domains driver... unless there's some reason that stops you from doing that?
Thanks,
- Angelo
next prev parent reply other threads:[~2021-11-11 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 7:20 Chunfeng Yun
2021-11-11 13:56 ` AngeloGioacchino Del Regno [this message]
2021-11-24 6:38 ` Chunfeng Yun
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=e6ebf764-b94a-7b77-df17-1cb8e4b14635@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=chun-jie.chen@mediatek.com \
--cc=chunfeng.yun@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.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
all inboxes | Powered by JetHome®