From: Youngmin Nam <youngmin.nam@samsung.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: tomasz.figa@gmail.com, krzysztof.kozlowski@linaro.org,
s.nawrocki@samsung.com, alim.akhtar@samsung.com,
linus.walleij@linaro.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, semen.protsenko@linaro.org
Subject: Re: [PATCH v2] pinctrl: samsung: add irq_set_affinity() for non wake up external gpio interrupt
Date: Tue, 28 Nov 2023 10:01:25 +0900 [thread overview]
Message-ID: <ZWU75VtJ/mXpMyQr@perf> (raw)
In-Reply-To: <bb738a6b-815d-4fad-b73f-559f1ba8cd68@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2232 bytes --]
On Mon, Nov 27, 2023 at 10:54:56AM +0100, Krzysztof Kozlowski wrote:
> On 26/11/2023 10:46, Youngmin Nam wrote:
> > To support affinity setting for non wake up external gpio interrupt,
> > add irq_set_affinity callback using irq number from pinctrl driver data.
> >
> > Before this patch, changing the irq affinity of gpio interrupt is not possible:
> >
> > # cat /proc/irq/418/smp_affinity
> > 3ff
> > # echo 00f > /proc/irq/418/smp_affinity
>
> Does this command succeed on your board?
>
Yes.
> > # cat /proc/irq/418/smp_affinity
> > 3ff
> > # cat /proc/interrupts
> > CPU0 CPU1 CPU2 CPU3 ...
> > 418: 3631 0 0 0 ...
> >
> > With this patch applied, it's possible to change irq affinity of gpio interrupt:
>
> ...
>
> On which board did you test it?
>
>
I tested on S5E9945 ERD(Exynos Reference Development) board.
> > + if (parent)
> > + return parent->chip->irq_set_affinity(parent, dest, force);
> > +
>
> I think there is a helper for it: irq_chip_set_affinity_parent().
>
>
The irq_chip_set_affinity_parent() requires parent_data of irq_data.
But when I tested as below, exynos's irqd->parent_data was null.
So we should use irqchip's affinity function instead of the helper function.
--- a/drivers/pinctrl/samsung/pinctrl-exynos.c
+++ b/drivers/pinctrl/samsung/pinctrl-exynos.c
@@ -153,14 +153,12 @@ static int exynos_irq_set_type(struct irq_data *irqd, unsigned int type)
static int exynos_irq_set_affinity(struct irq_data *irqd,
const struct cpumask *dest, bool force)
{
- struct samsung_pin_bank *bank = irq_data_get_irq_chip_data(irqd);
- struct samsung_pinctrl_drv_data *d = bank->drvdata;
- struct irq_data *parent = irq_get_irq_data(d->irq);
-
- if (parent)
- return parent->chip->irq_set_affinity(parent, dest, force);
+ if (!irqd->parent_data) {
+ pr_err("irqd->parent_data is null!!\n");
+ return -EINVAL;
+ }
- return -EINVAL;
+ return irq_chip_set_affinity_parent(irqd, dest, force);
}
[ 149.658395] irqd->parent_data is null!!
> Best regards,
> Krzysztof
>
>
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Youngmin Nam <youngmin.nam@samsung.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: tomasz.figa@gmail.com, krzysztof.kozlowski@linaro.org,
s.nawrocki@samsung.com, alim.akhtar@samsung.com,
linus.walleij@linaro.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, semen.protsenko@linaro.org
Subject: Re: [PATCH v2] pinctrl: samsung: add irq_set_affinity() for non wake up external gpio interrupt
Date: Tue, 28 Nov 2023 10:01:25 +0900 [thread overview]
Message-ID: <ZWU75VtJ/mXpMyQr@perf> (raw)
In-Reply-To: <bb738a6b-815d-4fad-b73f-559f1ba8cd68@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2232 bytes --]
On Mon, Nov 27, 2023 at 10:54:56AM +0100, Krzysztof Kozlowski wrote:
> On 26/11/2023 10:46, Youngmin Nam wrote:
> > To support affinity setting for non wake up external gpio interrupt,
> > add irq_set_affinity callback using irq number from pinctrl driver data.
> >
> > Before this patch, changing the irq affinity of gpio interrupt is not possible:
> >
> > # cat /proc/irq/418/smp_affinity
> > 3ff
> > # echo 00f > /proc/irq/418/smp_affinity
>
> Does this command succeed on your board?
>
Yes.
> > # cat /proc/irq/418/smp_affinity
> > 3ff
> > # cat /proc/interrupts
> > CPU0 CPU1 CPU2 CPU3 ...
> > 418: 3631 0 0 0 ...
> >
> > With this patch applied, it's possible to change irq affinity of gpio interrupt:
>
> ...
>
> On which board did you test it?
>
>
I tested on S5E9945 ERD(Exynos Reference Development) board.
> > + if (parent)
> > + return parent->chip->irq_set_affinity(parent, dest, force);
> > +
>
> I think there is a helper for it: irq_chip_set_affinity_parent().
>
>
The irq_chip_set_affinity_parent() requires parent_data of irq_data.
But when I tested as below, exynos's irqd->parent_data was null.
So we should use irqchip's affinity function instead of the helper function.
--- a/drivers/pinctrl/samsung/pinctrl-exynos.c
+++ b/drivers/pinctrl/samsung/pinctrl-exynos.c
@@ -153,14 +153,12 @@ static int exynos_irq_set_type(struct irq_data *irqd, unsigned int type)
static int exynos_irq_set_affinity(struct irq_data *irqd,
const struct cpumask *dest, bool force)
{
- struct samsung_pin_bank *bank = irq_data_get_irq_chip_data(irqd);
- struct samsung_pinctrl_drv_data *d = bank->drvdata;
- struct irq_data *parent = irq_get_irq_data(d->irq);
-
- if (parent)
- return parent->chip->irq_set_affinity(parent, dest, force);
+ if (!irqd->parent_data) {
+ pr_err("irqd->parent_data is null!!\n");
+ return -EINVAL;
+ }
- return -EINVAL;
+ return irq_chip_set_affinity_parent(irqd, dest, force);
}
[ 149.658395] irqd->parent_data is null!!
> Best regards,
> Krzysztof
>
>
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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:[~2023-11-28 0:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231126091120epcas2p4a1320e3b0f9be8f8a0f575a322981d38@epcas2p4.samsung.com>
2023-11-26 9:46 ` [PATCH v2] pinctrl: samsung: add irq_set_affinity() for non wake up external gpio interrupt Youngmin Nam
2023-11-26 9:46 ` Youngmin Nam
2023-11-27 9:54 ` Krzysztof Kozlowski
2023-11-27 9:54 ` Krzysztof Kozlowski
2023-11-28 1:01 ` Youngmin Nam [this message]
2023-11-28 1:01 ` Youngmin Nam
2023-11-28 7:29 ` Krzysztof Kozlowski
2023-11-28 7:29 ` Krzysztof Kozlowski
2023-11-28 21:35 ` Sam Protsenko
2023-11-28 21:35 ` Sam Protsenko
2023-11-29 7:07 ` Youngmin Nam
2023-11-29 7:07 ` Youngmin Nam
2023-11-29 8:00 ` Krzysztof Kozlowski
2023-11-29 8:00 ` Krzysztof Kozlowski
2023-11-29 8:46 ` Youngmin Nam
2023-11-29 8:46 ` Youngmin Nam
2023-11-29 8:39 ` Krzysztof Kozlowski
2023-11-29 8:39 ` Krzysztof Kozlowski
2023-11-29 10:04 ` Youngmin Nam
2023-11-29 10:04 ` Youngmin Nam
2023-11-29 18:48 ` Sam Protsenko
2023-11-29 18:48 ` Sam Protsenko
2023-11-30 7:30 ` Youngmin Nam
2023-11-30 7:30 ` Youngmin Nam
2023-11-30 7:56 ` Krzysztof Kozlowski
2023-11-30 7:56 ` Krzysztof Kozlowski
2023-11-30 7:55 ` Krzysztof Kozlowski
2023-11-30 7:55 ` Krzysztof Kozlowski
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=ZWU75VtJ/mXpMyQr@perf \
--to=youngmin.nam@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=krzysztof.kozlowski@linaro.org \
--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=linux-samsung-soc@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=semen.protsenko@linaro.org \
--cc=tomasz.figa@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.