From: Ian Campbell <ian.campbell@citrix.com>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Cc: tim@xen.org, julien.grall@linaro.org,
stefano.stabellini@citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v1 0/2] Add support for Xilinx ZynqMP SoC
Date: Fri, 6 Mar 2015 09:44:16 +0000 [thread overview]
Message-ID: <1425635056.14353.20.camel@citrix.com> (raw)
In-Reply-To: <20150306013156.GD9306@toto>
On Fri, 2015-03-06 at 11:31 +1000, Edgar E. Iglesias wrote:
> On Thu, Mar 05, 2015 at 04:50:15PM +0000, Ian Campbell wrote:
> > On Thu, 2015-03-05 at 18:27 +1000, Edgar E. Iglesias wrote:
> > > From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
> > >
> > > Adds support for the Cadence UART in Xilinx ZynqMP. The
> > > rest of the ZynqMP platform is discovered via device-tree.
> >
> > Is it fully discovered and working out of the box? That would be ....
> > awesome!
>
> Yes it would be awesome if we can keep it like that :-)
I suppose you are seeing the "WARNING: Unrecognized/unsupported device
tree compatible list" message?
I wonder if we should either remove or tone down that warning, now that
we have a platform which genuinely doesn't require any platform specific
code. I think we probably want to say something so in bug reports we
know what is happening, maybe just something like "Platform: Generic
System".
> It's possible that we will need to add platform code in the future
> as we test out more features. In particular we'll likely need to do
> something around power/clock management.
Yes, this is something of an open problem for us, and one which I'm
unsure how to solve without some platform specific code in each case.
Most power/clock management should be deferred to the h/w domain which
is managing the I/O peripherals (likely dom0) but we need some way to
filter its activities to keep e.g. the CPU and UART (or in reality any
h/w block Xen itself is using, which isn't many fortunately) clocks on.
http://bugs.xenproject.org/xen/bug/45 is a related bug.
> > Do you have any links to any more information about this platform (I'm
> > just curious).
>
> This one is a good starting point with follow-up links:
> http://www.xilinx.com/products/technology/ultrascale-mpsoc.html
>
> The short version is that the ZynqMP is a chip including both a hard SoC part
> (PS, Programmable System) and a "soft" Programmable Logic (PL) FPGA part.
> In terms of Virtualization, the hard PS part has quad Cortex-A53s with
> EL2 enabled and an SMMU to allow secure device-passthrough of DMA capable devices.
That sounds like a pretty sweet platform, thanks!
> For early access there are two platforms available, an FPGA based
> emulation platform (EP108) and a modified version of QEMU. XEN can run
> on both those platforms.
>
>
> > Also, if you could find the time to add a wikipage as a child of
> > http://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions
> > (like for the other platforms) and add it to the h/w table on the main
> > page that would be great.
> >
> > The wiki is locked down because of spammers, once you've created an
> > account either drop me a line or fill in the form
> > http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html and someone will enable write access for you.
>
> Yes, I'm happy to update the wiki. I've created a user (edgar_igl) and filled out the form.
I've just seen the form entry and added the write bit to "edgar_igl".
Thanks!
Ian.
next prev parent reply other threads:[~2015-03-06 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 8:27 [PATCH v1 0/2] Add support for Xilinx ZynqMP SoC Edgar E. Iglesias
2015-03-05 8:27 ` [PATCH v1 1/2] xen/arm: Add Cadence UART driver Edgar E. Iglesias
2015-03-05 17:06 ` Ian Campbell
2015-03-06 1:08 ` Edgar E. Iglesias
2015-03-05 8:27 ` [PATCH v1 2/2] xen/arm: Add Xilinx ZynqMP early printk support Edgar E. Iglesias
2015-03-05 16:50 ` [PATCH v1 0/2] Add support for Xilinx ZynqMP SoC Ian Campbell
2015-03-06 1:31 ` Edgar E. Iglesias
2015-03-06 9:44 ` Ian Campbell [this message]
2015-03-09 3:14 ` Edgar E. Iglesias
2015-03-09 11:09 ` Ian Campbell
2015-03-09 12:07 ` Edgar E. Iglesias
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=1425635056.14353.20.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=edgar.iglesias@gmail.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.