From: Will Deacon <will.deacon@arm.com>
To: Bintian Wang <bintian.wang@huawei.com>
Cc: Mark Rutland <Mark.Rutland@arm.com>,
"dan.zhao@hisilicon.com" <dan.zhao@hisilicon.com>,
"btw@mail.itp.ac.cn" <btw@mail.itp.ac.cn>,
Catalin Marinas <Catalin.Marinas@arm.com>,
"wangbinghui@hisilicon.com" <wangbinghui@hisilicon.com>,
"tyler.baker@linaro.org" <tyler.baker@linaro.org>,
"huxinwei@huawei.com" <huxinwei@huawei.com>,
"haojian.zhuang@linaro.org" <haojian.zhuang@linaro.org>,
"yanhaifeng@gmail.com" <yanhaifeng@gmail.com>,
"rob.herring@linaro.org" <rob.herring@linaro.org>,
"mturquette@linaro.org" <mturquette@linaro.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"khilman@kernel.org" <khilman@kernel.org>,
"victor.lixin@hisilicon.com" <victor.lixin@hisilicon.com>,
"xuwei5@hisilicon.com" <xuwei5@hisilicon.com>,
"jh80.chung@samsung.com" <jh80.chung@samsung.com>,
"sledge.yanwei@huawei.com" <sledge.yanwei@huawei.com>,
"kong.kongxinwei@hisilicon.com" <kong.kongxinwei@hisilicon.co>
Subject: Re: [PATCH v4 0/5] arm64,hi6220: Enable Hisilicon Hi6220 SoC
Date: Thu, 7 May 2015 10:02:11 +0100 [thread overview]
Message-ID: <20150507090210.GB22115@arm.com> (raw)
In-Reply-To: <1430827599-11560-1-git-send-email-bintian.wang@huawei.com>
Hi Bintian,
On Tue, May 05, 2015 at 01:06:34PM +0100, Bintian Wang wrote:
> Hi6220 is one mobile solution of Hisilicon, this patchset contains
> initial support for Hi6220 SoC and HiKey development board, which
> supports octal ARM Cortex A53 cores. Initial support is minimal and
> includes just the arch configuration, clock driver, device tree
> configuration.
>
> PSCI is enabled in device tree and there is no problem to boot all the
> octal cores, and the CPU hotplug is also working now, you can download
> and compile the latest firmware based on the following link to run this
> patch set:
> https://github.com/96boards/documentation/wiki/UEFI
>
> Changes v4:
> * Rebase to kernel 4.1-rc1
> * Delete "arm,cortex-a15-gic" from the gic node in dts
I gave these patches a go on top of -rc2 using the ATF and UEFI you link to
above.
The good news is that the thing booted and all the cores entered at EL2.
Thanks!
The bad news is that running hackbench quickly got the *heatsink*
temperature to 73 degress C and rising (measured with an infrared
thermometer).
So my question is, does this SoC have an automatic thermal cut out? Whilst
I'm all for merging enabling code into the kernel, if it really relies on
the kernel to stop it from catching fire, maybe it's not a great idea
putting these patches into people's hands just yet.
Will
next prev parent reply other threads:[~2015-05-07 9:02 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
[not found] ` <1430827599-11560-1-git-send-email-bintian.wang-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
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 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
[not found] ` <555B9E7B.9000809-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
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-13 7:33 ` Bintian
2015-05-13 9:16 ` Will Deacon
2015-05-13 9:19 ` Arnd Bergmann
2015-05-13 10:17 ` Bintian
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
[not found] ` <20150515002739.GF31753-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-05-15 1:31 ` Bintian
2015-05-05 23:46 ` [PATCH v4 0/5] arm64,hi6220: Enable Hisilicon Hi6220 SoC Tyler Baker
2015-05-06 10:46 ` Bintian
2015-05-07 9:02 ` Will Deacon [this message]
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
2015-05-07 9:33 ` Haojian Zhuang
2015-05-07 10:44 ` Jorge Ramirez-Ortiz
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=20150507090210.GB22115@arm.com \
--to=will.deacon@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=arnd@arndb.de \
--cc=bintian.wang@huawei.com \
--cc=btw@mail.itp.ac.cn \
--cc=dan.zhao@hisilicon.com \
--cc=haojian.zhuang@linaro.org \
--cc=huxinwei@huawei.com \
--cc=jh80.chung@samsung.com \
--cc=khilman@kernel.org \
--cc=kong.kongxinwei@hisilicon.co \
--cc=mturquette@linaro.org \
--cc=rob.herring@linaro.org \
--cc=sledge.yanwei@huawei.com \
--cc=tyler.baker@linaro.org \
--cc=victor.lixin@hisilicon.com \
--cc=wangbinghui@hisilicon.com \
--cc=xuwei5@hisilicon.com \
--cc=yanhaifeng@gmail.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).