From: Rohan Mithari <rohanmithari09@gmail.com>
To: robh@kernel.org
Cc: krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
peng.hao2@zte.com.cn, Rohan Mithari <rohanmithari09@gmail.com>
Subject: [PATCH v2] dt-bindings: misc: convert pvpanic-mmio binding to YAML
Date: Fri, 29 May 2026 11:34:59 +0530 [thread overview]
Message-ID: <20260529060459.1053503-1-rohanmithari09@gmail.com> (raw)
Convert the legacy pvpanic-mmio txt binding into YAML schema
format for device tree validation support.
---
Changes in v2:
- Remove legacy txt binding
- Fix reg example format
- Add trailing newline
- Run checkpatch validation with --no-tree
Signed-off-by: Rohan Mithari <rohanmithari09@gmail.com>
---
.../devicetree/bindings/misc/pvpanic-mmio.txt | 29 ----------------
.../bindings/misc/qemu,pvpanic-mmio.yaml | 34 +++++++++++++++++++
2 files changed, 34 insertions(+), 29 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/misc/pvpanic-mmio.txt
create mode 100644 Documentation/devicetree/bindings/misc/qemu,pvpanic-mmio.yaml
diff --git a/Documentation/devicetree/bindings/misc/pvpanic-mmio.txt b/Documentation/devicetree/bindings/misc/pvpanic-mmio.txt
deleted file mode 100644
index 985e90736780..000000000000
--- a/Documentation/devicetree/bindings/misc/pvpanic-mmio.txt
+++ /dev/null
@@ -1,29 +0,0 @@
-* QEMU PVPANIC MMIO Configuration bindings
-
-QEMU's emulation / virtualization targets provide the following PVPANIC
-MMIO Configuration interface on the "virt" machine.
-type:
-
-- a read-write, 16-bit wide data register.
-
-QEMU exposes the data register to guests as memory mapped registers.
-
-Required properties:
-
-- compatible: "qemu,pvpanic-mmio".
-- reg: the MMIO region used by the device.
- * Bytes 0x0 Write panic event to the reg when guest OS panics.
- * Bytes 0x1 Reserved.
-
-Example:
-
-/ {
- #size-cells = <0x2>;
- #address-cells = <0x2>;
-
- pvpanic-mmio@9060000 {
- compatible = "qemu,pvpanic-mmio";
- reg = <0x0 0x9060000 0x0 0x2>;
- };
-};
-
diff --git a/Documentation/devicetree/bindings/misc/qemu,pvpanic-mmio.yaml b/Documentation/devicetree/bindings/misc/qemu,pvpanic-mmio.yaml
new file mode 100644
index 000000000000..fe24bdcacc9c
--- /dev/null
+++ b/Documentation/devicetree/bindings/misc/qemu,pvpanic-mmio.yaml
@@ -0,0 +1,34 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/misc/qemu,pvpanic-mmio.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: QEMU PVPANIC MMIO device
+
+description:
+ QEMU provides a pvpanic MMIO interface for guest panic notification.
+
+maintainers:
+ - Peng Hao <peng.hao2@zte.com.cn>
+
+properties:
+ compatible:
+ const: qemu,pvpanic-mmio
+
+ reg:
+ maxItems: 1
+
+required:
+ - compatible
+ - reg
+
+additionalProperties: false
+
+examples:
+ - |
+ pvpanic@9060000 {
+ compatible = "qemu,pvpanic-mmio";
+ reg = <0x9060000 0x2>;
+ };
+
--
2.34.1
next reply other threads:[~2026-05-29 6:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 6:04 Rohan Mithari [this message]
2026-05-29 7:56 ` [PATCH v2] dt-bindings: misc: convert pvpanic-mmio binding to YAML Krzysztof Kozlowski
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=20260529060459.1053503-1-rohanmithari09@gmail.com \
--to=rohanmithari09@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.hao2@zte.com.cn \
--cc=robh@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