From: Rohit Visavalia <rohit.visavalia@amd.com>
To: <mturquette@baylibre.com>, <sboyd@kernel.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>
Cc: <linux-clk@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Rohit Visavalia <rohit.visavalia@amd.com>
Subject: [PATCH 0/3] dt-bindings: clock: xilinx: Update VCU bindings
Date: Thu, 2 Jan 2025 08:36:57 -0800 [thread overview]
Message-ID: <20250102163700.759712-1-rohit.visavalia@amd.com> (raw)
This patch series converts dt-binding to dtschema and adds reset GPIO
as optional property.
Rohit Visavalia (3):
dt-bindings: clock: xilinx: move xlnx_vcu dt-binding to clock from soc
dt-bindings: clock: xilinx: Convert VCU bindings to dtschema
dt-bindings: clock: xilinx: Update VCU bindings for reset GPIO
.../devicetree/bindings/clock/xlnx,vcu.yaml | 64 +++++++++++++++++++
.../bindings/soc/xilinx/xlnx,vcu.txt | 26 --------
2 files changed, 64 insertions(+), 26 deletions(-)
create mode 100644 Documentation/devicetree/bindings/clock/xlnx,vcu.yaml
delete mode 100644 Documentation/devicetree/bindings/soc/xilinx/xlnx,vcu.txt
--
2.25.1
next reply other threads:[~2025-01-02 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 16:36 Rohit Visavalia [this message]
2025-01-02 16:36 ` [PATCH 1/3] dt-bindings: clock: xilinx: move xlnx_vcu dt-binding to clock from soc Rohit Visavalia
2025-01-02 18:30 ` Krzysztof Kozlowski
2025-01-03 11:35 ` Visavalia, Rohit
2025-01-02 16:36 ` [PATCH 2/3] dt-bindings: clock: xilinx: Convert VCU bindings to dtschema Rohit Visavalia
2025-01-02 18:26 ` Krzysztof Kozlowski
2025-01-03 11:35 ` Visavalia, Rohit
2025-01-02 16:37 ` [PATCH 3/3] dt-bindings: clock: xilinx: Update VCU bindings for reset GPIO Rohit Visavalia
2025-01-02 18:29 ` Krzysztof Kozlowski
2025-01-03 11:35 ` Visavalia, Rohit
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=20250102163700.759712-1-rohit.visavalia@amd.com \
--to=rohit.visavalia@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.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