dt-bindings: iio: adc: convert Xilinx XADC bindings to YAML
Subsystems (3)
PATCH 1/1 dt-bindings: iio: adc: convert Xilinx XADC bindings to YAML
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.
--- .../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
Documentation/devicetree/bindings/iio/adc/xilinx-xadc.txt deleted +0 -141
@@ -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; - }; - }; - };
Documentation/devicetree/bindings/iio/adc/xilinx-xadc.yaml new file +186 -0
186 lines not on this page · raw message
Signature · 5 lines
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
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).
Quoted 9 lines · On Sun, 5 Jul 2026 14:53:08 +0600 Avermoal <[email protected]> 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.yamlfile 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 <[email protected]>
Sign off with your real name (or a known identity) to comply with the DCO.
Quoted 7 lines
--- .../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]
Quoted 7 lines
Signature · 5 lines
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.
Signature · 2 lines
best regards, max
Quoted 3 lines · 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.
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
Quoted 9 lines
Quoted 3 lines
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
Quoted 10 lines · CDT Mikhail Lukianchikov
Quoted 9 lines
Quoted 3 lines
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
Quoted 7 lines
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()().
Quoted 10 lines
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.
Signature · 2 lines
best regards, max
Jonathan Cameron
maintainerQuoted 17 lines · On Sun, 05 Jul 2026 12:44:46 -0500 "Maxwell Doose" <[email protected]> wrote:
Quoted 14 lines · CDT Mikhail Lukianchikov
Quoted 9 lines
Quoted 3 lines
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.txtHello Krzyszof,
Thank you for feedback.
Quoted 8 lines
Quoted 3 lines
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! :)
Quoted 15 lines
Quoted 11 lines
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.
Quoted 17 lines · Mikhail Lukianchikov
Quoted 9 lines
Quoted 3 lines
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.txtHello Krzyszof,
Thank you for feedback.
I'm the newbie at Linux kernel developers community, and sorry for my mistakes in sending commits.
Quoted 6 lines
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