From: Thomas Gleixner <tglx@kernel.org>
To: Prabhakar <prabhakar.csengg@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Prabhakar <prabhakar.csengg@gmail.com>,
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 v3 5/6] irqchip/renesas-rzv2h: Add CA55 software interrupt support
Date: Tue, 24 Feb 2026 08:34:17 +0100 [thread overview]
Message-ID: <87bjhevbly.ffs@tglx> (raw)
In-Reply-To: <20260209104121.26172-6-prabhakar.mahadev-lad.rj@bp.renesas.com>
On Mon, Feb 09 2026 at 10:41, Prabhakar wrote:
> static int rzv2h_icu_set_type(struct irq_data *d, unsigned int type)
> {
> + unsigned int gic_type = IRQ_TYPE_LEVEL_HIGH;
> unsigned int hw_irq = irqd_to_hwirq(d);
> int ret;
>
> @@ -445,6 +475,11 @@ static int rzv2h_icu_set_type(struct irq_data *d, unsigned int type)
> /* TINT */
> ret = rzv2h_tint_set_type(d, type);
> break;
> + case ICU_CA55_INT_START ... ICU_CA55_INT_LAST:
> + /* CA55 Software Interrupts have EDGE_RISING type */
> + gic_type = IRQ_TYPE_EDGE_RISING;
So this unconditionally selects EDGE_RISING independent of the type
provided by the caller. Interesting choice and compatible with the rest
of the code - _not_.
> +
> +static int rzv2h_icu_setup_irqs(struct platform_device *pdev,
> + struct irq_domain *irq_domain)
I told you before that you have 100 characters. Get rid of these line breaks.
> +{
> + bool irq_inject = IS_ENABLED(CONFIG_GENERIC_IRQ_INJECTION);
> + static const char * const rzv2h_swint_names[] = {
> + "int-ca55-0", "int-ca55-1",
> + "int-ca55-2", "int-ca55-3",
> + };
> + static const u8 swint_idx[] = { 0, 1, 2, 3 };
> + struct device *dev = &pdev->dev;
> + struct irq_fwspec fwspec;
> + unsigned int virq;
> + unsigned int i;
Coalesce same types into a single line. See Documentation/....
> + int ret;
> +
> + for (i = 0; i < ICU_CA55_INT_COUNT && irq_inject; i++) {
> + fwspec.fwnode = irq_domain->fwnode;
> + fwspec.param_count = 2;
> + fwspec.param[0] = ICU_CA55_INT_START + i;
> + fwspec.param[1] = IRQ_TYPE_EDGE_RISING;
> +
> + virq = irq_create_fwspec_mapping(&fwspec);
> + if (!virq)
> + return dev_err_probe(dev, -EINVAL, "failed to create IRQ mapping for %s\n",
> + rzv2h_swint_names[i]);
This lacks curly brackets on the if(). See Documentation/.....
> + ret = devm_request_irq(dev, virq, rzv2h_icu_swint_irq, 0, dev_name(dev),
> + (void *)&swint_idx[i]);
> + if (ret)
> + return dev_err_probe(dev, ret, "Failed to request %s IRQ\n",
> + rzv2h_swint_names[i]);
Ditto.
> + }
Thanks,
tglx
next prev parent reply other threads:[~2026-02-24 7:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 10:41 [PATCH v3 0/6] irqchip/renesas-rzv2h: Add support to handle ICU error IRQ and add SWPE trigger Prabhakar
2026-02-09 10:41 ` [PATCH v3 1/6] irqchip/renesas-rzv2h: Use local node pointer Prabhakar
2026-02-09 10:41 ` [PATCH v3 2/6] irqchip/renesas-rzv2h: Use local device pointer in ICU probe Prabhakar
2026-02-09 10:41 ` [PATCH v3 3/6] irqchip/renesas-rzv2h: Switch to using dev_err_probe() Prabhakar
2026-02-09 10:41 ` [PATCH v3 4/6] irqchip/renesas-rzv2h: Make IRQ type handling range-aware Prabhakar
2026-02-24 7:30 ` Thomas Gleixner
2026-02-24 13:41 ` Lad, Prabhakar
2026-02-09 10:41 ` [PATCH v3 5/6] irqchip/renesas-rzv2h: Add CA55 software interrupt support Prabhakar
2026-02-24 7:34 ` Thomas Gleixner [this message]
2026-02-24 15:36 ` Lad, Prabhakar
2026-02-09 10:41 ` [PATCH v3 6/6] irqchip/renesas-rzv2h: Handle ICU error IRQ and add SWPE trigger 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=87bjhevbly.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.