From: "Rob Herring (Arm)" <robh@kernel.org>
To: Krishna Yarlagadda <kyarlagadda@nvidia.com>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
thierry.reding@gmail.com, corbet@lwn.net,
wsa+renesas@sang-engineering.com, linux-mmc@vger.kernel.org,
mkumard@nvidia.com, conor+dt@kernel.org, digetx@gmail.com,
jonathanh@nvidia.com, ulf.hansson@linaro.org,
adrian.hunter@intel.com, krzk+dt@kernel.org,
ldewangan@nvidia.com, andi.shyti@kernel.org,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [RFC PATCH V2 02/12] dt-bindings: misc: Tegra configuration settings
Date: Mon, 01 Jul 2024 10:58:06 -0600 [thread overview]
Message-ID: <171985308459.97826.5913144398477563186.robh@kernel.org> (raw)
In-Reply-To: <20240701151231.29425-3-kyarlagadda@nvidia.com>
On Mon, 01 Jul 2024 20:42:20 +0530, Krishna Yarlagadda wrote:
> Config framework parses device tree and provides a list of register
> settings with mask per mode to be applied by the controller.
>
> Add binding document for config settings framework. Config settings
> are defined as a property per field and have different modes per device.
>
> Signed-off-by: Krishna Yarlagadda <kyarlagadda@nvidia.com>
> ---
> .../misc/nvidia,tegra-config-settings.yaml | 62 +++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 63 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/misc/nvidia,tegra-config-settings.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
./Documentation/devicetree/bindings/misc/nvidia,tegra-config-settings.yaml:46:1: [error] syntax error: found character '\t' that cannot start any token (syntax)
dtschema/dtc warnings/errors:
make[2]: *** Deleting file 'Documentation/devicetree/bindings/misc/nvidia,tegra-config-settings.example.dts'
Documentation/devicetree/bindings/misc/nvidia,tegra-config-settings.yaml:46:1: found character that cannot start any token
make[2]: *** [Documentation/devicetree/bindings/Makefile:26: Documentation/devicetree/bindings/misc/nvidia,tegra-config-settings.example.dts] Error 1
make[2]: *** Waiting for unfinished jobs....
./Documentation/devicetree/bindings/misc/nvidia,tegra-config-settings.yaml:46:1: found character that cannot start any token
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/misc/nvidia,tegra-config-settings.yaml: ignoring, error parsing file
make[1]: *** [/builds/robherring/dt-review-ci/linux/Makefile:1430: dt_binding_check] Error 2
make: *** [Makefile:240: __sub-make] Error 2
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20240701151231.29425-3-kyarlagadda@nvidia.com
The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.
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 after running the above command yourself. Note
that DT_SCHEMA_FILES can be set to your schema file to speed up checking
your schema. However, it must be unset to test all examples with your schema.
next prev parent reply other threads:[~2024-07-01 16:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 15:12 [RFC PATCH V2 00/12] Introduce Tegra register config settings Krishna Yarlagadda
2024-07-01 15:12 ` [RFC PATCH V2 01/12] Documentation: Introduce config settings framework Krishna Yarlagadda
2024-07-01 15:12 ` [RFC PATCH V2 02/12] dt-bindings: misc: Tegra configuration settings Krishna Yarlagadda
2024-07-01 16:58 ` Rob Herring (Arm) [this message]
2024-07-01 15:12 ` [RFC PATCH V2 03/12] soc: tegra: Add config setting framework Krishna Yarlagadda
2024-07-01 15:12 ` [RFC PATCH V2 04/12] dt-bindings: misc: tegra-i2c: config settings Krishna Yarlagadda
2024-07-01 16:58 ` Rob Herring (Arm)
2024-07-01 17:42 ` Rob Herring
2024-07-02 10:29 ` Thierry Reding
2024-07-03 20:21 ` Rob Herring
2024-07-05 10:51 ` Thierry Reding
2024-07-01 15:12 ` [RFC PATCH V2 05/12] dt-bindings: i2c: tegra-i2c: reference to config Krishna Yarlagadda
2024-07-01 16:58 ` Rob Herring (Arm)
2024-07-01 15:12 ` [RFC PATCH V2 06/12] i2c: tegra: split clock initialization code Krishna Yarlagadda
2024-07-01 15:12 ` [RFC PATCH V2 07/12] i2c: tegra: config settings for interface timings Krishna Yarlagadda
2024-07-01 15:12 ` [RFC PATCH V2 08/12] arm64: tegra: I2C " Krishna Yarlagadda
2024-07-01 15:12 ` [RFC PATCH V2 09/12] dt-bindings: misc: tegra-sdhci: config settings Krishna Yarlagadda
2024-07-01 15:12 ` [RFC PATCH V2 10/12] dt-bindings: mmc: tegra-sdhci: reference to config Krishna Yarlagadda
2024-07-01 15:12 ` [RFC PATCH V2 11/12] mmc: host: tegra: config settings for timing Krishna Yarlagadda
2024-07-01 15:12 ` [RFC PATCH V2 12/12] arm64: tegra: SDHCI timing settings Krishna Yarlagadda
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=171985308459.97826.5913144398477563186.robh@kernel.org \
--to=robh@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=kyarlagadda@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkumard@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=ulf.hansson@linaro.org \
--cc=wsa+renesas@sang-engineering.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).