linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleksii Moisieiev <Oleksii_Moisieiev@epam.com>
To: "robh+dt@kernel.org" <robh+dt@kernel.org>
Cc: Oleksii Moisieiev <Oleksii_Moisieiev@epam.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Cristian Marussi <cristian.marussi@arm.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH v2 0/2] dt-bindings: xen: Add xen,scmi-devid parameter for
Date: Mon, 7 Mar 2022 08:17:43 +0000	[thread overview]
Message-ID: <cover.1646639462.git.oleksii_moisieiev@epam.com> (raw)

Introducing new parameter called xen,scmi-devid to the device-tree bindings.
This parameter should be set for the device nodes, which has
clocks/power-domains/resets working through SCMI.
Given parameter should set the device_id, needed to set device
permissions in the Firmware.
This property is used by Xen hypervisor, which works as trusted Agent,
to set permissions for the devices, passed-through to the Guest Domains,
which are non-trusted Agents. Trusted Agent will use xen,scmi-devid to
set the Device permissions for the Firmware (See Section 4.2.2.10 [0]
for details).
Agents concept is described in Section 4.2.1 [0].

xen,scmi-devid in Device-tree node example:
usb@e6590000
{
    xen,scmi-devid = <19>;
    clocks = <&scmi_clock 3>, <&scmi_clock 2>;
    resets = <&scmi_reset 10>, <&scmi_reset 9>;
    power-domains = <&scmi_power 0>;
};

Given example shows the configuration of the hsusb node, which is using
scmi to contol clocks, resets and power-domains. scmi_devid is set
equals to 19, which should match defined id for usb in the Firmware.

Trusted Agent will use xen,scmi-devid to set the device permissions for
the Agents. Guest OS should not have an access to the permissions
settings, so no code to process xen,scmi-devid was presented in Linux
kernel.

We are currently contributing changes to Xen, which are intended to
mediate SCMI access from Guests to the Firmware. Xen uses xen,scmi-devid to set
the permissions for the devices. See [1] thread for details.

[0] https://developer.arm.com/documentation/den0056/latest
[1] https://xen.markmail.org/message/mmi4fpb4qr6e3kad


Oleksii Moisieiev (2):
  dt-bindings: Add vendor prefix for Xen hypervisor
  dt-bindings: xen: Add xen,scmi-devid property description for SCMI

 .../bindings/firmware/xen,scmi-devid.yaml     | 42 +++++++++++++++++++
 .../devicetree/bindings/vendor-prefixes.yaml  |  2 +
 2 files changed, 44 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/firmware/xen,scmi-devid.yaml

-- 
2.27.0

             reply	other threads:[~2022-03-07  8:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07  8:17 Oleksii Moisieiev [this message]
2022-03-07  8:17 ` [PATCH v2 1/2] dt-bindings: Add vendor prefix for Xen hypervisor Oleksii Moisieiev
2022-03-07 23:30   ` Stefano Stabellini
2022-03-08 20:14   ` Rob Herring
2022-03-10 11:38     ` Oleksii Moisieiev
2022-03-10 17:20       ` Stefano Stabellini
2022-03-07  8:17 ` [PATCH v2 2/2] dt-bindings: xen: Add xen,scmi-devid property description for SCMI Oleksii Moisieiev
2022-03-07 23:38   ` Stefano Stabellini
2022-03-08 20:13   ` Rob Herring
2022-03-16 16:46     ` Oleksii Moisieiev
2022-03-16 18:59       ` Sudeep Holla
2022-03-18 23:53         ` Stefano Stabellini
2022-03-22 11:12           ` Sudeep Holla
2022-03-22 19:21             ` Oleksii Moisieiev
2022-03-23 10:54               ` Sudeep Holla
2022-03-28  8:52                 ` Oleksii Moisieiev
2022-04-12 22:42                   ` Stefano Stabellini
2022-04-22 17:59                   ` Sudeep Holla

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=cover.1646639462.git.oleksii_moisieiev@epam.com \
    --to=oleksii_moisieiev@epam.com \
    --cc=cristian.marussi@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sstabellini@kernel.org \
    --cc=sudeep.holla@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).