* [PATCH] dt-bindings: iio: adc: convert Xilinx XADC bindings to YAML
@ 2026-07-05 6:34 Avermoal
2026-07-05 15:42 ` Krzysztof Kozlowski
0 siblings, 1 reply; 9+ messages in thread
From: Avermoal @ 2026-07-05 6:34 UTC (permalink / raw)
To: Jonathan Cameron
Cc: David Lechner, Nuno Sá, Andy Shevchenko, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Michal Simek, linux-iio,
devicetree, linux-arm-kernel, linux-kernel, Avermoal
Convert the Xilinx XADC binding documentation from .txt to YAML format.
This conversion is part of the ongoing effort to migrate all DT bindings
to a machine-verifiable schema.
The new xilinx-xadc.yaml file was created from the original .txt and
includes all necessary properties, descriptions, and examples. The
conversion also fixes a minor typo in the 'xlnx,channels' property name.
Signed-off-by: Avermoal <avermoal@gmail.com>
---
.../bindings/iio/adc/xilinx-xadc.txt | 141 --------------
.../bindings/iio/adc/xilinx-xadc.yaml | 174 ++++++++++++++++++
2 files changed, 174 insertions(+), 141 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/iio/adc/xilinx-xadc.txt
create mode 100644 Documentation/devicetree/bindings/iio/adc/xilinx-xadc.yaml
diff --git a/Documentation/devicetree/bindings/iio/adc/xilinx-xadc.txt b/Documentation/devicetree/bindings/iio/adc/xilinx-xadc.txt
deleted file mode 100644
index f42e18078376..000000000000
--- a/Documentation/devicetree/bindings/iio/adc/xilinx-xadc.txt
+++ /dev/null
@@ -1,141 +0,0 @@
-Xilinx XADC device driver
-
-This binding document describes the bindings for the Xilinx 7 Series XADC as well
-as the UltraScale/UltraScale+ System Monitor.
-
-The Xilinx XADC is an ADC that can be found in the Series 7 FPGAs from Xilinx.
-The XADC has a DRP interface for communication. Currently two different
-frontends for the DRP interface exist. One that is only available on the ZYNQ
-family as a hardmacro in the SoC portion of the ZYNQ. The other one is available
-on all series 7 platforms and is a softmacro with a AXI interface. This binding
-document describes the bindings for both of them since the bindings are very
-similar.
-
-The Xilinx System Monitor is an ADC that is found in the UltraScale and
-UltraScale+ FPGAs from Xilinx. The System Monitor provides a DRP interface for
-communication. Xilinx provides a standard IP core that can be used to access the
-System Monitor through an AXI interface in the FPGA fabric. This IP core is
-called the Xilinx System Management Wizard. This document describes the bindings
-for this IP.
-
-Required properties:
- - compatible: Should be one of
- * "xlnx,zynq-xadc-1.00.a": When using the ZYNQ device
- configuration interface to interface to the XADC hardmacro.
- * "xlnx,axi-xadc-1.00.a": When using the axi-xadc pcore to
- interface to the XADC hardmacro.
- * "xlnx,system-management-wiz-1.3": When using the
- Xilinx System Management Wizard fabric IP core to access the
- UltraScale and UltraScale+ System Monitor.
- - reg: Address and length of the register set for the device
- - interrupts: Interrupt for the XADC control interface.
- - clocks: When using the ZYNQ this must be the ZYNQ PCAP clock,
- when using the axi-xadc or the axi-system-management-wizard this must be
- the clock that provides the clock to the AXI bus interface of the core.
-
-Optional properties:
- - xlnx,external-mux:
- * "none": No external multiplexer is used, this is the default
- if the property is omitted.
- * "single": External multiplexer mode is used with one
- multiplexer.
- * "dual": External multiplexer mode is used with two
- multiplexers for simultaneous sampling.
- - xlnx,external-mux-channel: Configures which pair of pins is used to
- sample data in external mux mode.
- Valid values for single external multiplexer mode are:
- 0: VP/VN
- 1: VAUXP[0]/VAUXN[0]
- 2: VAUXP[1]/VAUXN[1]
- ...
- 16: VAUXP[15]/VAUXN[15]
- Valid values for dual external multiplexer mode are:
- 1: VAUXP[0]/VAUXN[0] - VAUXP[8]/VAUXN[8]
- 2: VAUXP[1]/VAUXN[1] - VAUXP[9]/VAUXN[9]
- ...
- 8: VAUXP[7]/VAUXN[7] - VAUXP[15]/VAUXN[15]
-
- This property needs to be present if the device is configured for
- external multiplexer mode (either single or dual). If the device is
- not using external multiplexer mode the property is ignored.
- - xnlx,channels: List of external channels that are connected to the ADC
- Required properties:
- * #address-cells: Should be 1.
- * #size-cells: Should be 0.
-
- The child nodes of this node represent the external channels which are
- connected to the ADC. If the property is no present no external
- channels will be assumed to be connected.
-
- Each child node represents one channel and has the following
- properties:
- Required properties:
- * reg: Pair of pins the channel is connected to.
- 0: VP/VN
- 1: VAUXP[0]/VAUXN[0]
- 2: VAUXP[1]/VAUXN[1]
- ...
- 16: VAUXP[15]/VAUXN[15]
- Note each channel number should only be used at most
- once.
- Optional properties:
- * xlnx,bipolar: If set the channel is used in bipolar
- mode.
-
-
-Examples:
- xadc@f8007100 {
- compatible = "xlnx,zynq-xadc-1.00.a";
- reg = <0xf8007100 0x20>;
- interrupts = <0 7 4>;
- interrupt-parent = <&gic>;
- clocks = <&pcap_clk>;
-
- xlnx,channels {
- #address-cells = <1>;
- #size-cells = <0>;
- channel@0 {
- reg = <0>;
- };
- channel@1 {
- reg = <1>;
- };
- channel@8 {
- reg = <8>;
- };
- };
- };
-
- xadc@43200000 {
- compatible = "xlnx,axi-xadc-1.00.a";
- reg = <0x43200000 0x1000>;
- interrupts = <0 53 4>;
- interrupt-parent = <&gic>;
- clocks = <&fpga1_clk>;
-
- xlnx,channels {
- #address-cells = <1>;
- #size-cells = <0>;
- channel@0 {
- reg = <0>;
- xlnx,bipolar;
- };
- };
- };
-
- adc@80000000 {
- compatible = "xlnx,system-management-wiz-1.3";
- reg = <0x80000000 0x1000>;
- interrupts = <0 81 4>;
- interrupt-parent = <&gic>;
- clocks = <&fpga1_clk>;
-
- xlnx,channels {
- #address-cells = <1>;
- #size-cells = <0>;
- channel@0 {
- reg = <0>;
- xlnx,bipolar;
- };
- };
- };
diff --git a/Documentation/devicetree/bindings/iio/adc/xilinx-xadc.yaml b/Documentation/devicetree/bindings/iio/adc/xilinx-xadc.yaml
new file mode 100644
index 000000000000..a32b712d8485
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/adc/xilinx-xadc.yaml
@@ -0,0 +1,174 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/adc/xilinx-xadc.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Xilinx 7 Series XADC and UltraScale/UltraScale+ System Monitor
+
+maintainers:
+ - Avermoal <avermoal@gmail.com>
+
+description: |
+ The Xilinx XADC is an ADC that can be found in the Series 7 FPGAs from Xilinx.
+ The XADC has a DRP interface for communication. Currently two different
+ frontends for the DRP interface exist. One that is only available on the ZYNQ
+ family as a hardmacro in the SoC portion of the ZYNQ. The other one is
+ available on all series 7 platforms and is a softmacro with an AXI interface.
+ This binding document describes the bindings for both of them since the
+ bindings are very similar.
+
+ The Xilinx System Monitor is an ADC that is found in the UltraScale and
+ UltraScale+ FPGAs from Xilinx. The System Monitor provides a DRP interface
+ for communication. Xilinx provides a standard IP core that can be used to
+ access the System Monitor through an AXI interface in the FPGA fabric.
+ This IP core is called the Xilinx System Management Wizard. This document
+ describes the bindings for this IP.
+
+properties:
+ compatible:
+ description: |
+ Specifies the interface type and the target device.
+ - "xlnx,zynq-xadc-1.00.a"
+ for ZYNQ device configuration interface (hardmacro in SoC)
+ - "xlnx,axi-xadc-1.00.a"
+ for AXI pcore softmacro on all Series 7 FPGAs
+ - "xlnx,system-management-wiz-1.3"
+ for UltraScale/UltraScale+ System Monitor via AXI
+ enum:
+ - xlnx,zynq-xadc-1.00.a
+ - xlnx,axi-xadc-1.00.a
+ - xlnx,system-management-wiz-1.3
+
+ reg:
+ description: Address and length of the register set for the device.
+ maxItems: 1
+
+ interrupts:
+ description: Interrupt for the XADC control interface.
+ maxItems: 1
+
+ clocks:
+ description: |
+ When using the ZYNQ this must be the ZYNQ PCAP clock,
+ when using the axi-xadc or the axi-system-management-wizard this must be
+ the clock that provides the clock to the AXI bus interface of the core.
+ maxItems: 1
+
+ xlnx,external-mux:
+ description: |
+ External multiplexer mode. If omitted, defaults to "none".
+ - "none" – no external multiplexer (default)
+ - "single" – one external multiplexer
+ - "dual" – two external multiplexers for simultaneous sampling
+ $ref: /schemas/types.yaml#/definitions/string
+ enum: [none, single, dual]
+ default: none
+
+ xlnx,external-mux-channel:
+ description: |
+ Configures which pair of pins is used to sample data in external mux mode.
+ For single mode: 0 (VP/VN) or 1..16 (VAUXP[0..15]/VAUXN[0..15]).
+ For dual mode: 1..8, where the value n corresponds to the pair
+ (VAUXP[n-1]/VAUXN[n-1] and VAUXP[n+7]/VAUXN[n+7]).
+ $ref: /schemas/types.yaml#/definitions/uint32
+ minimum: 0
+ maximum: 16
+
+ xlnx,channels:
+ description: |
+ Container for external channels that are connected to the ADC.
+ If this property is not present, no external channels will be assumed.
+ type: object
+ properties:
+ "#address-cells":
+ const: 1
+ "#size-cells":
+ const: 0
+ patternProperties:
+ "^channel@[0-9a-f]+$":
+ type: object
+ description: Each child node represents one external channel.
+ properties:
+ reg:
+ description: |
+ Pair of pins the channel is connected to.
+ 0: VP/VN
+ 1..16: VAUXP[0..15]/VAUXN[0..15]
+ $ref: /schemas/types.yaml#/definitions/uint32
+ minimum: 0
+ maximum: 16
+ xlnx,bipolar:
+ description: If present, the channel is used in bipolar mode.
+ type: boolean
+ required:
+ - reg
+ additionalProperties: false
+ additionalProperties: false
+
+required:
+ - compatible
+ - reg
+ - interrupts
+ - clocks
+
+unevaluatedProperties: false
+
+examples:
+ - |
+ xadc@f8007100 {
+ compatible = "xlnx,zynq-xadc-1.00.a";
+ reg = <0xf8007100 0x20>;
+ interrupts = <0 7 4>;
+ interrupt-parent = <&gic>;
+ clocks = <&pcap_clk>;
+
+ xlnx,channels {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ channel@0 {
+ reg = <0>;
+ };
+ channel@1 {
+ reg = <1>;
+ };
+ channel@8 {
+ reg = <8>;
+ };
+ };
+ };
+ - |
+ xadc@43200000 {
+ compatible = "xlnx,axi-xadc-1.00.a";
+ reg = <0x43200000 0x1000>;
+ interrupts = <0 53 4>;
+ interrupt-parent = <&gic>;
+ clocks = <&fpga1_clk>;
+
+ xlnx,channels {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ channel@0 {
+ reg = <0>;
+ xlnx,bipolar;
+ };
+ };
+ };
+ - |
+ adc@80000000 {
+ compatible = "xlnx,system-management-wiz-1.3";
+ reg = <0x80000000 0x1000>;
+ interrupts = <0 81 4>;
+ interrupt-parent = <&gic>;
+ clocks = <&fpga1_clk>;
+
+ xlnx,channels {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ channel@0 {
+ reg = <0>;
+ xlnx,bipolar;
+ };
+ };
+ };
+...
--
2.52.0
^ permalink raw reply related [flat|nested] 9+ messages in thread* Re: [PATCH] dt-bindings: iio: adc: convert Xilinx XADC bindings to YAML
2026-07-05 6:34 [PATCH] dt-bindings: iio: adc: convert Xilinx XADC bindings to YAML Avermoal
@ 2026-07-05 15:42 ` Krzysztof Kozlowski
0 siblings, 0 replies; 9+ messages in thread
From: Krzysztof Kozlowski @ 2026-07-05 15:42 UTC (permalink / raw)
To: Avermoal, Jonathan Cameron
Cc: David Lechner, Nuno Sá, Andy Shevchenko, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Michal Simek, linux-iio,
devicetree, linux-arm-kernel, linux-kernel
On 05/07/2026 08:34, Avermoal wrote:
> Convert the Xilinx XADC binding documentation from .txt to YAML format.
> This conversion is part of the ongoing effort to migrate all DT bindings
> to a machine-verifiable schema.
>
Don't duplicate.
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 9+ messages in thread
* [PATCH] dt-bindings: iio: adc: convert Xilinx XADC bindings to YAML
@ 2026-07-05 8:53 Avermoal
2026-07-05 15:04 ` Maxwell Doose
2026-07-05 15:42 ` Krzysztof Kozlowski
0 siblings, 2 replies; 9+ messages in thread
From: Avermoal @ 2026-07-05 8:53 UTC (permalink / raw)
To: Jonathan Cameron
Cc: David Lechner, Nuno Sá, Andy Shevchenko, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Michal Simek, linux-iio,
devicetree, linux-arm-kernel, linux-kernel, Avermoal
Convert the Xilinx XADC binding documentation from .txt to YAML format.
This conversion is part of the ongoing effort to migrate all DT bindings
to a machine-verifiable schema.
The new xilinx-xadc.yaml file was created from the original .txt and
includes all necessary properties, descriptions, and examples. The
conversion also fixes a minor typo in the 'xlnx,channels' property name.
Signed-off-by: Avermoal <avermoal@gmail.com>
---
.../bindings/iio/adc/xilinx-xadc.txt | 141 -------------
.../bindings/iio/adc/xilinx-xadc.yaml | 186 ++++++++++++++++++
2 files changed, 186 insertions(+), 141 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/iio/adc/xilinx-xadc.txt
create mode 100644 Documentation/devicetree/bindings/iio/adc/xilinx-xadc.yaml
diff --git a/Documentation/devicetree/bindings/iio/adc/xilinx-xadc.txt b/Documentation/devicetree/bindings/iio/adc/xilinx-xadc.txt
deleted file mode 100644
index f42e18078376..000000000000
--- a/Documentation/devicetree/bindings/iio/adc/xilinx-xadc.txt
+++ /dev/null
@@ -1,141 +0,0 @@
-Xilinx XADC device driver
-
-This binding document describes the bindings for the Xilinx 7 Series XADC as well
-as the UltraScale/UltraScale+ System Monitor.
-
-The Xilinx XADC is an ADC that can be found in the Series 7 FPGAs from Xilinx.
-The XADC has a DRP interface for communication. Currently two different
-frontends for the DRP interface exist. One that is only available on the ZYNQ
-family as a hardmacro in the SoC portion of the ZYNQ. The other one is available
-on all series 7 platforms and is a softmacro with a AXI interface. This binding
-document describes the bindings for both of them since the bindings are very
-similar.
-
-The Xilinx System Monitor is an ADC that is found in the UltraScale and
-UltraScale+ FPGAs from Xilinx. The System Monitor provides a DRP interface for
-communication. Xilinx provides a standard IP core that can be used to access the
-System Monitor through an AXI interface in the FPGA fabric. This IP core is
-called the Xilinx System Management Wizard. This document describes the bindings
-for this IP.
-
-Required properties:
- - compatible: Should be one of
- * "xlnx,zynq-xadc-1.00.a": When using the ZYNQ device
- configuration interface to interface to the XADC hardmacro.
- * "xlnx,axi-xadc-1.00.a": When using the axi-xadc pcore to
- interface to the XADC hardmacro.
- * "xlnx,system-management-wiz-1.3": When using the
- Xilinx System Management Wizard fabric IP core to access the
- UltraScale and UltraScale+ System Monitor.
- - reg: Address and length of the register set for the device
- - interrupts: Interrupt for the XADC control interface.
- - clocks: When using the ZYNQ this must be the ZYNQ PCAP clock,
- when using the axi-xadc or the axi-system-management-wizard this must be
- the clock that provides the clock to the AXI bus interface of the core.
-
-Optional properties:
- - xlnx,external-mux:
- * "none": No external multiplexer is used, this is the default
- if the property is omitted.
- * "single": External multiplexer mode is used with one
- multiplexer.
- * "dual": External multiplexer mode is used with two
- multiplexers for simultaneous sampling.
- - xlnx,external-mux-channel: Configures which pair of pins is used to
- sample data in external mux mode.
- Valid values for single external multiplexer mode are:
- 0: VP/VN
- 1: VAUXP[0]/VAUXN[0]
- 2: VAUXP[1]/VAUXN[1]
- ...
- 16: VAUXP[15]/VAUXN[15]
- Valid values for dual external multiplexer mode are:
- 1: VAUXP[0]/VAUXN[0] - VAUXP[8]/VAUXN[8]
- 2: VAUXP[1]/VAUXN[1] - VAUXP[9]/VAUXN[9]
- ...
- 8: VAUXP[7]/VAUXN[7] - VAUXP[15]/VAUXN[15]
-
- This property needs to be present if the device is configured for
- external multiplexer mode (either single or dual). If the device is
- not using external multiplexer mode the property is ignored.
- - xnlx,channels: List of external channels that are connected to the ADC
- Required properties:
- * #address-cells: Should be 1.
- * #size-cells: Should be 0.
-
- The child nodes of this node represent the external channels which are
- connected to the ADC. If the property is no present no external
- channels will be assumed to be connected.
-
- Each child node represents one channel and has the following
- properties:
- Required properties:
- * reg: Pair of pins the channel is connected to.
- 0: VP/VN
- 1: VAUXP[0]/VAUXN[0]
- 2: VAUXP[1]/VAUXN[1]
- ...
- 16: VAUXP[15]/VAUXN[15]
- Note each channel number should only be used at most
- once.
- Optional properties:
- * xlnx,bipolar: If set the channel is used in bipolar
- mode.
-
-
-Examples:
- xadc@f8007100 {
- compatible = "xlnx,zynq-xadc-1.00.a";
- reg = <0xf8007100 0x20>;
- interrupts = <0 7 4>;
- interrupt-parent = <&gic>;
- clocks = <&pcap_clk>;
-
- xlnx,channels {
- #address-cells = <1>;
- #size-cells = <0>;
- channel@0 {
- reg = <0>;
- };
- channel@1 {
- reg = <1>;
- };
- channel@8 {
- reg = <8>;
- };
- };
- };
-
- xadc@43200000 {
- compatible = "xlnx,axi-xadc-1.00.a";
- reg = <0x43200000 0x1000>;
- interrupts = <0 53 4>;
- interrupt-parent = <&gic>;
- clocks = <&fpga1_clk>;
-
- xlnx,channels {
- #address-cells = <1>;
- #size-cells = <0>;
- channel@0 {
- reg = <0>;
- xlnx,bipolar;
- };
- };
- };
-
- adc@80000000 {
- compatible = "xlnx,system-management-wiz-1.3";
- reg = <0x80000000 0x1000>;
- interrupts = <0 81 4>;
- interrupt-parent = <&gic>;
- clocks = <&fpga1_clk>;
-
- xlnx,channels {
- #address-cells = <1>;
- #size-cells = <0>;
- channel@0 {
- reg = <0>;
- xlnx,bipolar;
- };
- };
- };
diff --git a/Documentation/devicetree/bindings/iio/adc/xilinx-xadc.yaml b/Documentation/devicetree/bindings/iio/adc/xilinx-xadc.yaml
new file mode 100644
index 000000000000..d61635516ce2
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/adc/xilinx-xadc.yaml
@@ -0,0 +1,186 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/adc/xilinx-xadc.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Xilinx 7 Series XADC and UltraScale/UltraScale+ System Monitor
+
+maintainers:
+ - Avermoal <avermoal@gmail.com>
+
+description: |
+ The Xilinx XADC is an ADC that can be found in the Series 7 FPGAs from Xilinx.
+ The XADC has a DRP interface for communication. Currently two different
+ frontends for the DRP interface exist. One that is only available on the ZYNQ
+ family as a hardmacro in the SoC portion of the ZYNQ. The other one is
+ available on all series 7 platforms and is a softmacro with an AXI interface.
+ This binding document describes the bindings for both of them since the
+ bindings are very similar.
+
+ The Xilinx System Monitor is an ADC that is found in the UltraScale and
+ UltraScale+ FPGAs from Xilinx. The System Monitor provides a DRP interface
+ for communication. Xilinx provides a standard IP core that can be used to
+ access the System Monitor through an AXI interface in the FPGA fabric.
+ This IP core is called the Xilinx System Management Wizard. This document
+ describes the bindings for this IP.
+
+properties:
+ compatible:
+ description: |
+ Specifies the interface type and the target device.
+ - "xlnx,zynq-xadc-1.00.a"
+ for ZYNQ device configuration interface (hardmacro in SoC)
+ - "xlnx,axi-xadc-1.00.a"
+ for AXI pcore softmacro on all Series 7 FPGAs
+ - "xlnx,system-management-wiz-1.3"
+ for UltraScale/UltraScale+ System Monitor via AXI
+ enum:
+ - xlnx,zynq-xadc-1.00.a
+ - xlnx,axi-xadc-1.00.a
+ - xlnx,system-management-wiz-1.3
+
+ reg:
+ description: Address and length of the register set for the device.
+ maxItems: 1
+
+ interrupts:
+ description: Interrupt for the XADC control interface.
+ maxItems: 1
+
+ clocks:
+ description: |
+ When using the ZYNQ this must be the ZYNQ PCAP clock,
+ when using the axi-xadc or the axi-system-management-wizard this must be
+ the clock that provides the clock to the AXI bus interface of the core.
+ maxItems: 1
+
+ xlnx,external-mux:
+ description: |
+ External multiplexer mode. If omitted, defaults to "none".
+ - "none" – no external multiplexer (default)
+ - "single" – one external multiplexer
+ - "dual" – two external multiplexers for simultaneous sampling
+ $ref: /schemas/types.yaml#/definitions/string
+ enum: [none, single, dual]
+ default: none
+
+ xlnx,external-mux-channel:
+ description: |
+ Configures which pair of pins is used to sample data in external mux mode.
+ For single mode: 0 (VP/VN) or 1..16 (VAUXP[0..15]/VAUXN[0..15]).
+ For dual mode: 1..8, where the value n corresponds to the pair
+ (VAUXP[n-1]/VAUXN[n-1] and VAUXP[n+7]/VAUXN[n+7]).
+ $ref: /schemas/types.yaml#/definitions/uint32
+ minimum: 0
+ maximum: 16
+
+ xlnx,channels:
+ description: |
+ Container for external channels that are connected to the ADC.
+ If this property is not present, no external channels will be assumed.
+ type: object
+ properties:
+ "#address-cells":
+ const: 1
+ "#size-cells":
+ const: 0
+ patternProperties:
+ "^channel@[0-9a-f]+$":
+ type: object
+ description: Each child node represents one external channel.
+ properties:
+ reg:
+ description: |
+ Pair of pins the channel is connected to.
+ 0: VP/VN
+ 1..16: VAUXP[0..15]/VAUXN[0..15]
+ maxItems: 1
+ xlnx,bipolar:
+ description: If present, the channel is used in bipolar mode.
+ type: boolean
+ required:
+ - reg
+ additionalProperties: false
+ required:
+ - "#address-cells"
+ - "#size-cells"
+ additionalProperties: false
+
+allOf:
+ - if:
+ required:
+ - xlnx,external-mux
+ properties:
+ xlnx,external-mux:
+ enum: [single, dual]
+ then:
+ required:
+ - xlnx,external-mux-channel
+
+required:
+ - compatible
+ - reg
+ - interrupts
+ - clocks
+
+additionalProperties: false
+
+examples:
+ - |
+ xadc@f8007100 {
+ compatible = "xlnx,zynq-xadc-1.00.a";
+ reg = <0xf8007100 0x20>;
+ interrupts = <0 7 4>;
+ interrupt-parent = <&gic>;
+ clocks = <&pcap_clk>;
+
+ xlnx,channels {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ channel@0 {
+ reg = <0>;
+ };
+ channel@1 {
+ reg = <1>;
+ };
+ channel@8 {
+ reg = <8>;
+ };
+ };
+ };
+ - |
+ xadc@43200000 {
+ compatible = "xlnx,axi-xadc-1.00.a";
+ reg = <0x43200000 0x1000>;
+ interrupts = <0 53 4>;
+ interrupt-parent = <&gic>;
+ clocks = <&fpga1_clk>;
+
+ xlnx,channels {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ channel@0 {
+ reg = <0>;
+ xlnx,bipolar;
+ };
+ };
+ };
+ - |
+ adc@80000000 {
+ compatible = "xlnx,system-management-wiz-1.3";
+ reg = <0x80000000 0x1000>;
+ interrupts = <0 81 4>;
+ interrupt-parent = <&gic>;
+ clocks = <&fpga1_clk>;
+
+ xlnx,channels {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ channel@0 {
+ reg = <0>;
+ xlnx,bipolar;
+ };
+ };
+ };
+...
--
Changes in v2:
- Fix conditional requirement for xlnx,external-mux-channel (add if/required block)
- Correct reg type in child nodes (use maxItems: 1 instead of items)
- Make #address-cells and #size-cells required under xlnx,channels
2.52.0
^ permalink raw reply related [flat|nested] 9+ messages in thread* Re: [PATCH] dt-bindings: iio: adc: convert Xilinx XADC bindings to YAML
2026-07-05 8:53 Avermoal
@ 2026-07-05 15:04 ` Maxwell Doose
2026-07-05 15:42 ` Krzysztof Kozlowski
1 sibling, 0 replies; 9+ messages in thread
From: Maxwell Doose @ 2026-07-05 15:04 UTC (permalink / raw)
To: Avermoal
Cc: Jonathan Cameron, David Lechner, Nuno Sá, Andy Shevchenko,
Rob Herring, Krzysztof Kozlowski, Conor Dooley, Michal Simek,
linux-iio, devicetree, linux-arm-kernel, linux-kernel
Hi there,
Firstly, please wait around 24hrs before sending a new version and
additionally mark it with [PATCH vX] (where X is the version of the
patch you're sending, which in this case appears to be 2).
On Sun, 5 Jul 2026 14:53:08 +0600
Avermoal <avermoal@gmail.com> wrote:
> Convert the Xilinx XADC binding documentation from .txt to YAML format.
> This conversion is part of the ongoing effort to migrate all DT bindings
> to a machine-verifiable schema.
>
> The new xilinx-xadc.yaml file was created from the original .txt and
> includes all necessary properties, descriptions, and examples. The
> conversion also fixes a minor typo in the 'xlnx,channels' property name.
>
> Signed-off-by: Avermoal <avermoal@gmail.com>
Sign off with your real name (or a known identity) to comply with the
DCO.
> ---
> .../bindings/iio/adc/xilinx-xadc.txt | 141 -------------
> .../bindings/iio/adc/xilinx-xadc.yaml | 186 ++++++++++++++++++
> 2 files changed, 186 insertions(+), 141 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/iio/adc/xilinx-xadc.txt
> create mode 100644 Documentation/devicetree/bindings/iio/adc/xilinx-xadc.yaml
>
[snip]
> --
>
> Changes in v2:
> - Fix conditional requirement for xlnx,external-mux-channel (add
> if/required block)
> - Correct reg type in child nodes (use maxItems: 1 instead of items)
> - Make #address-cells and #size-cells required under xlnx,channels
Also put this at the top under the ---, it's very difficult to scroll
all the way down here to read it.
--
best regards,
max
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] dt-bindings: iio: adc: convert Xilinx XADC bindings to YAML
2026-07-05 8:53 Avermoal
2026-07-05 15:04 ` Maxwell Doose
@ 2026-07-05 15:42 ` Krzysztof Kozlowski
2026-07-05 16:56 ` Mikhail Lukianchikov
1 sibling, 1 reply; 9+ messages in thread
From: Krzysztof Kozlowski @ 2026-07-05 15:42 UTC (permalink / raw)
To: Avermoal, Jonathan Cameron
Cc: David Lechner, Nuno Sá, Andy Shevchenko, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Michal Simek, linux-iio,
devicetree, linux-arm-kernel, linux-kernel
On 05/07/2026 10:53, Avermoal wrote:
> Convert the Xilinx XADC binding documentation from .txt to YAML format.
> This conversion is part of the ongoing effort to migrate all DT bindings
> to a machine-verifiable schema.
Sorry, but what effort exactly? Where is this effort documented? Do you
have a mentor if this is some sort of mentorship effort?
And if this is ongoing effort then don't duplicate:
https://lore.kernel.org/all/?q=dfn%3Axilinx-xadc.txt
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] dt-bindings: iio: adc: convert Xilinx XADC bindings to YAML
2026-07-05 15:42 ` Krzysztof Kozlowski
@ 2026-07-05 16:56 ` Mikhail Lukianchikov
2026-07-05 17:44 ` Maxwell Doose
2026-07-06 5:56 ` Krzysztof Kozlowski
0 siblings, 2 replies; 9+ messages in thread
From: Mikhail Lukianchikov @ 2026-07-05 16:56 UTC (permalink / raw)
To: Krzysztof Kozlowski
Cc: Jonathan Cameron, David Lechner, Nuno Sá, Andy Shevchenko,
Rob Herring, Conor Dooley, Michal Simek, linux-iio, devicetree,
linux-arm-kernel, linux-kernel
>> Convert the Xilinx XADC binding documentation from .txt to YAML format.
>> This conversion is part of the ongoing effort to migrate all DT bindings
>> to a machine-verifiable schema.
>
>Sorry, but what effort exactly? Where is this effort documented? Do you
>have a mentor if this is some sort of mentorship effort?
>
>And if this is ongoing effort then don't duplicate:
>https://lore.kernel.org/all/?q=dfn%3Axilinx-xadc.txt
Hello Krzyszof,
Thank you for feedback.
I'm the newbie at Linux kernel developers community,
and sorry for my mistakes in sending commits.
I'll answer your questions.
I am not part of any official mentorship program,
I just decided to try to contribute to the development of the Linux kernel.
Yes, it's a ongoing effort, and to be honest, this effort is the general
community initiative to convert all DT bindings from .txt to .yaml. I didn't know that work
on this file was already underway.
Tell me, should I continue working in this case?
Best regards
Mikhail
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] dt-bindings: iio: adc: convert Xilinx XADC bindings to YAML
2026-07-05 16:56 ` Mikhail Lukianchikov
@ 2026-07-05 17:44 ` Maxwell Doose
2026-07-05 23:04 ` Jonathan Cameron
2026-07-06 5:56 ` Krzysztof Kozlowski
1 sibling, 1 reply; 9+ messages in thread
From: Maxwell Doose @ 2026-07-05 17:44 UTC (permalink / raw)
To: Mikhail Lukianchikov, Krzysztof Kozlowski
Cc: Jonathan Cameron, David Lechner, Nuno Sá, Andy Shevchenko,
Rob Herring, Conor Dooley, Michal Simek, linux-iio, devicetree,
linux-arm-kernel, linux-kernel
On Sun Jul 5, 2026 at 11:56 AM CDT
Mikhail Lukianchikov <avermoal@gmail.com> wrote:
>>> Convert the Xilinx XADC binding documentation from .txt to YAML format.
>>> This conversion is part of the ongoing effort to migrate all DT bindings
>>> to a machine-verifiable schema.
>>
>>Sorry, but what effort exactly? Where is this effort documented? Do you
>>have a mentor if this is some sort of mentorship effort?
>>
>>And if this is ongoing effort then don't duplicate:
>>https://lore.kernel.org/all/?q=dfn%3Axilinx-xadc.txt
>
> Hello Krzyszof,
>
> Thank you for feedback.
>
> I'm the newbie at Linux kernel developers community,
> and sorry for my mistakes in sending commits.
>
No worries, we've all done it at some point. If you're looking for stuff
to do then the todo in drivers/iio/ was just recently updated. There are
still a handful of drivers also in iio that still need conversions to
guard()().
>
> I'll answer your questions.
> I am not part of any official mentorship program,
> I just decided to try to contribute to the development of the Linux kernel.
> Yes, it's a ongoing effort, and to be honest, this effort is the general
> community initiative to convert all DT bindings from .txt to .yaml. I didn't know that work
> on this file was already underway.
>
> Tell me, should I continue working in this case?
>
After looking at the link Krzysztof sent you it looks like it's already
being done, so I'd recommend dropping this one.
--
best regards,
max
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] dt-bindings: iio: adc: convert Xilinx XADC bindings to YAML
2026-07-05 17:44 ` Maxwell Doose
@ 2026-07-05 23:04 ` Jonathan Cameron
0 siblings, 0 replies; 9+ messages in thread
From: Jonathan Cameron @ 2026-07-05 23:04 UTC (permalink / raw)
To: Maxwell Doose
Cc: Mikhail Lukianchikov, Krzysztof Kozlowski, David Lechner,
Nuno Sá, Andy Shevchenko, Rob Herring, Conor Dooley,
Michal Simek, linux-iio, devicetree, linux-arm-kernel,
linux-kernel
On Sun, 05 Jul 2026 12:44:46 -0500
"Maxwell Doose" <m32285159@gmail.com> wrote:
> On Sun Jul 5, 2026 at 11:56 AM CDT
> Mikhail Lukianchikov <avermoal@gmail.com> wrote:
>
> >>> Convert the Xilinx XADC binding documentation from .txt to YAML format.
> >>> This conversion is part of the ongoing effort to migrate all DT bindings
> >>> to a machine-verifiable schema.
> >>
> >>Sorry, but what effort exactly? Where is this effort documented? Do you
> >>have a mentor if this is some sort of mentorship effort?
> >>
> >>And if this is ongoing effort then don't duplicate:
> >>https://lore.kernel.org/all/?q=dfn%3Axilinx-xadc.txt
> >
> > Hello Krzyszof,
> >
> > Thank you for feedback.
> >
> > I'm the newbie at Linux kernel developers community,
> > and sorry for my mistakes in sending commits.
> >
>
> No worries, we've all done it at some point. If you're looking for stuff
> to do then the todo in drivers/iio/ was just recently updated. There are
> still a handful of drivers also in iio that still need conversions to
> guard()().
Tweak that to 'may benefit from'. I don't want people doing that blindly
with assumption it is always a good idea! :)
>
> >
> > I'll answer your questions.
> > I am not part of any official mentorship program,
> > I just decided to try to contribute to the development of the Linux kernel.
> > Yes, it's a ongoing effort, and to be honest, this effort is the general
> > community initiative to convert all DT bindings from .txt to .yaml. I didn't know that work
> > on this file was already underway.
> >
> > Tell me, should I continue working in this case?
> >
>
> After looking at the link Krzysztof sent you it looks like it's already
> being done, so I'd recommend dropping this one.
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCH] dt-bindings: iio: adc: convert Xilinx XADC bindings to YAML
2026-07-05 16:56 ` Mikhail Lukianchikov
2026-07-05 17:44 ` Maxwell Doose
@ 2026-07-06 5:56 ` Krzysztof Kozlowski
1 sibling, 0 replies; 9+ messages in thread
From: Krzysztof Kozlowski @ 2026-07-06 5:56 UTC (permalink / raw)
To: Mikhail Lukianchikov, Krzysztof Kozlowski
Cc: Jonathan Cameron, David Lechner, Nuno Sá, Andy Shevchenko,
Rob Herring, Conor Dooley, Michal Simek, linux-iio, devicetree,
linux-arm-kernel, linux-kernel
On 05/07/2026 18:56, Mikhail Lukianchikov wrote:
>>> Convert the Xilinx XADC binding documentation from .txt to YAML format.
>>> This conversion is part of the ongoing effort to migrate all DT bindings
>>> to a machine-verifiable schema.
>>
>> Sorry, but what effort exactly? Where is this effort documented? Do you
>> have a mentor if this is some sort of mentorship effort?
>>
>> And if this is ongoing effort then don't duplicate:
>> https://lore.kernel.org/all/?q=dfn%3Axilinx-xadc.txt
>
> Hello Krzyszof,
>
> Thank you for feedback.
>
> I'm the newbie at Linux kernel developers community,
> and sorry for my mistakes in sending commits.
>
> I'll answer your questions.
> I am not part of any official mentorship program,
> I just decided to try to contribute to the development of the Linux kernel.
> Yes, it's a ongoing effort, and to be honest, this effort is the general
> community initiative to convert all DT bindings from .txt to .yaml. I didn't know that work
> on this file was already underway.
Take a look at other commits to learn how the commit msg could be written.
In any case,
1. Do not send duplicated versions of patches (you posted same twice).
2. Check if that binding was converted already.
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2026-07-06 5:56 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-05 6:34 [PATCH] dt-bindings: iio: adc: convert Xilinx XADC bindings to YAML Avermoal
2026-07-05 15:42 ` Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2026-07-05 8:53 Avermoal
2026-07-05 15:04 ` Maxwell Doose
2026-07-05 15:42 ` Krzysztof Kozlowski
2026-07-05 16:56 ` Mikhail Lukianchikov
2026-07-05 17:44 ` Maxwell Doose
2026-07-05 23:04 ` Jonathan Cameron
2026-07-06 5:56 ` Krzysztof Kozlowski
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox