From: Rob Herring <robh@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: "Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Jakub Kicinski" <kuba@kernel.org>,
devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
"Biju Das" <biju.das@bp.renesas.com>,
linux-can@vger.kernel.org,
"Chris Paterson" <Chris.Paterson2@renesas.com>,
"Wolfgang Grandegger" <wg@grandegger.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Rob Herring" <robh+dt@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Marc Kleine-Budde" <mkl@pengutronix.de>,
"Eric Dumazet" <edumazet@google.com>
Subject: Re: [PATCH v2 1/6] dt-bindings: can: sja1000: Convert to json-schema
Date: Sun, 03 Jul 2022 12:00:23 -0600 [thread overview]
Message-ID: <1656871223.903187.1705437.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20220703104705.341070-2-biju.das.jz@bp.renesas.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
On Sun, 03 Jul 2022 11:47:00 +0100, Biju Das wrote:
> Convert the NXP SJA1000 CAN Controller Device Tree binding
> documentation to json-schema.
>
> Update the example to match reality.
>
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> ---
> v1->v2:
> * Moved $ref: can-controller.yaml# to top along with if conditional to
> avoid multiple mapping issues with the if conditional in the subsequent
> patch.
> ---
> .../bindings/net/can/nxp,sja1000.yaml | 102 ++++++++++++++++++
> .../devicetree/bindings/net/can/sja1000.txt | 58 ----------
> 2 files changed, 102 insertions(+), 58 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/net/can/nxp,sja1000.yaml
> delete mode 100644 Documentation/devicetree/bindings/net/can/sja1000.txt
>
Running 'make dtbs_check' with the schema in this patch gives the
following warnings. Consider if they are expected or the schema is
incorrect. These may not be new warnings.
Note that it is not yet a requirement to have 0 warnings for dtbs_check.
This will change in the future.
Full log is available here: https://patchwork.ozlabs.org/patch/
can@4,0: nxp,tx-output-config:0:0: 22 is not one of [1, 2, 4, 6, 8, 16, 32, 48]
arch/arm/boot/dts/imx27-phytec-phycore-rdk.dtb
can@4,0: 'reg-io-width' is a required property
arch/arm/boot/dts/imx27-phytec-phycore-rdk.dtb
next prev parent reply other threads:[~2022-07-03 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 10:46 [PATCH v2 0/6] Add support for RZ/N1 SJA1000 CAN controller Biju Das
2022-07-03 10:47 ` [PATCH v2 1/6] dt-bindings: can: sja1000: Convert to json-schema Biju Das
2022-07-03 18:00 ` Rob Herring [this message]
2022-07-03 18:54 ` Biju Das
2022-07-03 10:47 ` [PATCH v2 2/6] dt-bindings: can: nxp,sja1000: Document RZ/N1{D,S} support Biju Das
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=1656871223.903187.1705437.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wg@grandegger.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