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 3BEA8C433F5
	for <linux-kernel@archiver.kernel.org>; Mon, 16 May 2022 11:29:19 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S233899AbiEPL3R (ORCPT <rfc822;linux-kernel@archiver.kernel.org>);
        Mon, 16 May 2022 07:29:17 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53638 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S229693AbiEPL3O (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 16 May 2022 07:29:14 -0400
Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D9605D139;
        Mon, 16 May 2022 04:29:13 -0700 (PDT)
Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140])
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
        (No client certificate requested)
        by ams.source.kernel.org (Postfix) with ESMTPS id 50D3EB81057;
        Mon, 16 May 2022 11:29:11 +0000 (UTC)
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8817CC385B8;
        Mon, 16 May 2022 11:29:09 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
        s=k20201202; t=1652700550;
        bh=nJB+Oj+EMaiHtJGEgHUqqIU2EC9RoBWL+Nd8eq8yAy4=;
        h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
        b=uMvfOMT98aHFxjccQ5rOtC4U6FS3lYCkZPilv2PAi7sDGVkVlP5lOfv/i99hMFTam
         OOdCc7Vhr3wLoYxmuj/G1uJQkwB1LNkUfNWS+b1Aa5Y+pHozEkZO384IvnpiB1QBch
         eDYqXTKamIlbLWtvuSPKOjf2opE5U2DRhtXQ/fC1EiQnZuwM6PRinF2ajbhP7EiTBp
         f12AKwjP96M3aM1cyhRqLZmxF4xVT19O+k8GYofJEk/N5gR4yjlKdCuuLFKMPYoc0y
         KCuoP/bzkF3xlHxw55strt/+EL+WJwnQV83Dj7p5d0FfXo9OH0ljmkDKesO4WbnM+K
         phBZuSpZheIgg==
Date:   Mon, 16 May 2022 16:59:05 +0530
From:   Vinod Koul <vkoul@kernel.org>
To:     Akhil R <akhilrajeev@nvidia.com>
Cc:     dmaengine@vger.kernel.org, jonathanh@nvidia.com,
        ldewangan@nvidia.com, linux-kernel@vger.kernel.org,
        linux-tegra@vger.kernel.org, p.zabel@pengutronix.de,
        thierry.reding@gmail.com
Subject: Re: [PATCH] dmaengine: tegra: Use platform_get_irq() to get IRQ
 resource
Message-ID: <YoI1gchpEUcqC6fY@matsya>
References: <20220505091440.12981-1-akhilrajeev@nvidia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20220505091440.12981-1-akhilrajeev@nvidia.com>
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 05-05-22, 14:44, Akhil R wrote:
> Use platform_irq_get() instead platform_get_resource() for IRQ resource
> to fix the probe failure. platform_get_resource() fails to fetch the IRQ
> resource as it might not be ready at that time.
> 
> platform_irq_get() is also the recommended way to get interrupt as it
> directly gives the IRQ number and no conversion from resource is
> required.

Applied, thanks

-- 
~Vinod