From: Shawn Guo <shawnguo@kernel.org>
To: Andy Tang <andy.tang@nxp.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Leo Li <leoyang.li@nxp.com>,
"edubezval@gmail.com" <edubezval@gmail.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"rui.zhang@intel.com" <rui.zhang@intel.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] arm64: dts: ls1088a: add one more thermal zone node
Date: Wed, 20 Mar 2019 22:49:09 +0800 [thread overview]
Message-ID: <20190320144907.GC8337@dragon> (raw)
In-Reply-To: <VI1PR04MB433351C20A9863EEF21A2504F3410@VI1PR04MB4333.eurprd04.prod.outlook.com>
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
next prev parent reply other threads:[~2019-03-20 14:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 3:21 [PATCH v2] arm64: dts: ls1088a: add one more thermal zone node Yuantian Tang
2019-03-04 6:21 ` Shawn Guo
2019-03-04 6:46 ` Andy Tang
2019-03-04 6:53 ` Shawn Guo
2019-03-07 9:14 ` Daniel Lezcano
2019-03-08 2:07 ` Andy Tang
2019-03-08 9:28 ` Daniel Lezcano
2019-03-08 9:57 ` Andy Tang
2019-03-20 8:18 ` Shawn Guo
2019-03-20 8:44 ` Andy Tang
2019-03-20 14:49 ` Shawn Guo [this message]
2019-03-21 1:05 ` Andy Tang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190320144907.GC8337@dragon \
--to=shawnguo@kernel.org \
--cc=andy.tang@nxp.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).