From: Takashi Iwai <tiwai@suse.de>
To: Zhen Ni <nizhen@uniontech.com>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
tiwai@suse.com
Subject: Re: [PATCH] ALSA: n64: Use platform_get_irq() to get the interrupt
Date: Tue, 01 Mar 2022 10:36:09 +0100 [thread overview]
Message-ID: <s5ho82qqak6.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220301085536.24599-1-nizhen@uniontech.com>
On Tue, 01 Mar 2022 09:55:36 +0100,
Zhen Ni wrote:
>
> 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 bypassed the hierarchical setup and messed up the
> irq chaining.
>
> In preparation for removal of static setup of IRQ resource from DT core
> code use platform_get_irq().
>
> Signed-off-by: Zhen Ni <nizhen@uniontech.com>
The same fix has been already queued at commit a544684b790f.
thanks,
Takashi
prev parent reply other threads:[~2022-03-01 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 8:55 [PATCH] ALSA: n64: Use platform_get_irq() to get the interrupt Zhen Ni
2022-03-01 9:36 ` Takashi Iwai [this message]
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=s5ho82qqak6.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nizhen@uniontech.com \
--cc=tiwai@suse.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