From: Hangtian Zhu <hangtian.zhu@oss.qualcomm.com>
To: Thomas Gleixner <tglx@kernel.org>, jjohnson@kernel.org
Cc: linux-wireless@vger.kernel.org, ath12k@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 1/2] genirq: export irq_can_set_affinity() for module drivers
Date: Wed, 20 May 2026 10:42:36 +0800 [thread overview]
Message-ID: <b5870d83-6cc6-4b9e-bb4c-ee812d8b7727@oss.qualcomm.com> (raw)
In-Reply-To: <875x4jxyht.ffs@tglx>
On 5/19/2026 22:30, Thomas Gleixner wrote:
> eviewed-by: Thomas Gleixner <tglx@kernel.org>
> On Tue, May 19 2026 at 09:16, Hangtian Zhu wrote:
>> Export irq_can_set_affinity() for loadable drivers that need a runtime
>> check for IRQ affinity capability.
>>
>> In hierarchical IRQ setups where the effective irqchip path lacks
>> .irq_set_affinity(), drivers may need to switch to a fallback policy.
>> Without this export, module drivers cannot use the core helper and have
>> to open-code equivalent checks.
>>
>> Signed-off-by: Hangtian Zhu <hangtian.zhu@oss.qualcomm.com>
> Assuming this goes through the wireless tree:
yes, it's wireless tree.
> Acked-by: Thomas Gleixner <tglx@kernel.org>
>
> If not, please let me know and I pick it up.
next prev parent reply other threads:[~2026-05-20 2:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 1:16 [RESEND PATCH 0/2] genirq/ath12k: fallback to threaded NAPI when IRQ affinity is unavailable Hangtian Zhu
2026-05-19 1:16 ` [RESEND PATCH 1/2] genirq: export irq_can_set_affinity() for module drivers Hangtian Zhu
2026-05-19 14:30 ` Thomas Gleixner
2026-05-20 2:42 ` Hangtian Zhu [this message]
2026-05-20 16:00 ` Jeff Johnson
2026-05-19 1:16 ` [RESEND PATCH 2/2] wifi: ath12k: enable threaded NAPI when DP IRQ affinity is unavailable Hangtian Zhu
2026-06-18 7:11 ` Baochen Qiang
2026-06-30 21:26 ` [RESEND PATCH 0/2] genirq/ath12k: fallback to threaded NAPI when " Jeff Johnson
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=b5870d83-6cc6-4b9e-bb4c-ee812d8b7727@oss.qualcomm.com \
--to=hangtian.zhu@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tglx@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®