From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: Macpaul Lin <macpaul.lin@mediatek.com>,
Chunfeng Yun <chunfeng.yun@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, kernel@collabora.com,
Chen-Yu Tsai <wenst@chromium.org>,
Bear Wang <bear.wang@mediatek.com>,
Pablo Sun <pablo.sun@mediatek.com>
Subject: Re: Probe failure of usb controller @11290000 on MT8195 after next-20231221
Date: Mon, 22 Jul 2024 10:53:38 -0400 [thread overview]
Message-ID: <fab8e144-e5ef-4ce8-a74a-89024cd95100@notapiano> (raw)
In-Reply-To: <9f12777b-b8b6-4d34-b336-7637e551b552@collabora.com>
On Mon, Jul 15, 2024 at 02:04:54PM +0200, AngeloGioacchino Del Regno wrote:
[..]
> Besides, I also noticed that the CLK_APMIXED_PLL_SSUSB26M is missing from u2port1
> and the reason why it works is because other u3phy0 should be enabling that before
> u3phy1 inits and/or before the USB controller using U3P1 tries to initialize, so
> while you're at it ... if you can please also add that to the u3p1, I appreciate.
>
> u2port1: usb-phy@0 {
> reg = <0x0 0x700>;
> clocks = <&apmixedsys CLK_APMIXED_PLL_SSUSB26M>,
> <&topckgen CLK_TOP_SSUSB_PHY_P1_REF>;
> clock-names = "ref", "da_ref";
> #phy-cells = <1>;
> };
I'm not familiar with the clock topology on MT8195, but I noticed the
CLK_APMIXED_PLL_SSUSB26M clock is currently only present in the USB3 phy nodes:
u3port1 and u3port0. You're suggesting to add it to a USB2 phy node here. Is it
needed by all USB2 phy nodes (u2port0, u2port1, u2port2, u2port3) then?
Thanks,
Nícolas
next prev parent reply other threads:[~2024-07-22 14:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 18:36 Probe failure of usb controller @11290000 on MT8195 after next-20231221 Nícolas F. R. A. Prado
2024-01-19 9:12 ` AngeloGioacchino Del Regno
2024-07-10 19:15 ` Nícolas F. R. A. Prado
2024-07-11 4:13 ` Macpaul Lin
2024-07-11 9:21 ` AngeloGioacchino Del Regno
2024-07-11 16:33 ` Nícolas F. R. A. Prado
2024-07-12 8:12 ` AngeloGioacchino Del Regno
2024-07-12 15:58 ` Nícolas F. R. A. Prado
2024-07-15 12:04 ` AngeloGioacchino Del Regno
2024-07-15 14:00 ` Nícolas F. R. A. Prado
2024-07-22 14:53 ` Nícolas F. R. A. Prado [this message]
2024-07-11 9:14 ` AngeloGioacchino Del Regno
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=fab8e144-e5ef-4ce8-a74a-89024cd95100@notapiano \
--to=nfraprado@collabora.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bear.wang@mediatek.com \
--cc=chunfeng.yun@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=macpaul.lin@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=pablo.sun@mediatek.com \
--cc=wenst@chromium.org \
/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