From: Chen-Yu Tsai <wenst@chromium.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: linux-mediatek@lists.infradead.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, matthias.bgg@gmail.com,
weiyi.lu@mediatek.com, tinghan.shen@mediatek.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH v1 1/2] arm64: dts: mediatek: mt8195: Add subsys clks for PCIe power domains
Date: Tue, 24 Jun 2025 12:09:22 +0800 [thread overview]
Message-ID: <20250624040922.GA1077353@google.com> (raw)
In-Reply-To: <33847b76-11b5-4233-a5e6-9f8fd3c691a2@collabora.com>
On Wed, Apr 02, 2025 at 12:07:16PM +0200, AngeloGioacchino Del Regno wrote:
> Il 02/04/25 11:34, Chen-Yu Tsai ha scritto:
> > On Wed, Apr 2, 2025 at 5:10 PM AngeloGioacchino Del Regno
> > <angelogioacchino.delregno@collabora.com> wrote:
> > >
> > > The PCIe MAC needs the sram to be powered on for internal IP
> > > access and it has always worked before because the bootloader
> > > on Chromebooks was leaving the PCIe PERI_AO MEM clocks on
> > > before booting the kernel.
> > > Add the SRAM (mem) clock as a subsystem clock on the PCIe MAC
> > > P0 and P1 to correctly describe the hardware and to avoid any
> > > issue with bootloaders behaving differently.
> > >
> > > Fixes: 2b515194bf0c ("arm64: dts: mt8195: Add power domains controller")
> > > Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> > > ---
> > > arch/arm64/boot/dts/mediatek/mt8195.dtsi | 4 ++++
> > > 1 file changed, 4 insertions(+)
> > >
> > > diff --git a/arch/arm64/boot/dts/mediatek/mt8195.dtsi b/arch/arm64/boot/dts/mediatek/mt8195.dtsi
> > > index b33726da900b..0cb96cba727a 100644
> > > --- a/arch/arm64/boot/dts/mediatek/mt8195.dtsi
> > > +++ b/arch/arm64/boot/dts/mediatek/mt8195.dtsi
> > > @@ -792,12 +792,16 @@ power-domain@MT8195_POWER_DOMAIN_CAM_MRAW {
> > >
> > > power-domain@MT8195_POWER_DOMAIN_PCIE_MAC_P0 {
> > > reg = <MT8195_POWER_DOMAIN_PCIE_MAC_P0>;
> > > + clocks = <&pericfg_ao CLK_PERI_AO_PCIE_P0_MEM>;
> > > + clock-names = "ss-pextp0-mem";
> >
> > Doesn't the PCIe host controller already reference this clock?
> >
> > > mediatek,infracfg = <&infracfg_ao>;
> > > #power-domain-cells = <0>;
> > > };
> > >
> > > power-domain@MT8195_POWER_DOMAIN_PCIE_MAC_P1 {
> > > reg = <MT8195_POWER_DOMAIN_PCIE_MAC_P1>;
> > > + clocks = <&pericfg_ao CLK_PERI_AO_PCIE_P1_MEM>;
> > > + clock-names = "ss-pextp1-mem";
> >
> > Not this one though, since:
> >
> > /* Designer has connect pcie1 with peri_mem_p0 clock */
> > <&pericfg_ao CLK_PERI_AO_PCIE_P0_MEM>;
> >
>
> I'm not sure what this comment refers to - as in, whether this is referring
> to the board designer or to the SoC//IP designer...
When MediaTek says "designer" they are referring to the hardware designer,
in this case I believe it would be the SoC-level hardware designer /
integrator.
> ...but if MediaTek can clarify, I'd be happy :-)
>
> Cheers,
> Angelo
>
> >
> > ChenYu
> >
> > > mediatek,infracfg = <&infracfg_ao>;
> > > #power-domain-cells = <0>;
> > > };
> > > --
> > > 2.48.1
> > >
> > >
>
next prev parent reply other threads:[~2025-06-24 4:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 9:06 [PATCH v1 0/2] arm64: dts: mediatek: mt8195: Power domains fixes AngeloGioacchino Del Regno
2025-04-02 9:06 ` [PATCH v1 1/2] arm64: dts: mediatek: mt8195: Add subsys clks for PCIe power domains AngeloGioacchino Del Regno
2025-04-02 9:34 ` Chen-Yu Tsai
2025-04-02 10:07 ` AngeloGioacchino Del Regno
2025-06-24 4:09 ` Chen-Yu Tsai [this message]
2025-04-02 9:06 ` [PATCH v1 2/2] arm64: dts: mediatek: mt8195: Reparent vdec1/2 and venc1 " AngeloGioacchino Del Regno
2025-04-02 9:24 ` Chen-Yu Tsai
2025-04-14 9:53 ` (subset) [PATCH v1 0/2] arm64: dts: mediatek: mt8195: Power domains fixes 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=20250624040922.GA1077353@google.com \
--to=wenst@chromium.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=tinghan.shen@mediatek.com \
--cc=weiyi.lu@mediatek.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 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.