All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Oleksii Moisieiev <Oleksii_Moisieiev@epam.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>
Cc: "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: Re: [RFC PATCH 0/1] dt-bindings: arm: Add scmi_devid paramter for
Date: Mon, 21 Feb 2022 22:01:43 +0100	[thread overview]
Message-ID: <2546477f-4190-e838-3095-f47b31802445@kernel.org> (raw)
In-Reply-To: <cover.1645460043.git.oleksii_moisieiev@epam.com>

On 21/02/2022 18:26, Oleksii Moisieiev wrote:
> Introducing new parameter called 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 feature will be extremely useful for
> the virtualized systems, which has more that one Guests running on the
> system at the same time or for the syestems, which require several
> agents with different permissions. Trusted agent will use 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].
> 
> scmi_devid in Device-tree node example:
> usb@e6590000
> {
>     scmi_devid = <19>;
>     clocks = <&scmi_clock 3>, <&scmi_clock 2>;
>     resets = <&scmi_reset 10>, <&scmi_reset 9>;
>     power-domains = <&scmi_power 0>;
> };

And how do you prevent DT overlay adding such devid to any other node
thus allowing any other device to send requests with given devid?

Plus few technicalities:
1. Hyphen, not underscore in property name, so scmi-devid.
2. Your schema does is not selected by anything. How is it intended to
be used? Nothing is including it, either...

Best regards,
Krzysztof

  parent reply	other threads:[~2022-02-21 21:01 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 17:26 [RFC PATCH 0/1] dt-bindings: arm: Add scmi_devid paramter for Oleksii Moisieiev
2022-02-21 17:26 ` [RFC PATCH 1/1] dt-bindings: arm: Add scmi_devid property description for SCMI Oleksii Moisieiev
2022-02-22 14:22   ` Rob Herring
2022-02-22 14:51     ` Oleksii Moisieiev
2022-02-22 18:25       ` Rob Herring
2022-02-21 21:01 ` Krzysztof Kozlowski [this message]
2022-02-21 21:39   ` [RFC PATCH 0/1] dt-bindings: arm: Add scmi_devid paramter for Oleksii Moisieiev
2022-02-22  8:06     ` Krzysztof Kozlowski
2022-02-22  8:55       ` Oleksii Moisieiev
2022-02-22  9:27         ` Krzysztof Kozlowski
2022-02-22 10:30           ` Oleksii Moisieiev
2022-02-22 11:16             ` Krzysztof Kozlowski
2022-02-22 13:54               ` Oleksii Moisieiev
2022-02-22 16:14       ` Sudeep Holla
2022-02-22 17:34         ` Oleksii Moisieiev
2022-02-24  2:51           ` Stefano Stabellini
2022-02-24  9:32             ` Cristian Marussi
2022-02-24 22:22               ` Stefano Stabellini
2022-03-01 14:55                 ` Oleksii Moisieiev
2022-03-04 11:21                 ` Sudeep Holla
2022-03-04 11:18             ` Sudeep Holla
2022-02-22 11:00 ` Cristian Marussi
2022-02-22 13:51   ` Oleksii Moisieiev
2022-02-22 16:06   ` Sudeep Holla
2022-02-22 17:15     ` Oleksii Moisieiev
2022-02-24 11:54       ` Sudeep Holla
2022-02-24 22:51         ` Stefano Stabellini
2022-02-24 23:34           ` Stefano Stabellini
2022-03-04 11:12             ` Sudeep Holla
2022-03-05  0:45               ` Stefano Stabellini
2022-04-29 21:46                 ` Rob Herring
2022-03-01 16:10           ` Oleksii Moisieiev
2022-03-01 16:05         ` Oleksii Moisieiev

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=2546477f-4190-e838-3095-f47b31802445@kernel.org \
    --to=krzk@kernel.org \
    --cc=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 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.