From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Brugger Subject: Re: [PATCH v1 1/2] arm64: dts: mt7622: add some misc device nodes Date: Tue, 17 Jul 2018 09:55:43 +0200 Message-ID: <864955d5-26c4-a5f3-ec1a-420acba50880@gmail.com> References: <2ff39c40ef6bc3054667e63c785a1d28527b5ddf.1531753039.git.ryder.lee@mediatek.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <2ff39c40ef6bc3054667e63c785a1d28527b5ddf.1531753039.git.ryder.lee@mediatek.com> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Ryder Lee , Rob Herring , Will Deacon Cc: Sean Wang , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org List-Id: devicetree@vger.kernel.org Hi Ryder, On 16/07/18 16:59, Ryder Lee wrote: > Add some misc nodes support - timer and ARM CCI-400. > > Signed-off-by: Ryder Lee > --- > arch/arm64/boot/dts/mediatek/mt7622.dtsi | 36 ++++++++++++++++++++++++++++++++ > 1 file changed, 36 insertions(+) > > diff --git a/arch/arm64/boot/dts/mediatek/mt7622.dtsi b/arch/arm64/boot/dts/mediatek/mt7622.dtsi > index 9213c96..8cdec52 100644 > --- a/arch/arm64/boot/dts/mediatek/mt7622.dtsi > +++ b/arch/arm64/boot/dts/mediatek/mt7622.dtsi > @@ -217,6 +217,16 @@ > #reset-cells = <1>; > }; > > + timer: timer@10004000 { > + compatible = "mediatek,mt7622-timer", > + "mediatek,mt6577-timer"; > + reg = <0 0x10004000 0 0x80>; > + interrupts = ; > + clocks = <&infracfg CLK_INFRA_APXGPT_PD>, > + <&topckgen CLK_TOP_RTC>; > + clock-names = "system-clk", "rtc-clk"; > + }; > + > scpsys: scpsys@10006000 { > compatible = "mediatek,mt7622-scpsys", > "syscon"; > @@ -317,6 +327,32 @@ > <0 0x10360000 0 0x2000>; > }; > > + cci: cci@10390000 { > + compatible = "arm,cci-400"; > + #address-cells = <1>; > + #size-cells = <1>; > + reg = <0 0x10390000 0 0x1000>; > + ranges = <0 0 0x10390000 0x10000>; >>From my understanding of the binding description ranges should hold child address, parent address and size of the region in the child address space. I can see in arch/arm64 two different variants using 4 ranges values (like here) and using three values. @Rob + Will what is the preferred way to describe this? > + > + cci_control0: slave-if@1000 { > + compatible = "arm,cci-400-ctrl-if"; > + interface-type = "ace-lite"; > + reg = <0x1000 0x1000>; > + }; Don't we need to add phandles to the cci-control-port property in the cpu nodes? Regards, Matthias > + > + cci_control1: slave-if@4000 { > + compatible = "arm,cci-400-ctrl-if"; > + interface-type = "ace"; > + reg = <0x4000 0x1000>; > + }; > + > + cci_control2: slave-if@5000 { > + compatible = "arm,cci-400-ctrl-if"; > + interface-type = "ace"; > + reg = <0x5000 0x1000>; > + }; > + }; > + > auxadc: adc@11001000 { > compatible = "mediatek,mt7622-auxadc"; > reg = <0 0x11001000 0 0x1000>; >