From: William Breathitt Gray <william.gray@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
William Breathitt Gray <william.gray@linaro.org>
Subject: [PATCH v5 0/4] Migrate IDIO-16 GPIO drivers to regmap API
Date: Tue, 4 Apr 2023 10:32:44 -0400 [thread overview]
Message-ID: <cover.1680618405.git.william.gray@linaro.org> (raw)
Changes in v5:
- Remove regmap_config max_register lines as superfluous
- Enable use_raw_spinlock to prevent deadlocks when running -rt kernels
The regmap API supports IO port accessors so we can take advantage of
regmap abstractions rather than handling access to the device registers
directly in the driver. The 104-idio-16 and pci-idio-16 modules depend
on the IDIO-16 library and are thus updated accordingly.
By leveraging the regmap API, the idio-16 library is reduced to simply a
devm_idio_16_regmap_register() function and a configuration structure
struct idio_16_regmap_config.
This patchset depends on the "Drop map from handle_mask_sync()
parameters" patchset [0].
[0] https://lore.kernel.org/all/cover.1679323449.git.william.gray@linaro.org/
William Breathitt Gray (4):
gpio: idio-16: Migrate to the regmap API
gpio: 104-idio-16: Migrate to the regmap API
gpio: pci-idio-16: Migrate to the regmap API
gpio: idio-16: Remove unused legacy interface
drivers/gpio/Kconfig | 7 +-
drivers/gpio/gpio-104-idio-16.c | 286 +++++++------------------------
drivers/gpio/gpio-idio-16.c | 254 ++++++++++++++-------------
drivers/gpio/gpio-idio-16.h | 79 +++------
drivers/gpio/gpio-pci-idio-16.c | 294 +++++++-------------------------
5 files changed, 289 insertions(+), 631 deletions(-)
base-commit: 7b59bdbc3965ca8add53e084af394c13a2be22a8
prerequisite-patch-id: cd19046150b7cff1be4ac7152198777aa960a3df
prerequisite-patch-id: bd3e3830d9ce4f3876a77483364d7190b7fdffa7
--
2.39.2
next reply other threads:[~2023-04-04 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 14:32 William Breathitt Gray [this message]
2023-04-04 14:32 ` [PATCH v5 1/4] gpio: idio-16: Migrate to the regmap API William Breathitt Gray
2023-04-05 9:00 ` Andy Shevchenko
2023-04-04 14:32 ` [PATCH v5 2/4] gpio: 104-idio-16: " William Breathitt Gray
2023-04-04 14:32 ` [PATCH v5 3/4] gpio: pci-idio-16: " William Breathitt Gray
2023-04-04 14:32 ` [PATCH v5 4/4] gpio: idio-16: Remove unused legacy interface William Breathitt Gray
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=cover.1680618405.git.william.gray@linaro.org \
--to=william.gray@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.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;
as well as URLs for NNTP newsgroup(s).