From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jacky Huang <ychuang3@nuvoton.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Tomer Maimon <tmaimon77@gmail.com>,
linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, openbmc@lists.ozlabs.org
Cc: "Shan-Chun Hung" <schung@nuvoton.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Avi Fishman" <avifishman70@gmail.com>,
"Tali Perry" <tali.perry1@gmail.com>,
"Patrick Venture" <venture@google.com>,
"Nancy Yuen" <yuenn@google.com>,
"Benjamin Fair" <benjaminfair@google.com>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v2 0/5] pinctrl: nuvoton: A few cleanups and a fix
Date: Tue, 18 Mar 2025 12:57:13 +0200 [thread overview]
Message-ID: <20250318105932.2090926-1-andriy.shevchenko@linux.intel.com> (raw)
Convert Nuvoton drivers to use pin control provided data types
and more of device property APIs.
While doing that, fix one non-critical issue that sparse complains about.
Compile tested only.
In v2:
- fixed compilation errors and warnings (LKP)
- collected tags (Jonathan)
Andy Shevchenko (5):
pinctrl: npcm8xx: Fix incorrect struct npcm8xx_pincfg assignment
pinctrl: nuvoton: Convert to use struct pingroup and
PINCTRL_PINGROUP()
pinctrl: nuvoton: Make use of struct pinfunction and
PINCTRL_PINFUNCTION()
pinctrl: nuvoton: Convert to use struct group_desc
pinctrl: nuvoton: Reduce use of OF-specific APIs
drivers/pinctrl/nuvoton/pinctrl-ma35.c | 120 ++++++++++------------
drivers/pinctrl/nuvoton/pinctrl-ma35d1.c | 1 -
drivers/pinctrl/nuvoton/pinctrl-npcm7xx.c | 44 ++------
drivers/pinctrl/nuvoton/pinctrl-npcm8xx.c | 35 ++-----
drivers/pinctrl/nuvoton/pinctrl-wpcm450.c | 11 +-
5 files changed, 77 insertions(+), 134 deletions(-)
--
2.47.2
next reply other threads:[~2025-03-18 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 10:57 Andy Shevchenko [this message]
2025-03-18 10:57 ` [PATCH v2 1/5] pinctrl: npcm8xx: Fix incorrect struct npcm8xx_pincfg assignment Andy Shevchenko
2025-03-18 10:57 ` [PATCH v2 2/5] pinctrl: nuvoton: Convert to use struct pingroup and PINCTRL_PINGROUP() Andy Shevchenko
2025-03-18 10:57 ` [PATCH v2 3/5] pinctrl: nuvoton: Make use of struct pinfunction and PINCTRL_PINFUNCTION() Andy Shevchenko
2025-03-18 10:57 ` [PATCH v2 4/5] pinctrl: nuvoton: Convert to use struct group_desc Andy Shevchenko
2025-03-18 10:57 ` [PATCH v2 5/5] pinctrl: nuvoton: Reduce use of OF-specific APIs Andy Shevchenko
2025-03-20 8:15 ` [PATCH v2 0/5] pinctrl: nuvoton: A few cleanups and a fix Linus Walleij
2025-03-20 9:45 ` Andy Shevchenko
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=20250318105932.2090926-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=j.neuschaefer@gmx.net \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=schung@nuvoton.com \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=ychuang3@nuvoton.com \
--cc=yuenn@google.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;
as well as URLs for NNTP newsgroup(s).