From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Chris Brandt <chris.brandt@renesas.com>,
linux-i2c@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Prabhakarprabhakar.csengg@gmail.com
Subject: Re: [PATCH v2 3/3] i2c: riic: Use platform_get_irq() to get the interrupt
Date: Mon, 3 Jan 2022 10:19:09 +0100 [thread overview]
Message-ID: <YdK/jYJTaDQRfOzi@ninjato> (raw)
In-Reply-To: <20211221175322.7096-4-prabhakar.mahadev-lad.rj@bp.renesas.com>
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
On Tue, Dec 21, 2021 at 05:53:22PM +0000, 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 <prabhakar.mahadev-lad.rj@bp.renesas.com>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Chris Brandt <chris.brandt@renesas.com>,
linux-i2c@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Prabhakarprabhakar.csengg@gmail.com
Subject: Re: [PATCH v2 3/3] i2c: riic: Use platform_get_irq() to get the interrupt
Date: Mon, 3 Jan 2022 10:19:09 +0100 [thread overview]
Message-ID: <YdK/jYJTaDQRfOzi@ninjato> (raw)
In-Reply-To: <20211221175322.7096-4-prabhakar.mahadev-lad.rj@bp.renesas.com>
[-- Attachment #1.1: Type: text/plain, Size: 587 bytes --]
On Tue, Dec 21, 2021 at 05:53:22PM +0000, 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 <prabhakar.mahadev-lad.rj@bp.renesas.com>
Applied to for-next, thanks!
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-01-03 9:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 17:53 [PATCH v2 0/3] i2c/busses: Use platform_get_irq/_optional() variants to fetch IRQ's Lad Prabhakar
2021-12-21 17:53 ` Lad Prabhakar
2021-12-21 17:53 ` [PATCH v2 1/3] i2c: bcm2835: Use platform_get_irq() to get the interrupt Lad Prabhakar
2021-12-21 17:53 ` Lad Prabhakar
2021-12-21 18:24 ` Florian Fainelli
2021-12-21 18:24 ` Florian Fainelli
2022-01-03 9:18 ` Wolfram Sang
2022-01-03 9:18 ` Wolfram Sang
2021-12-21 17:53 ` [PATCH v2 2/3] i2c: sh_mobile: Use platform_get_irq_optional() " Lad Prabhakar
2021-12-21 17:53 ` Lad Prabhakar
2021-12-22 9:20 ` Geert Uytterhoeven
2021-12-22 9:20 ` Geert Uytterhoeven
2021-12-22 9:49 ` Wolfram Sang
2021-12-22 9:49 ` Wolfram Sang
2021-12-25 17:48 ` Andy Shevchenko
2021-12-25 17:48 ` Andy Shevchenko
2021-12-25 23:45 ` Prabhakar Mahadev Lad
2021-12-25 23:45 ` Prabhakar Mahadev Lad
2021-12-26 8:40 ` Andy Shevchenko
2021-12-26 8:40 ` Andy Shevchenko
2021-12-26 10:03 ` Lad, Prabhakar
2021-12-26 10:03 ` Lad, Prabhakar
2022-01-03 9:19 ` Wolfram Sang
2022-01-03 9:19 ` Wolfram Sang
2021-12-21 17:53 ` [PATCH v2 3/3] i2c: riic: Use platform_get_irq() " Lad Prabhakar
2021-12-21 17:53 ` Lad Prabhakar
2021-12-22 9:52 ` Wolfram Sang
2021-12-22 9:52 ` Wolfram Sang
2021-12-22 13:00 ` Geert Uytterhoeven
2021-12-22 13:00 ` Geert Uytterhoeven
2022-01-03 9:19 ` Wolfram Sang [this message]
2022-01-03 9:19 ` Wolfram Sang
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=YdK/jYJTaDQRfOzi@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=Prabhakarprabhakar.csengg@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=chris.brandt@renesas.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenz@kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.