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 8898EC433FE for ; Mon, 20 Dec 2021 10:21:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231186AbhLTKVu (ORCPT ); Mon, 20 Dec 2021 05:21:50 -0500 Received: from mail-ua1-f44.google.com ([209.85.222.44]:37691 "EHLO mail-ua1-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231167AbhLTKVt (ORCPT ); Mon, 20 Dec 2021 05:21:49 -0500 Received: by mail-ua1-f44.google.com with SMTP id o1so16750513uap.4; Mon, 20 Dec 2021 02:21:49 -0800 (PST) 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=YZuaGItJIS6bhn0pnYKjSvX8duMimq87kuh/1dcSYow=; b=aRkJOOTNPw696QPGeQ8mJJL5ml+4d9Ss3igqtx3KsjVYZKRhGFSPd+jQPI+F2N73Ke fPOKoIkVBmM+23P0fKTOwFMz2/A8ETL8RPn1k7UYzgUAxUPo2b9eVhBrYRMWJYEiUXlS gBUL1kNHI6M3ZMj7YNzPRLEefwA39arOqKnteP4Nad01fqkyB3Lqa/kGOj6PNkhglciy uIWsveO1LCrzDNZQwBf4OiUO/0iJA19B8mjhJxcJT9WxCzANR+DwWqtmTEbPHwTXoikO zhYNXAHXI8NfIu+ANltFo19DJoLL7Yv3sVj7fEc79LY5Ygmi+Dmh3kQspKlOP2+kMtEj 1WXg== X-Gm-Message-State: AOAM533tpInY4aabqF+XKYXSAYAdIWPrJpb29qRy37X+bUebtk4yut0T DJ0LIwj7ItBpM7ymeUlyzlRGL1BI+6bwlQ== X-Google-Smtp-Source: ABdhPJw6BR9Ub8uR9XHB5wgFkSpeBcPX2wk8nPa835SPT4+6i35xxCNVpRDG2ny5O3ACX9rM3wVQFw== X-Received: by 2002:a67:ac49:: with SMTP id n9mr4735802vsh.65.1639995708807; Mon, 20 Dec 2021 02:21:48 -0800 (PST) Received: from mail-ua1-f45.google.com (mail-ua1-f45.google.com. [209.85.222.45]) by smtp.gmail.com with ESMTPSA id b10sm3075523uad.8.2021.12.20.02.21.47 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 20 Dec 2021 02:21:48 -0800 (PST) Received: by mail-ua1-f45.google.com with SMTP id i6so16749005uae.6; Mon, 20 Dec 2021 02:21:47 -0800 (PST) X-Received: by 2002:a9f:3e01:: with SMTP id o1mr4782661uai.89.1639995707724; Mon, 20 Dec 2021 02:21:47 -0800 (PST) MIME-Version: 1.0 References: <20211220010411.12075-1-prabhakar.mahadev-lad.rj@bp.renesas.com> <20211220010411.12075-2-prabhakar.mahadev-lad.rj@bp.renesas.com> In-Reply-To: <20211220010411.12075-2-prabhakar.mahadev-lad.rj@bp.renesas.com> From: Geert Uytterhoeven Date: Mon, 20 Dec 2021 11:21:36 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 1/6] usb: host: fotg210: Use platform_get_irq() to get the interrupt To: Lad Prabhakar Cc: Rob Herring , Greg Kroah-Hartman , USB list , Peter Chen , Pawel Laszczak , Roger Quadros , Aswath Govindraju , Felipe Balbi , Rui Miguel Silva , Bin Liu , Linux-Renesas , Linux Kernel Mailing List , Prabhakar Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 20, 2021 at 10:18 AM 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 bypasses the hierarchical setup and messes 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 Reviewed-by: Geert Uytterhoeven Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds