From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linusw@kernel.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v1 0/3] pinctrl: pinconf-generic: More fwnode related conversions
Date: Tue, 17 Mar 2026 11:36:10 +0100 [thread overview]
Message-ID: <20260317103817.1982584-1-andriy.shevchenko@linux.intel.com> (raw)
While I have noticed some inconsistencies in the pinconf-generic code,
I also found one minor issue and a room to convert the code to use
fwnode APIs instead of being too OF-centric. This might help in the future
to use similar data structures in software nodes.
Andy Shevchenko (3):
pinctrl: pinconf-generic: Fully validate 'pinmux' property
pinctrl: pinconf-generic: Validate fwnode instead of device node
pinctrl: pinconf-generic: Convert ..._parse_dt_pinmux() to fwnode API
drivers/pinctrl/pinconf-generic.c | 37 ++++++++++++++++++-------------
1 file changed, 22 insertions(+), 15 deletions(-)
--
2.50.1
next reply other threads:[~2026-03-17 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 10:36 Andy Shevchenko [this message]
2026-03-17 10:36 ` [PATCH v1 1/3] pinctrl: pinconf-generic: Fully validate 'pinmux' property Andy Shevchenko
2026-03-17 10:36 ` [PATCH v1 2/3] pinctrl: pinconf-generic: Validate fwnode instead of device node Andy Shevchenko
2026-03-17 10:36 ` [PATCH v1 3/3] pinctrl: pinconf-generic: Convert ..._parse_dt_pinmux() to fwnode API Andy Shevchenko
2026-03-19 18:22 ` [PATCH v1 0/3] pinctrl: pinconf-generic: More fwnode related conversions 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=20260317103817.1982584-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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