From: Marc Zyngier <maz@kernel.org>
To: Robert Marko <robimarko@gmail.com>
Cc: bjorn.andersson@linaro.org, agross@kernel.org,
linus.walleij@linaro.org, linux-arm-msm@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: qcom: spmi-gpio: make the irqchip immutable
Date: Tue, 12 Jul 2022 11:42:32 +0100 [thread overview]
Message-ID: <87edyq1ujr.wl-maz@kernel.org> (raw)
In-Reply-To: <20220624195112.894916-1-robimarko@gmail.com>
On Fri, 24 Jun 2022 20:51:12 +0100,
Robert Marko <robimarko@gmail.com> wrote:
>
> Commit 6c846d026d49 ("gpio: Don't fiddle with irqchips marked as
> immutable") added a warning to indicate if the gpiolib is altering the
> internals of irqchips.
>
> Following this change the following warning is now observed for the SPMI
> PMIC pinctrl driver:
> gpio gpiochip1: (200f000.spmi:pmic@0:gpio@c000): not an immutable chip, please consider fixing it!
>
> Fix this by making the irqchip in the SPMI PMIC pinctrl driver immutable.
>
> Signed-off-by: Robert Marko <robimarko@gmail.com>
> ---
> drivers/pinctrl/qcom/pinctrl-spmi-gpio.c | 22 ++++++++++++----------
> 1 file changed, 12 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/pinctrl/qcom/pinctrl-spmi-gpio.c b/drivers/pinctrl/qcom/pinctrl-spmi-gpio.c
> index c3255b0bece4..406ee0933d0b 100644
> --- a/drivers/pinctrl/qcom/pinctrl-spmi-gpio.c
> +++ b/drivers/pinctrl/qcom/pinctrl-spmi-gpio.c
> @@ -171,7 +171,6 @@ struct pmic_gpio_state {
> struct regmap *map;
> struct pinctrl_dev *ctrl;
> struct gpio_chip chip;
> - struct irq_chip irq;
> u8 usid;
> u8 pid_base;
> };
> @@ -988,6 +987,17 @@ static void *pmic_gpio_populate_parent_fwspec(struct gpio_chip *chip,
> return fwspec;
> }
>
> +static const struct irq_chip spmi_gpio_irq_chip = {
> + .name = "spmi-gpio",
> + .irq_ack = irq_chip_ack_parent,
> + .irq_mask = irq_chip_mask_parent,
> + .irq_unmask = irq_chip_unmask_parent,
No, this is wrong. Please look at the documentation to see how you
must now directly call into the gpiolib helpers for these two
callbacks.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2022-07-12 10:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 19:51 [PATCH] pinctrl: qcom: spmi-gpio: make the irqchip immutable Robert Marko
2022-07-06 14:00 ` Manivannan Sadhasivam
2022-07-09 23:05 ` Linus Walleij
2022-07-18 9:59 ` Linus Walleij
2022-07-18 11:20 ` Robert Marko
2022-07-12 10:42 ` Marc Zyngier [this message]
2022-07-12 12:44 ` Manivannan Sadhasivam
2022-07-12 15:12 ` Marc Zyngier
2022-07-13 11:08 ` Robert Marko
2022-07-13 11:47 ` Marc Zyngier
2022-07-13 12:33 ` Robert Marko
2022-07-13 13:10 ` Marc Zyngier
2022-07-13 13:34 ` Robert Marko
2022-07-13 13:41 ` Marc Zyngier
2022-07-19 7:47 ` Manivannan Sadhasivam
2022-08-16 12:45 ` Robert Marko
2022-08-19 6:34 ` Manivannan Sadhasivam
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=87edyq1ujr.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robimarko@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 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).