From: Alexandre Torgue <alexandre.torgue@st.com>
To: Maxime Ripard <mripard@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>, Chen-Yu Tsai <wens@csie.org>,
Alexandru Ardelean <alexaundru.ardelean@analog.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Alexandre Torgue <alexandre.torgue@st.com>,
<linux-media@vger.kernel.org>, <netdev@vger.kernel.org>
Subject: [PATCH 2/3] dt-bindings: net: adi: Fix yaml verification issue
Date: Mon, 7 Oct 2019 12:25:51 +0200 [thread overview]
Message-ID: <20191007102552.19808-3-alexandre.torgue@st.com> (raw)
In-Reply-To: <20191007102552.19808-1-alexandre.torgue@st.com>
This commit fixes an issue seen during yaml check ("make dt_binding_check").
Each enum were not declared as uint32.
"Documentation/devicetree/bindings/net/adi,adin.yaml:
properties:adi,rx-internal-delay-ps:
..., 'enum': [1600, 1800, 2000, 2200, 2400], 'default': 2000}
is not valid under any of the given schemas"
Fixes: 767078132ff9 ("dt-bindings: net: add bindings for ADIN PHY driver")
Signed-off-by: Alexandre Torgue <alexandre.torgue@st.com>
diff --git a/Documentation/devicetree/bindings/net/adi,adin.yaml b/Documentation/devicetree/bindings/net/adi,adin.yaml
index d95cc691a65f..23e8597acda6 100644
--- a/Documentation/devicetree/bindings/net/adi,adin.yaml
+++ b/Documentation/devicetree/bindings/net/adi,adin.yaml
@@ -17,6 +17,8 @@ allOf:
properties:
adi,rx-internal-delay-ps:
+ allOf:
+ - $ref: "/schemas/types.yaml#/definitions/uint32"
description: |
RGMII RX Clock Delay used only when PHY operates in RGMII mode with
internal delay (phy-mode is 'rgmii-id' or 'rgmii-rxid') in pico-seconds.
@@ -24,6 +26,8 @@ properties:
default: 2000
adi,tx-internal-delay-ps:
+ allOf:
+ - $ref: "/schemas/types.yaml#/definitions/uint32"
description: |
RGMII TX Clock Delay used only when PHY operates in RGMII mode with
internal delay (phy-mode is 'rgmii-id' or 'rgmii-txid') in pico-seconds.
@@ -31,6 +35,8 @@ properties:
default: 2000
adi,fifo-depth-bits:
+ allOf:
+ - $ref: "/schemas/types.yaml#/definitions/uint32"
description: |
When operating in RMII mode, this option configures the FIFO depth.
enum: [ 4, 8, 12, 16, 20, 24 ]
--
2.17.1
next prev parent reply other threads:[~2019-10-07 10:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 10:25 [PATCH 0/3] Fixes for dt-bindings verification Alexandre Torgue
2019-10-07 10:25 ` [PATCH 1/3] dt-bindings: media: Fix id path for sun4i-a10-csi Alexandre Torgue
2019-10-07 11:00 ` Maxime Ripard
2019-10-07 14:08 ` Alexandre Torgue
2019-10-07 10:25 ` Alexandre Torgue [this message]
2019-10-07 13:56 ` [PATCH 2/3] dt-bindings: net: adi: Fix yaml verification issue Rob Herring
2019-10-07 14:07 ` Alexandre Torgue
2019-10-07 10:25 ` [PATCH 3/3] dt-bindings: regulator: Fix yaml verification for fixed-regulator schema Alexandre Torgue
2019-10-07 13:08 ` Rob Herring
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=20191007102552.19808-3-alexandre.torgue@st.com \
--to=alexandre.torgue@st.com \
--cc=alexaundru.ardelean@analog.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).