From: William Breathitt Gray <william.gray@linaro.org>
To: linus.walleij@linaro.org, brgl@bgdev.pl
Cc: broonie@kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, quarium@gmail.com,
jhentges@accesio.com, jay.dolan@accesio.com,
William Breathitt Gray <william.gray@linaro.org>
Subject: [PATCH v2 0/2] Migrate PCIe-IDIO-24 GPIO driver to the regmap API
Date: Mon, 27 Feb 2023 22:56:26 -0500 [thread overview]
Message-ID: <cover.1677555956.git.william.gray@linaro.org> (raw)
Changes in v2:
- Simplify PCIe-IDIO-24 register offset defines to remove superfluous
arithmetic
- Check for NULL pointer after chip->irq_drv_data allocation
- Set gpio_regmap drvdata and use gpio_regmap_get_drvdata() to get the
regmap in idio_24_reg_map_xlate()
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.
A patch to pass the device regmap and irq_drv_data as a parameters for
the struct regmap_irq_chip set_type_config() is included. This is needed
by idio_24_set_type_config() in order to update the type configuration
on the device as well as irq_drv_data for idio_24_handle_mask_sync().
William Breathitt Gray (2):
regmap: Pass regmap and irq_drv_data as parameters for
set_type_config()
gpio: pcie-idio-24: Migrate to the regmap API
drivers/base/regmap/regmap-irq.c | 13 +-
drivers/gpio/Kconfig | 3 +
drivers/gpio/gpio-pcie-idio-24.c | 693 ++++++++++++-------------------
include/linux/regmap.h | 12 +-
4 files changed, 279 insertions(+), 442 deletions(-)
base-commit: 4827aae061337251bb91801b316157a78b845ec7
--
2.39.2
next reply other threads:[~2023-03-01 12:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 3:56 William Breathitt Gray [this message]
2023-02-28 3:56 ` [PATCH v2 1/2] regmap: Pass regmap and irq_drv_data as parameters for set_type_config() William Breathitt Gray
2023-02-28 3:56 ` [PATCH v2 2/2] gpio: pcie-idio-24: Migrate to the regmap API 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.1677555956.git.william.gray@linaro.org \
--to=william.gray@linaro.org \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=jay.dolan@accesio.com \
--cc=jhentges@accesio.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quarium@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.