[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190320144907.GC8337@dragon>
Date: Wed, 20 Mar 2019 22:49:09 +0800
From: Shawn Guo <shawnguo@...nel.org>
To: Andy Tang <andy.tang@....com>
Cc: Daniel Lezcano <daniel.lezcano@...aro.org>,
"mark.rutland@....com" <mark.rutland@....com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Leo Li <leoyang.li@....com>,
"edubezval@...il.com" <edubezval@...il.com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"rui.zhang@...el.com" <rui.zhang@...el.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v2] arm64: dts: ls1088a: add one more thermal zone node
On Wed, Mar 20, 2019 at 08:44:18AM +0000, Andy Tang wrote:
> > > Sensor ID placement
> > > 1 DDR controller 1
> > > 2 DDR controller 2
> > > 3 DDR controller 3
> > > 4 core cluster 1
> > > 5 core cluster 2
> > > 6 core cluster 3
> > > 7 core cluster 4
> > >
> > > Apparently using CPU or CPU-cluster is not appropriate. Core-cluster is better.
> >
> > So using CPU is appropriate for me, less confusing, more consistent with other
> > platforms.
> What about core cluster? We can't name it cpu0, cpu1 etc I think.
Hmm, yes, that would be even more confusing. What about cpu-thermal-1,
cpu-thermal-2 ...?
Shawn
Powered by blists - more mailing lists