From: Conor Dooley <conor.dooley@microchip.com>
To: <linusw@kernel.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, <linux-gpio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [RESEND PATCH v2 0/2] pinctrl property checks
Date: Tue, 24 Feb 2026 13:39:03 +0000 [thread overview]
Message-ID: <20260224-stimulate-fraying-29ac76f6c55e@wendy> (raw)
Hey Linus,
Here's a !rfc version of these property checks. Nothing has changed here
outside of a rebase on v7.0-rc1.
Resending because I managed to lose the CC list on all but the cover.
Cheers,
Conor.
CC: Linus Walleij <linusw@kernel.org>
CC: Rob Herring <robh@kernel.org>
CC: Krzysztof Kozlowski <krzk+dt@kernel.org>
CC: Conor Dooley <conor+dt@kernel.org>
CC: linux-gpio@vger.kernel.org
CC: devicetree@vger.kernel.org
CC: linux-kernel@vger.kernel.org
Conor Dooley (2):
pinctrl: pinconf-generic: perform basic checks on pincfg properties
dt-bindings: pinctrl: pincfg-node: add restrictions on conflicting
properties
.../bindings/pinctrl/pincfg-node.yaml | 105 ++++++++++++++++--
drivers/pinctrl/pinconf-generic.c | 41 ++++++-
2 files changed, 138 insertions(+), 8 deletions(-)
--
2.51.0
next reply other threads:[~2026-02-24 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 13:39 Conor Dooley [this message]
2026-02-24 13:39 ` [RESEND PATCH v2 1/2] pinctrl: pinconf-generic: perform basic checks on pincfg properties Conor Dooley
2026-02-24 13:39 ` [RESEND PATCH v2 2/2] dt-bindings: pinctrl: pincfg-node: add restrictions on conflicting properties Conor Dooley
2026-03-06 23:41 ` Rob Herring
2026-02-26 22:47 ` [RESEND PATCH v2 0/2] pinctrl property checks Linus Walleij
2026-02-28 0:41 ` Conor Dooley
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=20260224-stimulate-fraying-29ac76f6c55e@wendy \
--to=conor.dooley@microchip.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=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