From: bintian.wang@huawei.com (Bintian)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/5] arm64,hi6220: Enable Hisilicon Hi6220 SoC
Date: Thu, 7 May 2015 21:06:16 +0800 [thread overview]
Message-ID: <554B6348.3000200@huawei.com> (raw)
In-Reply-To: <20150507125752.GE22115@arm.com>
Hello Will,
On 2015/5/7 20:57, Will Deacon wrote:
> On Thu, May 07, 2015 at 01:01:47PM +0100, Bintian wrote:
>> On 2015/5/7 19:25, Will Deacon wrote:
>>> On Thu, May 07, 2015 at 10:29:03AM +0100, Bintian wrote:
>>>> Hikey is a low cost board, I think it doesn't have an automatic thermal
>>>> cut out; I always use HiKey to test my patch, in the normal case,
>>>> temperature is not a problem.
>>>
>>> I don't see why the cost has anything to do with this issue; any money I
>>> save on the board will quickly be re-invested in my increased insurance
>>> premium.
>>>
>>> All I think we need is for secure software to keep an eye on the temperature
>>> and hit the power controller if it goes over some `fatal' threshold.
>>> Ideally, you'd be able to use a secure interrupt for this, but I suspect
>>> that you don't have the right hardware features for that (please correct me
>>> if I'm wrong). An alternative would be to hang something off a secure timer
>>> and get the firmware to check the board temperature on some low-frequency
>>> periodic tick.
>> If there is exception occurred on A core, there are two methods to
>> handle it:
>> (1) Delay for a period of time, watchdog will trigger the system reset.
>> (2) If the temperature is over 105 degree, the CPU will trigger reset(I
>> guess it's chip level).
>
> Aha, so now you're saying that there *is* a hardware shut-off at 105
> degrees, regardless of what the kernel is doing?
Yes!
> If that's the case, then
> we're fine and the current patches make sense in isolation.
Thank you very much and I need your ack in next version :)
I am preparing the next version and will send out soon.
Thanks,
Bintian
>
> Cheers,
>
> Will
>
> .
>
next prev parent reply other threads:[~2015-05-07 13:06 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 12:06 [PATCH v4 0/5] arm64,hi6220: Enable Hisilicon Hi6220 SoC Bintian Wang
2015-05-05 12:06 ` [PATCH v4 1/5] arm64: Enable Hisilicon ARMv8 SoC family in Kconfig and defconfig Bintian Wang
2015-05-05 12:06 ` [PATCH v4 2/5] arm64: hi6220: Document devicetree bindings for Hisilicon hi6220 SoC Bintian Wang
2015-05-15 0:27 ` Stephen Boyd
2015-05-15 1:31 ` Bintian
2015-05-05 12:06 ` [PATCH v4 3/5] clk: hi6220: Document devicetree bindings for hi6220 clock Bintian Wang
2015-05-15 0:26 ` Stephen Boyd
2015-05-05 12:06 ` [PATCH v4 4/5] clk: hi6220: Clock driver support for Hisilicon hi6220 SoC Bintian Wang
2015-05-15 0:25 ` Stephen Boyd
2015-05-15 7:42 ` Bintian
2015-05-15 19:30 ` Stephen Boyd
2015-05-16 2:54 ` Brent Wang
2015-05-19 20:35 ` Stephen Boyd
2015-05-20 0:52 ` Bintian
2015-05-05 12:06 ` [PATCH v4 5/5] arm64: dts: Add dts files for Hisilicon Hi6220 SoC Bintian Wang
2015-05-05 17:13 ` Mark Rutland
2015-05-06 3:16 ` Bintian
2015-05-06 3:51 ` Leo Yan
2015-05-06 9:20 ` Mark Rutland
2015-05-06 11:17 ` Leo Yan
2015-05-06 6:50 ` Bintian
2015-05-06 9:30 ` Mark Rutland
2015-05-06 10:36 ` Bintian
2015-05-06 10:55 ` Mark Rutland
2015-05-06 15:31 ` Brent Wang
2015-05-06 15:44 ` Mark Rutland
2015-05-06 16:03 ` Brent Wang
2015-05-06 16:23 ` Mark Rutland
2015-05-06 17:15 ` Brent Wang
2015-05-07 7:24 ` Bintian
2015-05-13 7:12 ` Bintian Wang
2015-05-13 7:30 ` Bintian
2015-05-06 10:38 ` Haojian Zhuang
2015-05-06 11:01 ` Mark Rutland
2015-05-05 13:45 ` [PATCH v4 0/5] arm64,hi6220: Enable " Haojian Zhuang
2015-05-05 23:46 ` Tyler Baker
2015-05-06 10:46 ` Bintian
2015-05-07 9:02 ` Will Deacon
2015-05-07 9:29 ` Bintian
2015-05-07 11:25 ` Will Deacon
2015-05-07 11:55 ` Leo Yan
2015-05-07 12:01 ` Bintian
2015-05-07 12:57 ` Will Deacon
2015-05-07 13:06 ` Bintian [this message]
2015-05-07 9:33 ` Haojian Zhuang
2015-05-07 10:44 ` Jorge Ramirez-Ortiz
2015-05-13 7:33 ` Bintian
2015-05-13 9:16 ` Will Deacon
2015-05-13 9:19 ` Arnd Bergmann
2015-05-13 10:17 ` Bintian
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=554B6348.3000200@huawei.com \
--to=bintian.wang@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).