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@xxxxxx> > --- > 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@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
