From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
Cc: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
LKML <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH] platform: goldfish: pipe: Use platform_get_irq() to get the interrupt
Date: Wed, 9 Mar 2022 13:23:57 +0100 [thread overview]
Message-ID: <YiicXXId7T+THYCT@kroah.com> (raw)
In-Reply-To: <CA+V-a8viRAW+YxhU=Krmc+zF3ixDOV8nL72PG7CP0iYU9onOhw@mail.gmail.com>
On Wed, Mar 09, 2022 at 12:09:45PM +0000, Lad, Prabhakar wrote:
> Hi Greg,
>
> I'm not sure how I missed you to add in the to list.
>
> On Fri, Dec 24, 2021 at 4:13 PM Lad Prabhakar
> <prabhakar.mahadev-lad.rj@bp.renesas.com> 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 <prabhakar.mahadev-lad.rj@bp.renesas.com>
> > ---
> > Hi,
> >
> > Dropping usage of platform_get_resource() was agreed based on
> > the discussion [0].
> >
> > [0] https://patchwork.kernel.org/project/linux-renesas-soc/
> > patch/20211209001056.29774-1-prabhakar.mahadev-lad.rj@bp.renesas.com/
> >
> > Cheers,
> > Prabhakar
> > ---
> > drivers/platform/goldfish/goldfish_pipe.c | 8 +++-----
> > 1 file changed, 3 insertions(+), 5 deletions(-)
> >
> Do you want me to resend this patch?
If you want me to apply it, yes.
thanks,
greg k-h
next prev parent reply other threads:[~2022-03-09 12:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 16:13 [PATCH] perf/arm-ccn: Use platform_get_irq() to get the interrupt Lad Prabhakar
2021-12-24 16:13 ` [PATCH] platform: goldfish: pipe: " Lad Prabhakar
2022-03-09 12:09 ` Lad, Prabhakar
2022-03-09 12:23 ` Greg Kroah-Hartman [this message]
2021-12-24 16:13 ` [PATCH] slimbus: qcom-ngd-ctrl: " Lad Prabhakar
2021-12-24 18:08 ` Bjorn Andersson
2021-12-25 17:40 ` Steev Klimaszewski
2022-03-10 1:48 ` Lad, Prabhakar
2022-03-10 10:16 ` Srinivas Kandagatla
2022-03-10 10:23 ` Lad, Prabhakar
2022-03-10 10:42 ` Srinivas Kandagatla
2022-03-10 14:14 ` Rob Herring
2022-03-10 14:59 ` Srinivas Kandagatla
2022-03-11 19:38 ` Lad, Prabhakar
2021-12-24 16:13 ` [PATCH] staging: axis-fifo: " Lad Prabhakar
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=YiicXXId7T+THYCT@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.org \
/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