From: Christoffer Dall <christoffer.dall@linaro.org>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Pawel Moll <pawel.moll@arm.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Will Deacon <will.deacon@arm.com>,
Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Kumar Gala <galak@codeaurora.org>,
Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm: document "mach-virt" platform.
Date: Sun, 2 Feb 2014 20:54:02 -0800 [thread overview]
Message-ID: <20140203045402.GA4167@cbox> (raw)
In-Reply-To: <1391098262-15944-1-git-send-email-ian.campbell@citrix.com>
On Thu, Jan 30, 2014 at 04:11:02PM +0000, Ian Campbell wrote:
> mach-virt has existed for a while but it is not written down what it actually
> consists of. Although it seems a bit unusual to document a binding for an
> entire platform since mach-virt is entirely virtual it is helpful to have
> something to refer to in the absence of a single concrete implementation.
>
> I've done my best to capture the requirements based on the git log and my
> memory/understanding.
[...]
>
> +
> +The platform may also provide hypervisor specific functionality
> +(e.g. PV I/O), if it does so then this functionality must be
> +discoverable (directly or indirectly) via device tree.
While this is obviously true, I'm not sure I see the value of this text.
Isn't it more essential to just say that *any* functionality provided to
the platform must be discoverable via device tree?
-Christoffer
prev parent reply other threads:[~2014-02-03 4:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 16:11 [PATCH] arm: document "mach-virt" platform Ian Campbell
[not found] ` <1391098262-15944-1-git-send-email-ian.campbell-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
2014-01-30 16:54 ` Christopher Covington
[not found] ` <52EA83D6.9050506-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-01-30 17:12 ` Stefano Stabellini
2014-02-03 4:56 ` Christoffer Dall
2014-02-03 11:14 ` Ian Campbell
2014-02-03 13:46 ` Christopher Covington
[not found] ` <52EF9D9F.5020600-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-02-03 17:41 ` Christoffer Dall
2014-01-30 17:15 ` Ian Campbell
[not found] ` <1391102149.9495.39.camel-ommiHX4a84BXesXXhkcM7miJhflN2719@public.gmane.org>
2014-01-30 17:43 ` Christopher Covington
2014-01-30 17:28 ` Arnd Bergmann
[not found] ` <201401301828.59294.arnd-r2nGTMty4D4@public.gmane.org>
2014-01-30 17:33 ` Marc Zyngier
[not found] ` <52EA8CFE.7020404-5wv7dgnIgG8@public.gmane.org>
2014-01-31 17:48 ` Rob Herring
2014-01-30 17:33 ` Ian Campbell
2014-01-30 17:13 ` Marc Zyngier
[not found] ` <52EA8853.8080709-5wv7dgnIgG8@public.gmane.org>
2014-01-30 17:21 ` Ian Campbell
[not found] ` <1391102475.9495.44.camel-ommiHX4a84BXesXXhkcM7miJhflN2719@public.gmane.org>
2014-01-30 17:24 ` Marc Zyngier
2014-01-30 17:29 ` Ian Campbell
2014-02-03 4:54 ` Christoffer Dall [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=20140203045402.GA4167@cbox \
--to=christoffer.dall@linaro.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ian.campbell@citrix.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=will.deacon@arm.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).