From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: julien.grall@linaro.org, xen-devel@lists.xen.org,
suravee.suthikulpanit@amd.com, stefano.stabellini@eu.citrix.com
Subject: Re: [V2 0/3] Introduce AMD Seattle platform support
Date: Thu, 2 Oct 2014 11:10:04 -0400 [thread overview]
Message-ID: <20141002151004.GC32249@laptop.dumpdata.com> (raw)
In-Reply-To: <1412254781.17146.9.camel@citrix.com>
On Thu, Oct 02, 2014 at 01:59:41PM +0100, Ian Campbell wrote:
> On Wed, 2014-10-01 at 14:51 -0500, suravee.suthikulpanit@amd.com wrote:
>
> Since we are post feature freeze this needs an ack from the release
> manager, Konrad CCd.
>
> Konrad, this is similar to the bcm series in that the only damage it can
> do is to the new platform being added. I think we should take it for
> 4.5.
Release-Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>
> > From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
> >
> > This patch series introduce minimal support for AMD Seattle system.
> > This has been tested to boot into dom0 and domU.
> >
> > The is platform currently using spintable as multi-core booting protocol.
> > However, it does supports system_off and system_reset from PSCI-0.2.
> > The firmware will support full PSCI-0.2 supports (except MIGRATION)
> > in the future.
> >
> > It also introduces GIC-400 device-tree matching string.
> >
> > Changes from V1:
> > * Remove dependency of system_off/reset of the Seattle platform
> > from PSCI subsystem.
> > * PSCI stuff is not re-submitted as a separate patch series.
> >
> > Suravee Suthikulpanit (3):
> > gicv2: Add compatibility id for gic-400
> > amd/seattle: Add early printk message for the platform
> > amd/seattle: Initial revision of AMD Seattle support
> >
> > xen/arch/arm/Rules.mk | 5 +++
> > xen/arch/arm/gic-v2.c | 1 +
> > xen/arch/arm/platforms/Makefile | 1 +
> > xen/arch/arm/platforms/seattle.c | 69 ++++++++++++++++++++++++++++++++++++++++
> > xen/include/asm-arm/gic.h | 4 ++-
> > 5 files changed, 79 insertions(+), 1 deletion(-)
> > create mode 100644 xen/arch/arm/platforms/seattle.c
> >
>
>
prev parent reply other threads:[~2014-10-02 15:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 19:51 [V2 0/3] Introduce AMD Seattle platform support suravee.suthikulpanit
2014-10-01 19:51 ` [V2 1/3] gicv2: Add compatibility id for gic-400 suravee.suthikulpanit
2014-10-01 19:51 ` [V2 2/3] amd/seattle: Add early printk message for the platform suravee.suthikulpanit
2014-10-02 15:52 ` Julien Grall
2014-10-02 18:40 ` Suravee Suthikulpanit
2014-10-01 19:51 ` [V2 3/3] amd/seattle: Initial revision of AMD Seattle support suravee.suthikulpanit
2014-10-02 10:41 ` Julien Grall
2014-10-02 19:04 ` Suravee Suthikulpanit
2014-10-02 20:37 ` Suravee Suthikulpanit
2014-10-02 21:26 ` Ian Campbell
2014-10-02 21:44 ` Julien Grall
2014-10-02 12:59 ` [V2 0/3] Introduce AMD Seattle platform support Ian Campbell
2014-10-02 15:10 ` Konrad Rzeszutek Wilk [this message]
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=20141002151004.GC32249@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=xen-devel@lists.xen.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).