From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Youngmin Nam <youngmin.nam@samsung.com>
Cc: tomasz.figa@gmail.com, 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 08:29:30 +0100 [thread overview]
Message-ID: <1fd55b36-0837-4bf7-9fde-e573d6cb214a@linaro.org> (raw)
In-Reply-To: <ZWU75VtJ/mXpMyQr@perf>
On 28/11/2023 02:01, Youngmin Nam wrote:
> 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.
Hm, fails all the time one mine.
>
>>> # 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.
There is no such board upstream. How can we reproduce this issue? I am
afraid we cannot test neither the bug nor the fix.
>
>>> + 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.
Hm, so now I wonder why do we not have parent_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.
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-11-28 7:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231126091120epcas2p4a1320e3b0f9be8f8a0f575a322981d38@epcas2p4.samsung.com>
2023-11-26 9:46 ` Youngmin Nam
2023-11-27 9:54 ` Krzysztof Kozlowski
2023-11-28 1:01 ` Youngmin Nam
2023-11-28 7:29 ` Krzysztof Kozlowski [this message]
2023-11-28 21:35 ` Sam Protsenko
2023-11-29 7:07 ` Youngmin Nam
2023-11-29 8:00 ` Krzysztof Kozlowski
2023-11-29 8:46 ` Youngmin Nam
2023-11-29 8:39 ` Krzysztof Kozlowski
2023-11-29 10:04 ` Youngmin Nam
2023-11-29 18:48 ` Sam Protsenko
2023-11-30 7:30 ` Youngmin Nam
2023-11-30 7:56 ` 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=1fd55b36-0837-4bf7-9fde-e573d6cb214a@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alim.akhtar@samsung.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=linux-samsung-soc@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=semen.protsenko@linaro.org \
--cc=tomasz.figa@gmail.com \
--cc=youngmin.nam@samsung.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
all inboxes | Powered by JetHome®