From: Rob Herring <robh@kernel.org>
To: Cristian Marussi <cristian.marussi@arm.com>
Cc: Rob Herring <robh+dt@kernel.org>,
peter.hilber@opensynergy.com, Jonathan.Cameron@Huawei.com,
sudeep.holla@arm.com, f.fainelli@gmail.com,
vincent.guittot@linaro.org, devicetree@vger.kernel.org,
souvik.chakravarty@arm.com, etienne.carriere@linaro.org,
linux-kernel@vger.kernel.org, igor.skalkin@opensynergy.com,
linux-arm-kernel@lists.infradead.org, james.quinlan@broadcom.com
Subject: Re: [PATCH v4 4/8] dt-bindings: firmware: arm,scmi: Add atomic-threshold-us optional property
Date: Tue, 15 Feb 2022 09:22:45 -0600 [thread overview]
Message-ID: <1644938565.068934.3450861.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20220213195832.27932-5-cristian.marussi@arm.com>
On Sun, 13 Feb 2022 19:58:28 +0000, Cristian Marussi wrote:
> SCMI protocols in the platform can optionally signal to the OSPM agent
> the expected execution latency for a specific resource/operation pair.
>
> Introduce an SCMI system wide optional property to describe a global time
> threshold which can be configured on a per-platform base to determine the
> opportunity, or not, for an SCMI command advertised to have a higher
> latency than the threshold, to be considered for atomic operations:
> high-latency SCMI synchronous commands should be preferably issued in the
> usual non-atomic mode.
>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
> ---
> v3 --> v4
> - renamed property to atomic-threshold-us
> v1 --> v2
> - rephrased the property description
> ---
> .../devicetree/bindings/firmware/arm,scmi.yaml | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
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.yaml: properties:atomic-threshold-us: '$ref' should not be valid under {'const': '$ref'}
hint: Standard unit suffix properties don't need a type $ref
from schema $id: http://devicetree.org/meta-schemas/core.yaml#
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/firmware/arm,scmi.yaml: ignoring, error in schema: properties: atomic-threshold-us
Documentation/devicetree/bindings/firmware/arm,scmi.example.dt.yaml:0:0: /example-0/firmware/scmi: failed to match any schema with compatible: ['arm,scmi']
Documentation/devicetree/bindings/firmware/arm,scmi.example.dt.yaml:0:0: /example-1/firmware/scmi: failed to match any schema with compatible: ['arm,scmi-smc']
Documentation/devicetree/bindings/mailbox/arm,mhu.example.dt.yaml:0:0: /example-1/firmware/scmi: failed to match any schema with compatible: ['arm,scmi']
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/patch/1592136
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-15 15:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 19:58 [PATCH v4 0/8] Add SCMI Virtio & Clock atomic support Cristian Marussi
2022-02-13 19:58 ` [PATCH v4 1/8] firmware: arm_scmi: Add a virtio channel refcount Cristian Marussi
2022-02-16 10:15 ` Peter Hilber
2022-02-16 14:47 ` Cristian Marussi
2022-02-13 19:58 ` [PATCH v4 2/8] firmware: arm_scmi: Review virtio free_list handling Cristian Marussi
2022-02-13 19:58 ` [PATCH v4 3/8] firmware: arm_scmi: Add atomic mode support to virtio transport Cristian Marussi
2022-02-15 9:11 ` Cristian Marussi
2022-02-16 9:12 ` Peter Hilber
2022-02-16 14:46 ` Cristian Marussi
2022-02-13 19:58 ` [PATCH v4 4/8] dt-bindings: firmware: arm,scmi: Add atomic-threshold-us optional property Cristian Marussi
2022-02-15 9:20 ` Cristian Marussi
2022-02-15 15:22 ` Rob Herring [this message]
2022-02-15 21:03 ` Rob Herring
2022-02-15 21:07 ` Cristian Marussi
2022-02-13 19:58 ` [PATCH v4 5/8] firmware: arm_scmi: Support optional system wide atomic-threshold-us Cristian Marussi
2022-02-13 19:58 ` [PATCH v4 6/8] firmware: arm_scmi: Add atomic support to clock protocol Cristian Marussi
2022-02-13 19:58 ` [PATCH v4 7/8] firmware: arm_scmi: Add support for clock_enable_latency Cristian Marussi
2022-02-13 19:58 ` [PATCH v4 8/8] clk: scmi: Support atomic clock enable/disable API Cristian Marussi
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=1644938565.068934.3450861.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Jonathan.Cameron@Huawei.com \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=etienne.carriere@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=igor.skalkin@opensynergy.com \
--cc=james.quinlan@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.hilber@opensynergy.com \
--cc=robh+dt@kernel.org \
--cc=souvik.chakravarty@arm.com \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.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