Return-Path: 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 A6886C433EF for ; Wed, 5 Jan 2022 09:24:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238858AbiAEJYv (ORCPT ); Wed, 5 Jan 2022 04:24:51 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57248 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233736AbiAEJYu (ORCPT ); Wed, 5 Jan 2022 04:24:50 -0500 Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 02629C061761 for ; Wed, 5 Jan 2022 01:24:50 -0800 (PST) Received: by mail-ed1-x52c.google.com with SMTP id n30so47221854eda.13 for ; Wed, 05 Jan 2022 01:24:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bgdev-pl.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=x/Nken2odV4gckkQ8V6N90O1oM6oc/RLFuu7U65G9ng=; b=enCDi3X3u8T4D6TrBkYLVSCRvi7Icbz9yjgOi3UoOeRpka+U4Gzd/Wxd25C5Gdb3G/ GMSeKDHw8db7ACPAcG2Aqn9Sq2unMNk+UMKtgNKp6BFmS51332wsfG9ZeSFny/AuA2YJ OUNBBcZ5QRdV4F4jXwWu7NTBc12LeuAlzABmgudthJ5gITvkLudYukB1uFE16vRBEipH oL+EZ5p1iJ+qI3BMIXPSGA1K+6gdfjB4MqqAjDIVzC2kog9gVgLX6Pp2sFfEQPpNFuFt jiKSPVN9qKQL0V+cFOOf0MOuJfOTFWka5pWca6b3wvfICtv70eMtIYxL4IcRJqaScicU OZfQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=x/Nken2odV4gckkQ8V6N90O1oM6oc/RLFuu7U65G9ng=; b=qBhad5SIxkkY44LDXhgc6tk3C1yXu7Hqsa8SU1/yxjA9O8A0sYzJ6ekxWmsgkzauTl o9lg40da41K9wrzMJ7Jg5KbM/WuHJsZGiDmgaIhhnbTUBEjUQvisuRliB+ynzzhQ/VRG 141Yw5hQrw8/BOzXAeYLelMWc92+sX4ZMKb/d1yiyhFkZhw9lK+7ib1ux7grybseES6I FaoS6l/61u0vv+q8ZFJ2U1M8iA6ua9ub0MRMaMnfv01iRYy0pHgk4luGH8JEvYPzgKG3 9YN1UjFV8hEV6E0swhCnex5YmZyRsylzv34NWrdUKlTvd/CmZujGnyfrCT8keiC5ylFS 4ZCw== X-Gm-Message-State: AOAM532SrrIe3L+oW2wsOU79rYrkibm5tdN6pSPugP4O6SqmA61D+U9h 4u8FPyKLQG33xXeQDapgPSkpGqkwm2dOAvrZb1z2ZA== X-Google-Smtp-Source: ABdhPJyATT38VL55Ws94nS9wqslEGbupCfSKXrv3FU/7Gb1aF9isr5j8LAZacVQJUds8OKc2Sb7KlPo5Gnes2znyX9k= X-Received: by 2002:a17:907:62a8:: with SMTP id nd40mr7909363ejc.101.1641374688581; Wed, 05 Jan 2022 01:24:48 -0800 (PST) MIME-Version: 1.0 References: <20211222171915.9053-1-prabhakar.mahadev-lad.rj@bp.renesas.com> <20211222171915.9053-3-prabhakar.mahadev-lad.rj@bp.renesas.com> In-Reply-To: <20211222171915.9053-3-prabhakar.mahadev-lad.rj@bp.renesas.com> From: Bartosz Golaszewski Date: Wed, 5 Jan 2022 10:24:38 +0100 Message-ID: Subject: Re: [PATCH 2/2] gpio: rcar: Use platform_get_irq() to get the interrupt To: Lad Prabhakar Cc: Linus Walleij , "open list:GPIO SUBSYSTEM" , Rob Herring , Linux Kernel Mailing List , Linux-Renesas , Prabhakar Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 22, 2021 at 6:19 PM Lad Prabhakar 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: Lad Prabhakar > --- Applied, thanks! Bart