From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Bartosz Golaszewski" <brgl@bgdev.pl>
Cc: "Lee Jones" <lee@kernel.org>, "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Kamel Bouhara" <kamel.bouhara@bootlin.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Uwe Kleine-König" <ukleinek@kernel.org>,
"Michael Walle" <mwalle@kernel.org>,
"Mark Brown" <broonie@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Danilo Krummrich" <dakr@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-input@vger.kernel.org,
linux-pwm@vger.kernel.org, andriy.shevchenko@intel.com,
"Grégory Clement" <gregory.clement@bootlin.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v9 06/11] gpio: regmap: Allow to allocate regmap-irq device
Date: Mon, 26 May 2025 14:03:12 +0200 [thread overview]
Message-ID: <DA62SSMI7C52.V2QD509S95QW@bootlin.com> (raw)
In-Reply-To: <CAMRc=MeT+b5dBOWyf6-BpTjk70nwVhLOpCY-JHNizBo5H1-AnQ@mail.gmail.com>
On Thu May 22, 2025 at 3:01 PM CEST, Bartosz Golaszewski wrote:
> On Thu, May 22, 2025 at 2:06 PM Mathieu Dubois-Briand
> <mathieu.dubois-briand@bootlin.com> wrote:
>>
>> GPIO controller often have support for IRQ: allow to easily allocate
>> both gpio-regmap and regmap-irq in one operation.
>>
>> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
>> ---
>> drivers/gpio/gpio-regmap.c | 21 +++++++++++++++++++--
>> include/linux/gpio/regmap.h | 11 +++++++++++
>> 2 files changed, 30 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpio/gpio-regmap.c b/drivers/gpio/gpio-regmap.c
>> index 87c4225784cf..9cbbbaf82609 100644
>> --- a/drivers/gpio/gpio-regmap.c
>> +++ b/drivers/gpio/gpio-regmap.c
>> @@ -215,6 +215,7 @@ EXPORT_SYMBOL_GPL(gpio_regmap_get_drvdata);
>> */
>> struct gpio_regmap *gpio_regmap_register(const struct gpio_regmap_config *config)
>> {
>> + struct irq_domain *irq_domain;
>> struct gpio_regmap *gpio;
>> struct gpio_chip *chip;
>> int ret;
>> @@ -295,8 +296,24 @@ struct gpio_regmap *gpio_regmap_register(const struct gpio_regmap_config *config
>> if (ret < 0)
>> goto err_free_gpio;
>>
>> - if (config->irq_domain) {
>> - ret = gpiochip_irqchip_add_domain(chip, config->irq_domain);
>> +#ifdef CONFIG_REGMAP_IRQ
>> + if (config->regmap_irq_chip) {
>> + struct regmap_irq_chip_data *irq_chip_data;
>> +
>> + ret = devm_regmap_add_irq_chip_fwnode(config->parent, dev_fwnode(config->parent),
>> + config->regmap, config->regmap_irq_line,
>> + config->regmap_irq_flags, 0,
>> + config->regmap_irq_chip, &irq_chip_data);
>
> I don't think using devres here is a good idea. There's no guarantee
> that gpio_regmap_register() will be called on device attach so you
> must not make the release of the resource depend on an associated
> detach which may never happen. Please use the non-managed variant
> here.
Right, I will make sure to use
regmap_add_irq_chip_fwnode()/regmap_del_irq_chip() here.
I should be able to send a new version in the coming days.
>
> Bart
>
Thanks for your review.
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-05-26 12:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 12:06 [PATCH v9 00/11] Add support for MAX7360 Mathieu Dubois-Briand
2025-05-22 12:06 ` [PATCH v9 01/11] dt-bindings: mfd: gpio: Add MAX7360 Mathieu Dubois-Briand
2025-05-22 12:06 ` [PATCH v9 02/11] mfd: Add max7360 support mathieu.dubois-briand
2025-05-22 12:06 ` [PATCH v9 03/11] pinctrl: Add MAX7360 pinctrl driver Mathieu Dubois-Briand
2025-05-22 12:06 ` [PATCH v9 04/11] pwm: max7360: Add MAX7360 PWM support mathieu.dubois-briand
2025-05-22 12:06 ` [PATCH v9 05/11] regmap: irq: Add support for chips without separate IRQ status Mathieu Dubois-Briand
2025-05-22 12:06 ` [PATCH v9 06/11] gpio: regmap: Allow to allocate regmap-irq device Mathieu Dubois-Briand
2025-05-22 13:01 ` Bartosz Golaszewski
2025-05-26 12:03 ` Mathieu Dubois-Briand [this message]
2025-05-22 12:06 ` [PATCH v9 07/11] gpio: regmap: Allow to provide init_valid_mask callback Mathieu Dubois-Briand
2025-05-22 12:48 ` Bartosz Golaszewski
2025-05-22 12:06 ` [PATCH v9 08/11] gpio: max7360: Add MAX7360 gpio support Mathieu Dubois-Briand
2025-05-22 12:06 ` [PATCH v9 09/11] input: keyboard: Add support for MAX7360 keypad Mathieu Dubois-Briand
2025-05-22 12:06 ` [PATCH v9 10/11] input: misc: Add support for MAX7360 rotary Mathieu Dubois-Briand
2025-05-22 12:06 ` [PATCH v9 11/11] MAINTAINERS: Add entry on MAX7360 driver Mathieu Dubois-Briand
2025-05-22 15:55 ` (subset) [PATCH v9 00/11] Add support for MAX7360 Mark Brown
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=DA62SSMI7C52.V2QD509S95QW@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=andriy.shevchenko@intel.com \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dakr@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gregory.clement@bootlin.com \
--cc=kamel.bouhara@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mwalle@kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=ukleinek@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
all inboxes | Powered by JetHome®