From: eddie.huang@mediatek.com (Eddie Huang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] arm64: dts: Add mediatek MT8173 SoC and evaluation board dts and Makefile
Date: Tue, 16 Dec 2014 16:46:55 +0800 [thread overview]
Message-ID: <1418719615.8392.17.camel@mtksdaap41> (raw)
In-Reply-To: <20141215125932.GF462@leverpostej>
Hi,
On Mon, 2014-12-15 at 12:59 +0000, Mark Rutland wrote:
> On Fri, Dec 12, 2014 at 08:08:25AM +0000, Eddie Huang wrote:
> > Hi Mark,
> >
> > On Thu, 2014-12-11 at 18:02 +0000, Mark Rutland wrote:
> > > Hi,
> > >
> > > On Wed, Dec 10, 2014 at 10:50:01AM +0000, Eddie Huang wrote:
> > > > Add device tree support for MT8173 SoC and evalutaion board based on it.
> > > >
> >
> > > > +
> > > > + psci {
> > > > + compatible = "arm,psci-0.2";
> > > > + method = "smc";
> > > > + };
> > >
> > > What are you using as your PSCI 0.2 implementation?
> > >
> > > Is it fully compliant? (e.g. are the reset and power off functions
> > > implemented, may CPU0 be hotplugged)?
> > >
> > > Given only portions of the GIC seem to be described below, what
> > > exception level is your kernel entered at? Per the spec it should be
> > > EL2, but given the brokenness below with the GIC I'm suspicious.
> > >
> >
> > Currently we only implement CPU boot, no power off, no CPU0 hotplug
> > either. And enter kernel at EL2. Actually, we run ATF in EL3, then
> > switch to EL2 to run lk and kernel.
>
> Ok. In the absence of CPU_OFF, this is not yet a conforming PSCI 0.2
> implementation, so I'm wary of marking this as PSCI 0.2 until that is
> the case. Any attempt to power of CPUs will hit a BUG() in cpu_die(),
> and we don't want that.
We are still developing PSCI related functions, CPU_ON, CPU_OFF,
CPU_SUSPEND are ready, others are going. PSCI 0.2 is our target although
lacks some implements
>
> Is CPU0 hotplug planned?
No
>
> If not, does your PSCI implementation report CPU0 as
> non-hotpluggable via MIGRATE_INFO_TYPE reporting a UP not migratable
> trusted OS (and MIGRATE_INFO_UP_CPU reporting CPU0 as the resident CPU)?
>
Will check whether add this
> Are SYSTEM_OFF and SYSTEM_RESET available?
No yet
>
> Thanks,
> Mark.
Since we miss some PSCI-0.2 implements, I don't know whether I should
remove PSCI stuff in this patch.
next prev parent reply other threads:[~2014-12-16 8:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 10:49 [PATCH 0/4] Add basic support for Mediatek MT8173 SoC Eddie Huang
2014-12-10 10:49 ` [PATCH 1/4] Document: DT: Add bindings for mediatek MT8173 Soc Platform Eddie Huang
2014-12-10 10:50 ` [PATCH 2/4] irqchip: mediatek: Add support for mt8173 Eddie Huang
2014-12-10 11:00 ` Arnd Bergmann
2014-12-10 14:37 ` Yingjoe Chen
2014-12-10 14:41 ` Arnd Bergmann
2014-12-10 10:50 ` [PATCH 3/4] arm64: dts: Add mediatek MT8173 SoC and evaluation board dts and Makefile Eddie Huang
2014-12-10 14:27 ` Yingjoe Chen
2014-12-10 14:50 ` Matthias Brugger
2014-12-11 12:47 ` Eddie Huang
2014-12-11 13:02 ` Matthias Brugger
2014-12-12 7:45 ` Eddie Huang
2014-12-11 18:02 ` Mark Rutland
2014-12-12 6:52 ` Sascha Hauer
2014-12-15 11:28 ` Mark Rutland
2014-12-12 8:08 ` Eddie Huang
2014-12-12 16:42 ` Jason Cooper
2014-12-15 13:32 ` Mark Rutland
2014-12-15 12:59 ` Mark Rutland
2014-12-16 8:46 ` Eddie Huang [this message]
2014-12-16 10:17 ` Mark Rutland
2014-12-10 10:50 ` [PATCH 4/4] arm64: mediatek: Add MT8173 SoC Kconfig and defconfig Eddie Huang
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=1418719615.8392.17.camel@mtksdaap41 \
--to=eddie.huang@mediatek.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).