From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by smtp.lore.kernel.org (Postfix) with ESMTP id 53D53C433F5
	for <linux-kernel@archiver.kernel.org>; Tue,  1 Mar 2022 09:36:20 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S233913AbiCAJg6 (ORCPT <rfc822;linux-kernel@archiver.kernel.org>);
        Tue, 1 Mar 2022 04:36:58 -0500
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34566 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S233790AbiCAJgx (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 1 Mar 2022 04:36:53 -0500
Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EAA6A8A6E4
        for <linux-kernel@vger.kernel.org>; Tue,  1 Mar 2022 01:36:10 -0800 (PST)
Received: from relay2.suse.de (relay2.suse.de [149.44.160.134])
        by smtp-out2.suse.de (Postfix) with ESMTP id 9393D1F37E;
        Tue,  1 Mar 2022 09:36:09 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa;
        t=1646127369; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc:
         mime-version:mime-version:content-type:content-type:
         in-reply-to:in-reply-to:references:references;
        bh=TUvrHcAGDos5ULC1GLEdmmBfTgcilvUucu6ZddpraxU=;
        b=foRYU9ABr0hd2wOhIt6pkd74d9Zy233u7DX+JvbICsyXGFsUkd1FEGorfDY5qqdQYgBxkC
        FEjXKpi8MH72W9nYf8LVqV4kJYPKkIKBl8gFBeeEX4RPETIFH3E1aFOcM5GsETgf2Qz1mw
        hsJLviT4QwVtORC9BSNbPJXHZMl3tnw=
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de;
        s=susede2_ed25519; t=1646127369;
        h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc:
         mime-version:mime-version:content-type:content-type:
         in-reply-to:in-reply-to:references:references;
        bh=TUvrHcAGDos5ULC1GLEdmmBfTgcilvUucu6ZddpraxU=;
        b=JUmeO7A4AuQXnnhWyvU6ANZFI9u6ZKKifaXQA4c6WPNtpR0HihrLalyeGFVro+zTlY4/SS
        ZBp/n5oPOZ0co5Bg==
Received: from alsa1.suse.de (alsa1.suse.de [10.160.4.42])
        by relay2.suse.de (Postfix) with ESMTP id 7F06DA3B81;
        Tue,  1 Mar 2022 09:36:09 +0000 (UTC)
Date:   Tue, 01 Mar 2022 10:36:09 +0100
Message-ID: <s5ho82qqak6.wl-tiwai@suse.de>
From:   Takashi Iwai <tiwai@suse.de>
To:     Zhen Ni <nizhen@uniontech.com>
Cc:     perex@perex.cz, tiwai@suse.com, alsa-devel@alsa-project.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: n64: Use platform_get_irq() to get the interrupt
In-Reply-To: <20220301085536.24599-1-nizhen@uniontech.com>
References: <20220301085536.24599-1-nizhen@uniontech.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3
 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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