[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250624040922.GA1077353@google.com>
Date: Tue, 24 Jun 2025 12:09:22 +0800
From: Chen-Yu Tsai <wenst@...omium.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Cc: linux-mediatek@...ts.infradead.org, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, matthias.bgg@...il.com, weiyi.lu@...iatek.com,
tinghan.shen@...iatek.com, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
kernel@...labora.com
Subject: Re: [PATCH v1 1/2] arm64: dts: mediatek: mt8195: Add subsys clks for
PCIe power domains
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@...labora.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@...labora.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@...195_POWER_DOMAIN_CAM_MRAW {
> > >
> > > power-domain@...195_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@...195_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
> > >
> > >
>
Powered by blists - more mailing lists