From: Michal Simek <michal.simek@amd.com>
To: Michal Simek <monstr@monstr.eu>, Rob Herring <robh@kernel.org>
Cc: linux-kernel@vger.kernel.org, git@amd.com,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
kishore Manne <nava.kishore.manne@amd.com>,
"moderated list:ARM/ZYNQ ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list:COMMON CLK FRAMEWORK" <linux-clk@vger.kernel.org>
Subject: Re: [PATCH v3 3/5] dt-bindings: clock: Move xlnx,zynqmp-clk to its own schema
Date: Wed, 8 Jul 2026 09:22:33 +0200 [thread overview]
Message-ID: <350447fc-95c3-411c-934b-26fdb37c5860@amd.com> (raw)
In-Reply-To: <da06120d-0850-4e79-9e07-efe481c057ff@monstr.eu>
On 7/7/26 18:34, Michal Simek wrote:
>
>
> On 7/7/26 17:55, Rob Herring wrote:
>> On Wed, Jun 3, 2026 at 10:12 AM Michal Simek <michal.simek@amd.com> wrote:
>>>
>>> The ZynqMP clock controller binding shares only #clock-cells with the
>>> Versal bindings. Move it to a dedicated xlnx,zynqmp-clk.yaml schema.
>>> Also remove "(Optional clock)" from clock description because it is visible
>>> from schema itself.
>>>
>>> Suggested-by: Rob Herring <robh@kernel.org>
>>> Signed-off-by: Michal Simek <michal.simek@amd.com>
>>> ---
>>>
>>> Changes in v3:
>>> - Cover change in zynqmp-firmware.yaml
>>> - Move clock-cells to be the last in the example
>>> - Remove comment around (Optional clock) which is obvious from schema
>>> itself
>>>
>>> Changes in v2:
>>> - New patch in series
>>> - Split zynqmp-clk from versal-clk
>>>
>>> .../bindings/clock/xlnx,versal-clk.yaml | 50 +-------------
>>> .../bindings/clock/xlnx,zynqmp-clk.yaml | 68 +++++++++++++++++++
>>> .../firmware/xilinx/xlnx,zynqmp-firmware.yaml | 7 +-
>>> 3 files changed, 76 insertions(+), 49 deletions(-)
>>> create mode 100644 Documentation/devicetree/bindings/clock/xlnx,zynqmp-
>>> clk.yaml
>>
>> This is now causing warnings in linux-next:
>>
>> /builds/robherring/linux-dt/Documentation/devicetree/bindings/clock/
>> xlnx,versal-clk.example.dtb:
>> zynqmp-firmware (xlnx,zynqmp-firmware):
>> clock-controller:clock-names:0: 'pss_ref_clk' was expected
>> from schema $id:
>> http://devicetree.org/schemas/firmware/xilinx/xlnx,zynqmp-firmware.yaml
>> /builds/robherring/linux-dt/Documentation/devicetree/bindings/clock/
>> xlnx,versal-clk.example.dtb:
>> zynqmp-firmware (xlnx,zynqmp-firmware):
>> clock-controller:clock-names:1: 'video_clk' was expected
>> from schema $id:
>> http://devicetree.org/schemas/firmware/xilinx/xlnx,zynqmp-firmware.yaml
>> /builds/robherring/linux-dt/Documentation/devicetree/bindings/clock/
>> xlnx,versal-clk.example.dtb:
>> zynqmp-firmware (xlnx,zynqmp-firmware): clock-controller:clock-names:
>> ['ref', 'pl_alt_ref'] is too short
>> from schema $id:
>> http://devicetree.org/schemas/firmware/xilinx/xlnx,zynqmp-firmware.yaml
>> /builds/robherring/linux-dt/Documentation/devicetree/bindings/clock/
>> xlnx,versal-clk.example.dtb:
>> zynqmp-firmware (xlnx,zynqmp-firmware): clock-controller:clocks:
>> [[4294967295], [4294967295]] is too short
>> from schema $id:
>> http://devicetree.org/schemas/firmware/xilinx/xlnx,zynqmp-firmware.yaml
>> /builds/robherring/linux-dt/Documentation/devicetree/bindings/clock/
>> xlnx,versal-clk.example.dtb:
>> zynqmp-firmware (xlnx,zynqmp-firmware): clock-controller:compatible:0:
>> 'xlnx,zynqmp-clk' was expected
>> from schema $id:
>> http://devicetree.org/schemas/firmware/xilinx/xlnx,zynqmp-firmware.yaml
>
> I will look at it. Thanks for reporting it.
Today Linux-next won't have this series and I have also sent v4 with fixing this.
Thanks,
Michal
next prev parent reply other threads:[~2026-07-08 7:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 15:12 [PATCH v3 0/5] clock: versal-clk: Fix Versal NET clock binding and switch to CCF Michal Simek
2026-06-03 15:12 ` [PATCH v3 1/5] dt-bindings: firmware: xilinx: Add missing example for ZynqMP Michal Simek
2026-06-03 15:30 ` Conor Dooley
2026-06-03 15:12 ` [PATCH v3 2/5] dt-bindings: clock: versal-clk: Fix mio_clk index range in clock-names pattern Michal Simek
2026-06-03 15:24 ` sashiko-bot
2026-06-03 15:33 ` Conor Dooley
2026-06-03 15:35 ` Michal Simek
2026-06-03 16:08 ` Conor Dooley
2026-06-03 15:12 ` [PATCH v3 3/5] dt-bindings: clock: Move xlnx,zynqmp-clk to its own schema Michal Simek
2026-06-03 15:34 ` sashiko-bot
2026-06-03 15:34 ` Conor Dooley
2026-07-07 15:55 ` Rob Herring
2026-07-07 16:34 ` Michal Simek
2026-07-08 7:22 ` Michal Simek [this message]
2026-06-03 15:12 ` [PATCH v3 4/5] dt-bindings: clock: versal-clk: Fix Versal NET clock validation Michal Simek
2026-06-03 15:12 ` [PATCH v3 5/5] arm64: versal-net: Switch Versal NET to firmware clock interface Michal Simek
2026-06-03 15:47 ` sashiko-bot
2026-06-29 9:59 ` [PATCH v3 0/5] clock: versal-clk: Fix Versal NET clock binding and switch to CCF Michal Simek
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=350447fc-95c3-411c-934b-26fdb37c5860@amd.com \
--to=michal.simek@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@amd.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=mturquette@baylibre.com \
--cc=nava.kishore.manne@amd.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.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