[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d7432483-7244-1c6e-cff7-ac56a67705a7@gmail.com>
Date: Fri, 16 Dec 2022 12:29:44 +0100
From: Matthias Brugger <matthias.bgg@...il.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>
Cc: robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
tinghan.shen@...iatek.com, weiyi.lu@...iatek.com,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: mediatek: mt8195: Use P1 clocks for PCIe1
controller
On 14/12/2022 14:11, AngeloGioacchino Del Regno wrote:
> Despite there being some flexibility regarding the P0/P1 connections,
> especially for TL and PERI, we must use P1 clocks on pcie1 otherwise
> we'll be dealing with unclocked access.
>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Seems my mail got lost somewhere:
Both patches applied, thanks!
> ---
> arch/arm64/boot/dts/mediatek/mt8195.dtsi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8195.dtsi b/arch/arm64/boot/dts/mediatek/mt8195.dtsi
> index 5d31536f4c48..e61944510b8e 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8195.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8195.dtsi
> @@ -1258,9 +1258,9 @@ pcie1: pcie@...f8000 {
>
> clocks = <&infracfg_ao CLK_INFRA_AO_PCIE_PL_P_250M_P1>,
> <&clk26m>,
> - <&infracfg_ao CLK_INFRA_AO_PCIE_TL_96M>,
> + <&infracfg_ao CLK_INFRA_AO_PCIE_P1_TL_96M>,
> <&clk26m>,
> - <&infracfg_ao CLK_INFRA_AO_PCIE_PERI_26M>,
> + <&infracfg_ao CLK_INFRA_AO_PCIE_P1_PERI_26M>,
> /* Designer has connect pcie1 with peri_mem_p0 clock */
> <&pericfg_ao CLK_PERI_AO_PCIE_P0_MEM>;
> clock-names = "pl_250m", "tl_26m", "tl_96m",
Powered by blists - more mailing lists