From: William Breathitt Gray <wbg@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Michael Walle <mwalle@kernel.org>,
Ioana Ciornei <ioana.ciornei@nxp.com>,
Mark Brown <broonie@kernel.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
William Breathitt Gray <wbg@kernel.org>,
Mark Cave-Ayland <mark.caveayland@nutanix.com>,
stable@vger.kernel.org
Subject: [PATCH v2 0/3] gpio: idio-16: Fix regmap initialization errors
Date: Mon, 20 Oct 2025 17:51:43 +0900 [thread overview]
Message-ID: <20251020-fix-gpio-idio-16-regmap-v2-0-ebeb50e93c33@kernel.org> (raw)
The migration of IDIO-16 GPIO drivers to the regmap API resulted in some
regressions to the gpio-104-idio-16, gpio-pci-idio-16, and gpio-idio-16
modules. Specifically, the 104-idio-16 and pci-idio-16 GPIO drivers
utilize regmap caching and thus must set max_register for their
regmap_config, while gpio-idio-16 requires fixed_direction_output to
represent the fixed direction of the IDIO-16 GPIO lines. Fixes for these
regressions are provided by this series.
Link: https://lore.kernel.org/r/cover.1680618405.git.william.gray@linaro.org
Closes: https://lore.kernel.org/r/9b0375fd-235f-4ee1-a7fa-daca296ef6bf@nutanix.com
Signed-off-by: William Breathitt Gray <wbg@kernel.org>
---
Changes in v2:
- Pick up Reviewed-by tags
- Replace Link tags with Closes tags for fixes addressing bug reports
- Link to v1: https://lore.kernel.org/r/20251017-fix-gpio-idio-16-regmap-v1-0-a7c71080f740@kernel.org
---
William Breathitt Gray (3):
gpio: 104-idio-16: Define maximum valid register address offset
gpio: pci-idio-16: Define maximum valid register address offset
gpio: idio-16: Define fixed direction of the GPIO lines
drivers/gpio/gpio-104-idio-16.c | 1 +
drivers/gpio/gpio-idio-16.c | 5 +++++
drivers/gpio/gpio-pci-idio-16.c | 1 +
3 files changed, 7 insertions(+)
---
base-commit: eba11116f39533d2e38cc5898014f2c95f32d23a
change-id: 20251017-fix-gpio-idio-16-regmap-1282cdc56a19
Best regards,
--
William Breathitt Gray <wbg@kernel.org>
next reply other threads:[~2025-10-20 8:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 8:51 William Breathitt Gray [this message]
2025-10-20 8:51 ` [PATCH v2 1/3] gpio: 104-idio-16: Define maximum valid register address offset William Breathitt Gray
2025-10-20 8:51 ` [PATCH v2 2/3] gpio: pci-idio-16: " William Breathitt Gray
2025-10-20 8:51 ` [PATCH v2 3/3] gpio: idio-16: Define fixed direction of the GPIO lines William Breathitt Gray
2025-10-21 13:21 ` Bartosz Golaszewski
2025-10-21 14:41 ` Andy Shevchenko
2025-10-21 14:49 ` Bartosz Golaszewski
2025-10-21 15:04 ` Andy Shevchenko
2025-10-22 2:18 ` William Breathitt Gray
2025-10-22 6:50 ` Bartosz Golaszewski
2025-10-21 7:15 ` [PATCH v2 0/3] gpio: idio-16: Fix regmap initialization errors Linus Walleij
2025-10-21 9:50 ` Bartosz Golaszewski
2025-10-22 6:54 ` (subset) " Bartosz Golaszewski
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=20251020-fix-gpio-idio-16-regmap-v2-0-ebeb50e93c33@kernel.org \
--to=wbg@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=ioana.ciornei@nxp.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.caveayland@nutanix.com \
--cc=mwalle@kernel.org \
--cc=stable@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).