[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1469785990.3012.35.camel@pengutronix.de>
Date: Fri, 29 Jul 2016 11:53:10 +0200
From: Philipp Zabel <p.zabel@...gutronix.de>
To: Bibby Hsieh <bibby.hsieh@...iatek.com>
Cc: Mark Rutland <mark.rutland@....com>, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mediatek@...ts.infradead.org,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Matthias Brugger <matthias.bgg@...il.com>,
Daniel Kurtz <djkurtz@...omium.org>,
Yingjoe Chen <yingjoe.chen@...iatek.com>,
Sascha Hauer <s.hauer@...gutronix.de>,
James Liao <jamesjj.liao@...iatek.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
YH Huang <yh.huang@...iatek.com>, CK Hu <ck.hu@...iatek.com>,
Yong Wu <yong.wu@...iatek.com>,
Eddie Huang <eddie.huang@...iatek.com>,
"dawei.chien@...iatek.com" <dawei.chien@...iatek.com>,
Chunfeng Yun <chunfeng.yun@...iatek.com>,
Junzhi Zhao <junzhi.zhao@...iatek.com>
Subject: Re: [PATCH v4] arm64: dts: mt8173: add mmsel clocks for 4K support
Hi Bibby,
Am Freitag, den 29.07.2016, 17:09 +0800 schrieb Bibby Hsieh:
> To support HDMI 4K resolution, mmsys need clcok
> mm_sel to be 400MHz.
>
> The board .dts file should override the clock rate
> property with the higher VENCPLL frequency the board
> supports HDMI 4K resolution.
>
> Signed-off-by: Bibby Hsieh <bibby.hsieh@...iatek.com>
> ---
> arch/arm64/boot/dts/mediatek/mt8173.dtsi | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> index 78529e4..93d4d17 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> @@ -690,6 +690,8 @@
> compatible = "mediatek,mt8173-mmsys", "syscon";
> reg = <0 0x14000000 0 0x1000>;
> power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
> + clocks = <&topckgen CLK_TOP_MM_SEL>;
> + clock-frequency = <400000000>;
This is unchanged compared to v3, I suggest to use assigned-clocks /
assigned-clock-rates properties instead.
best regards
Philipp
Powered by blists - more mailing lists