From: "Rob Herring (Arm)" <robh@kernel.org>
To: Dileep Kumar Nagavarapu <dileepkumar.nagavarapu@amd.com>
Cc: michal.simek@amd.com, lars@metafoo.de, linux-iio@vger.kernel.org,
nuno.sa@analog.com, git@amd.com, pramod.nexgen@gmail.com,
linux-kernel@vger.kernel.org, jic23@kernel.org,
conor+dt@kernel.org, krzk+dt@kernel.org,
devicetree@vger.kernel.org, sai.krishna.potthuri@amd.com,
andy@kernel.org, dlechner@baylibre.com
Subject: Re: [PATCH v5] dt-bindings: iio: adc: Convert xilinx-xadc bindings to YAML schema
Date: Tue, 10 Nov 2026 12:40:03 -0600 [thread overview]
Message-ID: <179433600251.1216259.14459896909936066829.robh@kernel.org> (raw)
In-Reply-To: <20261107134955.1423727-1-dileepkumar.nagavarapu@amd.com>
On Sat, 07 Nov 2026 19:19:55 +0530, Dileep Kumar Nagavarapu wrote:
> From: Pramod Maurya <pramod.nexgen@gmail.com>
>
> Convert the Xilinx XADC and UltraScale System Monitor device tree binding
> from the legacy plain-text format to a YAML.
>
> The new binding covers the same hardware and compatible strings:
> - xlnx,zynq-xadc-1.00.a (ZYNQ hardblock)
> - xlnx,axi-xadc-1.00.a (AXI softblock)
> - xlnx,system-management-wiz-1.3 (UltraScale System Management Wizard)
>
> The xlnx,channels subnode retains its legacy name (including the comma)
> for backwards compatibility with existing device trees.
>
> Move xlnx,channels under properties, as dt-schema now allows node names
> containing a comma for long-established bindings.Constrain the reg
> property of the channel subnodes to the valid channel range of 0 to
> 16 with minimum and maximum.
>
> Drop the redundant "type: boolean" from xlnx,bipolar, since its $ref to
> the flag type already implies it.
>
> Signed-off-by: Pramod Maurya <pramod.nexgen@gmail.com>
> Co-developed-by: Dileep Kumar Nagavarapu <dileepkumar.nagavarapu@amd.com>
> Signed-off-by: Dileep Kumar Nagavarapu <dileepkumar.nagavarapu@amd.com>
> ---
> This patch was originally posted by Pramod Maurya.
>
> Link:https://lore.kernel.org/all/20260515075736.172172-2-pramod.nexgen@gmail.com/
>
> I will be maintaining the patch going forward and posting updated
> revisions.
>
> Changes in v5:
> - Simplify the commit message: drop the mention of automated validation
> and remove the dt-schema PR reference
> - Use "hardblock" and "softblock" instead of "hardmacro" and "softmacro"
> for the Zynq and AXI XADC variants
> - Drop the clock description
> (Comments from Jonathan Cameron)
> - Drop the "|" literal block indicator from the clocks and
> xlnx,external-mux descriptions, as the formatting does not need to be
> preserved
> - Add "default: none" for xlnx,external-mux and remove the sentence about
> the behavior when it is omitted
> - Reduce the examples to a single one. Remove the ZYNQ/AXI/UltraScale
> origin comments and the two redundant examples. Add xlnx,bipolar to
> a channel in the remaining example
> - Add Sai Krishna Potthuri and Dileep Kumar Nagavarapu as additional
> maintainers in the binding and the MAINTAINERS entry, alongside
> Lars-Peter Clausen
> (Comments from Sashiko AI review)
> - Constrain reg in the channel subnodes to the valid range 0-16 with
> minimum/maximum
> - Reword the commit message to describe the valid range constraint
> (minimum and maximum)
>
> Changes in v4:
> - Move xlnx,channels from patternProperties: to properties: per Rob
> Herring's guidance (keywords.yaml: "Fixed strings belong in properties")
> This requires a companion dt-schema update to add xlnx,channels as an
> object-type exception in vendor-props.yaml (like adi,channels).
> - Fix reg constraints inside channel subnodes: remove items block with
> minimum/maximum which is invalid for cell arrays per cell.yaml; the
> valid channel range (0-16) is documented in the description instead.
> - Remove redundant type: boolean from xlnx,bipolar; the $ref to
> /schemas/types.yaml#/definitions/flag already implies boolean type.
> - Fix patternProperties regex for channel subnodes to "^channel@([0-9a-f]|10)$"
> covering all valid hex unit addresses for channels 0-16.
>
> Changes in v3:
> - Move xlnx,channels from properties: to patternProperties: to satisfy
> vendor-props.yaml meta-schema (reversed in v4, see above)
>
> Changes in v2:
> - Fix patternProperties regex to use lowercase hex unit addresses
> - Add allOf/if/then conditional requiring xlnx,external-mux-channel
> when xlnx,external-mux is "single" or "dual"
> ---
> .../bindings/iio/adc/xilinx-xadc.txt | 141 ---------------
> .../bindings/iio/adc/xlnx,xadc.yaml | 165 ++++++++++++++++++
> MAINTAINERS | 9 +
> 3 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/xlnx,xadc.yaml
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
prev parent reply other threads:[~2026-11-10 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 13:49 Dileep Kumar Nagavarapu
2026-11-07 19:26 ` Jonathan Cameron
2026-11-10 18:40 ` Rob Herring (Arm) [this message]
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=179433600251.1216259.14459896909936066829.robh@kernel.org \
--to=robh@kernel.org \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dileepkumar.nagavarapu@amd.com \
--cc=dlechner@baylibre.com \
--cc=git@amd.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=nuno.sa@analog.com \
--cc=pramod.nexgen@gmail.com \
--cc=sai.krishna.potthuri@amd.com \
/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
all inboxes | Powered by JetHome®