From: Rob Herring <robh@kernel.org>
To: Oleksii Moisieiev <Oleksii_Moisieiev@epam.com>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>
Subject: Re: [RFC PATCH 1/1] dt-bindings: arm: Add scmi_devid property description for SCMI
Date: Tue, 22 Feb 2022 08:22:43 -0600 [thread overview]
Message-ID: <1645539763.068794.3016153.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <c751add9b54e9661e463ae265d8d5f0314eac33e.1645460043.git.oleksii_moisieiev@epam.com>
On Mon, 21 Feb 2022 17:26:47 +0000, Oleksii Moisieiev wrote:
> Document scmi_devid property for the devices, using SCMI protocol
> to work with clocks/resets/power-domains etc. This property is intended
> to set the device id, which should be used to manage device permissions
> in the firmware. Device permissions management is descibed in DEN 0056,
> Section 4.2.2.10 [0].
>
> This property is useful for the virtualized systems, when several agents
> are running on the same platform. Agent term is descibed in Section
> 4.1.1 [0].
>
> [0] https://developer.arm.com/documentation/den0056/latest
>
> Signed-off-by: Oleksii Moisieiev <oleksii_moisieiev@epam.com>
> ---
> .../bindings/firmware/arm,scmi-devid.yaml | 41 +++++++++++++++++++
> 1 file changed, 41 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/firmware/arm,scmi-devid.yaml
>
My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check'
on your patch (DT_CHECKER_FLAGS is new in v5.13):
yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/firmware/arm,scmi-devid.example.dt.yaml: example-0: usb@ee0a0000:reg:0: [0, 3993632768, 0, 256] is too long
From schema: /usr/local/lib/python3.8/dist-packages/dtschema/schemas/reg.yaml
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/patch/1595720
This check can fail if there are any dependencies. The base for a patch
series is generally the most recent rc1.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit.
next prev parent reply other threads:[~2022-02-22 14:23 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 [this message]
2022-02-22 14:51 ` Oleksii Moisieiev
2022-02-22 18:25 ` Rob Herring
2022-02-21 21:01 ` [RFC PATCH 0/1] dt-bindings: arm: Add scmi_devid paramter for Krzysztof Kozlowski
2022-02-21 21:39 ` 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=1645539763.068794.3016153.nullmailer@robh.at.kernel.org \
--to=robh@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 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).