From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] Documentation: dt: keystone: ti-sci: Add optional host-id parameter
Date: Tue, 26 Jun 2018 15:12:03 -0600 [thread overview]
Message-ID: <20180626211203.GA19874@rob-hp-laptop> (raw)
In-Reply-To: <20180619194421.3432-2-nm@ti.com>
On Tue, Jun 19, 2018 at 02:44:20PM -0500, Nishanth Menon wrote:
> Texas Instrument's System Control Interface (TISCI) permits
> the ability for OSs running in virtual machines to be able to
> independently communicate with the firmware without the need going
> through an hypervisor.
>
> The "host-id" in effect is the hardware representation of the
> host (example: VMs locked to a core) as identified to the System
> Controller. Hypervisors can either fill in appropriate host-ids in dt
> used for each VM instance OR may use prebuilt blobs where the host-ids
> are pre-populated, as appropriate for the OS running in the VMs.
>
> This is introduced as an optional parameter to maintain consistency
> with legacy device tree blobs.
>
> We call this with a vendor prefix to prevent any possible confusion
> with SCSI ID (m68k) kernel option.
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
> Changes since RFC:
> * Commit message update to elaborate usage in VM
>
> RFC: https://patchwork.kernel.org/patch/10447753/
>
> Documentation/devicetree/bindings/arm/keystone/ti,sci.txt | 4 ++++
> 1 file changed, 4 insertions(+)
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-06-26 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 19:44 [PATCH 0/2] firmware: ti_sci: Add host-id as an optional parameter Nishanth Menon
2018-06-19 19:44 ` [PATCH 1/2] Documentation: dt: keystone: ti-sci: Add optional host-id parameter Nishanth Menon
2018-06-26 21:12 ` Rob Herring [this message]
2018-06-27 8:46 ` Geert Uytterhoeven
2018-06-19 19:44 ` [PATCH 2/2] firmware: ti_sci: Provide host-id as an optional dt parameter Nishanth Menon
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=20180626211203.GA19874@rob-hp-laptop \
--to=robh@kernel.org \
--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