From: <Tudor.Ambarus@microchip.com>
To: <prabhakar.mahadev-lad.rj@bp.renesas.com>,
<Ludovic.Desroches@microchip.com>, <linus.walleij@linaro.org>,
<Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>
Cc: <robh+dt@kernel.org>, <andy.shevchenko@gmail.com>,
<prabhakar.csengg@gmail.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] pinctrl: at91-pio4: Use platform_get_irq() to get the interrupt
Date: Mon, 17 Jan 2022 08:00:34 +0000 [thread overview]
Message-ID: <241bd054-ea30-ffc9-fb36-c30c8e06db7f@microchip.com> (raw)
In-Reply-To: <20220104140913.29699-1-prabhakar.mahadev-lad.rj@bp.renesas.com>
On 1/4/22 4:09 PM, Lad Prabhakar wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> platform_get_resource(pdev, IORESOURCE_IRQ, ..) relies on static
> allocation of IRQ resources in DT core code, this causes an issue
> when using hierarchical interrupt domains using "interrupts" property
> in the node as this bypasses the hierarchical setup and messes up the
> irq chaining.
>
> In preparation for removal of static setup of IRQ resource from DT core
> code use platform_get_irq().
>
> While at it, replace the dev_err() with dev_dbg() as platform_get_irq()
> prints an error message upon error.
>
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Reviewed-by: Tudor Ambarus <tudor.ambarus@microchip.com>
Tested-by: Tudor Ambarus <tudor.ambarus@microchip.com>
thanks,
ta
> ---
> v1->v2
> * Switched using platform_get_irq()
> * Replaced dev_err() with dev_dbg()
>
> v1: https://lore.kernel.org/lkml/20211224145748.18754-3-prabhakar.mahadev-lad.rj@bp.renesas.com/
> ---
> drivers/pinctrl/pinctrl-at91-pio4.c | 16 +++++++---------
> 1 file changed, 7 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/pinctrl/pinctrl-at91-pio4.c b/drivers/pinctrl/pinctrl-at91-pio4.c
> index fafd1f55cba7..517f2a6330ad 100644
> --- a/drivers/pinctrl/pinctrl-at91-pio4.c
> +++ b/drivers/pinctrl/pinctrl-at91-pio4.c
> @@ -1045,7 +1045,6 @@ static int atmel_pinctrl_probe(struct platform_device *pdev)
> const char **group_names;
> const struct of_device_id *match;
> int i, ret;
> - struct resource *res;
> struct atmel_pioctrl *atmel_pioctrl;
> const struct atmel_pioctrl_data *atmel_pioctrl_data;
>
> @@ -1164,16 +1163,15 @@ static int atmel_pinctrl_probe(struct platform_device *pdev)
>
> /* There is one controller but each bank has its own irq line. */
> for (i = 0; i < atmel_pioctrl->nbanks; i++) {
> - res = platform_get_resource(pdev, IORESOURCE_IRQ, i);
> - if (!res) {
> - dev_err(dev, "missing irq resource for group %c\n",
> + ret = platform_get_irq(pdev, i);
> + if (ret < 0) {
> + dev_dbg(dev, "missing irq resource for group %c\n",
> 'A' + i);
> - return -EINVAL;
> + return ret;
> }
> - atmel_pioctrl->irqs[i] = res->start;
> - irq_set_chained_handler_and_data(res->start,
> - atmel_gpio_irq_handler, atmel_pioctrl);
> - dev_dbg(dev, "bank %i: irq=%pr\n", i, res);
> + atmel_pioctrl->irqs[i] = ret;
> + irq_set_chained_handler_and_data(ret, atmel_gpio_irq_handler, atmel_pioctrl);
> + dev_dbg(dev, "bank %i: irq=%d\n", i, ret);
> }
>
> atmel_pioctrl->irq_domain = irq_domain_add_linear(dev->of_node,
> --
> 2.17.1
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2022-01-17 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 14:09 [PATCH v2] pinctrl: at91-pio4: Use platform_get_irq() to get the interrupt Lad Prabhakar
2022-01-16 0:00 ` Linus Walleij
2022-01-17 8:00 ` Tudor.Ambarus [this message]
2022-01-19 16:12 ` Linus Walleij
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=241bd054-ea30-ffc9-fb36-c30c8e06db7f@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andy.shevchenko@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@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).