[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <76146c97-d4ff-7058-0ca7-6b2baa3bf5fe@arm.com>
Date: Thu, 23 Feb 2017 10:56:11 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: Chunyan Zhang <zhang.lyra@...il.com>
Cc: Mathieu Poirier <mathieu.poirier@...aro.org>,
Sudeep Holla <sudeep.holla@....com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Greg KH <gregkh@...uxfoundation.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Arnd Bergmann <arnd@...db.de>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Orson Zhai <orson.zhai@...eadtrum.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH V2 1/3] arm64: dts: Add basic DT to support Spreadtrum's
SP9860G
Hi Chunyan,
On 23/02/17 06:20, Chunyan Zhang wrote:
[...]
>>> I noticed Juno use the 2), would you suggest that way?
>>
>> It is better to describe the HW component themselves rather than where
>> they are in the topology - the address of the component will make sure
>> the names are unique. So just the component type (etm, funnel,
>> replicator, ....) and the address they are located at.
>>
>
> OK. And to avoid making other person confused in the future, is it
> better to revise juno-base.dtsi according to this convention?
>
Yes, it was noticed by Olof and should be now fixed for v4.11(already
queued). You can check linux-next if you want to have a look before it
gets merged.
--
Regards,
Sudeep
Powered by blists - more mailing lists