From: Linus Walleij <linus.walleij@linaro.org>
To: Johan Korsnes <johan.korsnes@remarkable.no>,
Bough Chen <haibo.chen@nxp.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
imx@lists.linux.dev
Cc: linux-gpio@vger.kernel.org, Linus Walleij <linus.walleij@linaro.org>
Subject: [PATCH v2 0/2] gpio-mmio: Extend to handle pinctrl back-ends
Date: Sat, 15 Feb 2025 00:12:44 +0100 [thread overview]
Message-ID: <20250215-vf610-mmio-v2-0-4a91f8c8e8d5@linaro.org> (raw)
If we're using gpio-mmio with a pinctrl backend the
direction callbacks need to finalize their work by
calling into the pin control back-end.
As I was made aware that the vf610 driver was missing
only that to use gpio-mmio instead of custom code,
I took a stab at it.
This patch is made on top of Johan Korsnes bug fix,
so it needs to be applied after that is in, if this
works.
Plese try it out on vf610!
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
Changes in v2:
- Use the dual input/output set/clear registers for output.
- Provide the BGPIOF_READ_OUTPUT_REG_SET flag so the driver
behaves as described in the commit message...
- Drop the now unused spinlock (gpio-mmio has its own).
- Fix a speling mistake.
- Link to v1: https://lore.kernel.org/r/20250214-vf610-mmio-v1-0-6cccd0292e84@linaro.org
---
Linus Walleij (2):
gpio: mmio: Add flag for calling pinctrl back-end
gpio: vf610: Switch to gpio-mmio
drivers/gpio/Kconfig | 1 +
drivers/gpio/gpio-mmio.c | 36 +++++++++++----
drivers/gpio/gpio-vf610.c | 109 +++++++-------------------------------------
include/linux/gpio/driver.h | 3 ++
4 files changed, 49 insertions(+), 100 deletions(-)
---
base-commit: 8e2ad024bbbbd1add00e9ddc4aa943d3a27fa146
change-id: 20250213-vf610-mmio-eddfaeb6b197
Best regards,
--
Linus Walleij <linus.walleij@linaro.org>
next reply other threads:[~2025-02-14 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 23:12 Linus Walleij [this message]
2025-02-14 23:12 ` [PATCH v2 1/2] gpio: mmio: Add flag for calling pinctrl back-end Linus Walleij
2025-02-14 23:12 ` [PATCH v2 2/2] gpio: vf610: Switch to gpio-mmio Linus Walleij
2025-02-17 11:24 ` Bough Chen
2025-02-19 21:10 ` 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=20250215-vf610-mmio-v2-0-4a91f8c8e8d5@linaro.org \
--to=linus.walleij@linaro.org \
--cc=brgl@bgdev.pl \
--cc=haibo.chen@nxp.com \
--cc=imx@lists.linux.dev \
--cc=johan.korsnes@remarkable.no \
--cc=linux-gpio@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;
as well as URLs for NNTP newsgroup(s).