From: Thomas Gleixner <tglx@kernel.org>
To: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Magnus Damm <magnus.damm@gmail.com>,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH 4/6] irqchip/renesas-rzv2h: Add CA55 software interrupt support
Date: Fri, 30 Jan 2026 15:52:38 +0100 [thread overview]
Message-ID: <87fr7nkv9l.ffs@tglx> (raw)
In-Reply-To: <CA+V-a8sjADs_=81h=5R1nEFt3LWVNuHS1y-kH6Z5ANNp0Sci0w@mail.gmail.com>
On Fri, Jan 30 2026 at 11:17, Lad, Prabhakar wrote:
> On Thu, Jan 29, 2026 at 9:59 PM Thomas Gleixner <tglx@kernel.org> wrote:
>> It tries first to inject the interrupt via irq_set_irqchip_state(),
>> which only works when a chip in the hierarchy implements the
>> chip::irq_set_irqchip_state() callback.
>>
> I did implement irq_set_irqchip_state but it doesn't land in the
> rzv2h_icu_irq_set_irqchip_state(). So I was wondering if I missed
> something.
>
> #Trigger int-ca55-0
> root@rzv2h-evk:/sys/kernel/debug/irq/irqs# echo trigger > 14
>
> #The trace looks like below:
> irq_debug_write()
> -> irq_inject_interrupt()
> -> irq_set_irqchip_state()
>
> This lands in GICV3. For the RZ/V2H ICU only interrupts port_irqx and
> tintx interrupts are registered in irq_domain_create_hierarchy() for
> the rest of the interrupts these are supposed to be directly handled
> by GICv3.
...
> How do you propose to handle this? irq_inject_interrupt() would work
> if I move int-ca55-x and icu-error-ca55 under
> irq_domain_create_hierarchy().
Correct. That's how the hierarchy works.
next prev parent reply other threads:[~2026-01-30 14:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 15:01 [PATCH 0/6] irqchip/renesas-rzv2h: Add support to handle ICU error IRQ and add SWPE trigger Prabhakar
2026-01-21 15:01 ` [PATCH 1/6] irqchip/renesas-rzv2h: Use local node pointer Prabhakar
2026-01-21 15:01 ` [PATCH 2/6] irqchip/renesas-rzv2h: Use local device pointer in ICU probe Prabhakar
2026-01-21 15:01 ` [PATCH 3/6] irqchip/renesas-rzv2h: Switch to using dev_err_probe() Prabhakar
2026-01-21 15:01 ` [PATCH 4/6] irqchip/renesas-rzv2h: Add CA55 software interrupt support Prabhakar
2026-01-23 10:45 ` Geert Uytterhoeven
2026-01-23 11:24 ` Lad, Prabhakar
2026-01-26 16:03 ` Thomas Gleixner
2026-01-29 21:24 ` Lad, Prabhakar
2026-01-29 21:59 ` Thomas Gleixner
2026-01-30 11:17 ` Lad, Prabhakar
2026-01-30 14:52 ` Thomas Gleixner [this message]
2026-01-21 15:01 ` [PATCH 5/6] irqchip/renesas-rzv2h: Handle ICU error IRQ and add SWPE trigger Prabhakar
2026-01-22 8:20 ` Biju Das
2026-01-22 9:18 ` Lad, Prabhakar
2026-01-22 9:26 ` Biju Das
2026-01-26 16:11 ` Thomas Gleixner
2026-02-02 19:02 ` Lad, Prabhakar
2026-01-21 15:01 ` [PATCH 6/6] Documentation: ABI: Document rzv2h_icu debugfs triggers 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=87fr7nkv9l.ffs@tglx \
--to=tglx@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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.