mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Udaya Kiran Challa <challauday369@gmail.com>
Cc: conor+dt@kernel.org, me@brighamcampbell.com,
	skhan@linuxfoundation.org, linusw@kernel.org,
	linux-gpio@vger.kernel.org, krzk+dt@kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] dt-bindings: pinctrl: microchip,pic32mzda-pinctrl: Convert to DT schema
Date: Mon, 3 Aug 2026 17:24:08 -0500	[thread overview]
Message-ID: <178579584771.736715.6031577704790719107.robh@kernel.org> (raw)
In-Reply-To: <20260731174551.86367-1-challauday369@gmail.com>


On Fri, 31 Jul 2026 23:15:51 +0530, Udaya Kiran Challa wrote:
> Convert Microchip PIC32 Pin Controller devicetree binding
> from legacy text format to DT schema.
> 
> Signed-off-by: Udaya Kiran Challa <challauday369@gmail.com>
> ---
> Changelog:
> Changes since v4:
> - Add reference to pincfg-node.yaml
> 
> Link to v4:https://lore.kernel.org/all/20260722123243.341346-1-challauday369@gmail.com/
> 
> Changes since v3:
> - Drop "|" from description fields
> - Remove '#address-cells' and '#size-cells' properties from the schema
> - Consolidate repeated pin-node property definitions into a single
>   $defs/pin-node entry
> - Replace the two patternProperties blocks with additionalProperties
>   using oneOf to allow either:
>   - container nodes holding nested pin configuration nodes, or
>   - direct pin configuration nodes.
> - Update $ref to use the absolute schema path
>   /schemas/pinctrl/pinmux-node.yaml#
> 
> Link to v3:https://lore.kernel.org/all/20260719183431.124061-1-challauday369@gmail.com/
> 
> Changes since v2:
> - Add container node for grouped pin configuration sub-nodes
> - Correct regex patterns of direct and nested child nodes
> - Fix interrupts values in uart2 example
> 
> Link to v2:https://lore.kernel.org/all/20260707144223.120417-1-challauday369@gmail.com/
> 
> Changes since v1:
> - Add interrupts and clocks to uart2 example to satisfy uart schema validation
> - Corect regex patterns to accept standard DT node naming conventions
> - Add function property to top-level pin configuration nodes
> - Remove restrictive enum from function property to support all mux functions
> 
> Link to v1:https://lore.kernel.org/all/20260705132521.159522-1-challauday369@gmail.com/
> ---
>  .../pinctrl/microchip,pic32-pinctrl.txt       |  60 ----------
>  .../pinctrl/microchip,pic32mzda-pinctrl.yaml  | 109 ++++++++++++++++++
>  2 files changed, 109 insertions(+), 60 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/pinctrl/microchip,pic32-pinctrl.txt
>  create mode 100644 Documentation/devicetree/bindings/pinctrl/microchip,pic32mzda-pinctrl.yaml
> 

Reviewed-by: Rob Herring (Arm) <robh@kernel.org>


  reply	other threads:[~2026-08-03 22:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31 17:45 Udaya Kiran Challa
2026-08-03 22:24 ` Rob Herring (Arm) [this message]
2026-08-13 17:30   ` Uday Kiran
2026-08-14  7:13     ` Linus Walleij
2026-08-14  7:11 ` Linus Walleij

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=178579584771.736715.6031577704790719107.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=challauday369@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@brighamcampbell.com \
    --cc=skhan@linuxfoundation.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

all inboxes | Powered by JetHome®