[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260203-device-unwashed-ed24f8592d79@spud>
Date: Tue, 3 Feb 2026 17:29:41 +0000
From: Conor Dooley <conor@...nel.org>
To: linusw@...nel.org
Cc: conor@...nel.org,
Conor Dooley <conor.dooley@...rochip.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
linux-gpio@...r.kernel.org,
devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [rfc 0/2] pinctrl property checks
From: Conor Dooley <conor.dooley@...rochip.com>
Hey Linus,
Finally got around to sending the property stuff that we were talking
about. It's definitely not the best thing I have ever written, but I
think it does an okay job of warning about setups that don't make sense
while adding fairly little complexity wise.
Cheers,
Conor.
CC: Linus Walleij <linusw@...nel.org>
CC: Rob Herring <robh@...nel.org>
CC: Krzysztof Kozlowski <krzk+dt@...nel.org>
CC: Conor Dooley <conor+dt@...nel.org>
CC: linux-gpio@...r.kernel.org
CC: devicetree@...r.kernel.org
CC: linux-kernel@...r.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
Powered by blists - more mailing lists