thermal/drivers/rcar_gen3: Handle -ENXIO from optional IRQ lookup
Subsystems (5)
PATCH v2 1/2 thermal/drivers/rcar_gen3: Handle -ENXIO from optional IRQ lookup
From: bui duc phuc <[email protected]>
rcar_gen3_thermal_request_irqs() may return -ENXIO when no optional IRQ is available. The caller currently treats all negative return values the same way, disabling hardware trip-point support and continuing probe.
Distinguish -ENXIO from other errors so that the existing behavior is preserved when the optional IRQ is absent, while errors such as -EPROBE_DEFER, -EINVAL, and other failures are propagated to the caller.
---
Link v1 :
https://lore.kernel.org/all/[email protected]/
Changes in v2:
- Update the commit message.
- Move error handling to the caller.
drivers/thermal/renesas/rcar_gen3_thermal.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/thermal/renesas/rcar_gen3_thermal.c +4 -1
@@ -527,8 +527,11 @@ static int rcar_gen3_thermal_probe(struct platform_device *pdev) priv->info =of_device_get_match_data (dev);platform_set_drvdata (pdev, priv); -if (rcar_gen3_thermal_request_irqs (priv, pdev)) + ret =rcar_gen3_thermal_request_irqs (priv, pdev); +if (ret == -ENXIO ) priv->ops.set_trips =NULL ; +else if (ret) +return ret;pm_runtime_enable (dev);pm_runtime_get_sync (dev);
Signature · 1 line
2.43.0
PATCH v2 2/2 thermal/drivers/brcmstb_thermal: Propagate errors from optional IRQ lookup
From: bui duc phuc <[email protected]>
platform_get_irq_optional() returns a positive IRQ number on success or a negative error code on failure. For an optional IRQ, -ENXIO indicates that no IRQ is available, while other errors should be propagated.
Propagate errors such as -EPROBE_DEFER and -EINVAL instead of continuing probe without the IRQ.
--- drivers/thermal/broadcom/brcmstb_thermal.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/thermal/broadcom/brcmstb_thermal.c +3 -1
@@ -350,7 +350,9 @@ static int brcmstb_thermal_probe(struct platform_device *pdev) priv->thermal = thermal; irq =platform_get_irq_optional (pdev,0 ); -if (irq >=0 ) { +if (irq <0 && irq != -ENXIO ) +return irq; +if (irq >0 ) { ret = devm_request_threaded_irq(&pdev->dev, irq, NULL, brcmstb_tmon_irq_thread, IRQF_ONESHOT,
Signature · 1 line
2.43.0
Niklas Söderlund
maintainerHi Bui,
Thanks for your work.
Quoted 28 lines · On 2026-08-10 18:18:40 +0700, [email protected] wrote:
From: bui duc phuc <[email protected]>
rcar_gen3_thermal_request_irqs()may return-ENXIOwhen no optional IRQ is available. The caller currently treats all negative return values the same way, disabling hardware trip-point support and continuing probe.Distinguish
-ENXIOfrom other errors so that the existing behavior is preserved when the optional IRQ is absent, while errors such as -EPROBE_DEFER,-EINVAL, and other failures are propagated to the caller.Signed-off-by bui duc phuc <[email protected]>---
Link v1 :
https://lore.kernel.org/all/[email protected]/
Changes in v2:
- Update the commit message.
- Move error handling to the caller.drivers/thermal/renesas/rcar_gen3_thermal.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)drivers/thermal/renesas/rcar_gen3_thermal.c +0
-0
drivers/thermal/renesas/rcar_gen3_thermal.c static int rcar_gen3_thermal_probe(struct platform_device *pdev) · line 534
Quoted 9 lines
drivers/thermal/renesas/rcar_gen3_thermal.c +4
-1@@ -527,8 +527,11 @@ static int rcar_gen3_thermal_probe(struct platform_device *pdev) priv->info =of_device_get_match_data (dev);platform_set_drvdata (pdev, priv); -if (rcar_gen3_thermal_request_irqs (priv, pdev)) + ret =rcar_gen3_thermal_request_irqs (priv, pdev); +if (ret == -ENXIO ) priv->ops.set_trips =NULL ; +else if (ret) +return ret;
I'm not sure I like this.
The old behavior is that for any reason we can't get the optional IRQ the driver still works, but without hardware trip points.
While the new behavior is that if *something* other then the IRQ not being available we fail probe. What is the gain here? What benefit is there from the driver not providing thermal readouts if say for example getting the optional IRQ would return -EINVAL ?
Quoted 6 lines
drivers/thermal/renesas/rcar_gen3_thermal.c +0
-0pm_runtime_enable (dev);pm_runtime_get_sync (dev);Signature · 1 line
2.43.0
Signature · 2 lines
Kind Regards, Niklas Söderlund
Hi Niklas,
Thank you for your feedback.
Quoted 7 lines
drivers/thermal/renesas/rcar_gen3_thermal.c static int rcar_gen3_thermal_probe(struct platform_device *pdev) · line 534
Quoted 6 lines
drivers/thermal/renesas/rcar_gen3_thermal.c +4
-1-if (rcar_gen3_thermal_request_irqs (priv, pdev)) + ret =rcar_gen3_thermal_request_irqs (priv, pdev); +if (ret == -ENXIO ) priv->ops.set_trips =NULL ; +else if (ret) +return ret;
Quoted 5 lines
I'm not sure I like this.
The old behavior is that for any reason we can't get the optional IRQ the driver still works, but without hardware trip points.
Regarding the old behavior, it was handled like this:
------------------------------
irq = platform_get_irq_optional(pdev, i);
if (irq < 0)
return irq;------------------------------
As I understand it, this is essentially the behavior of platform_get_irq() itself:
https://elixir.bootlin.com/linux/v7.2-rc6/source/drivers/base/platform.c#L301
This could be understood as rcar-gen3 not actually supporting an optional IRQ. If you still want to keep the old behavior, then I think we should switch to platform_get_irq() instead of platform_get_irq_optional(), since using the latter
could give a misleading impression that rcar-gen3 supports an optional IRQ.
Incidentally, I also don't quite understand why rcar-gen2 supports an optional IRQ
while rcar-gen3 does not. Is there a hardware limitation on rcar-gen3 that requires
the IRQ to be present, or is this just a difference in the driver implementation?
https://elixir.bootlin.com/linux/v7.2-rc6/source/drivers/thermal/renesas/rcar_thermal.c#L422
Quoted 5 lines
While the new behavior is that if *something* other then the IRQ not being available we fail probe. What is the gain here? What benefit is there from the driver not providing thermal readouts if say for example getting the optional IRQ would return
-EINVAL?
Regarding the benefit of the new behavior:
If rcar-gen3 actually supports an optional IRQ, I think the benefit is that it reflects
the actual state of the system. It allows the developer to know that something went
wrong and investigate or fix the underlying issue. In the case of -EPROBE_DEFER,
the benefit is even clearer, as it allows the kernel to defer the probe and retry it later
when the dependency becomes available.
If we silently ignore the error as we do currently, the driver may still be able to provide
thermal information as you mentioned. However, can we still guarantee the correctness
and safety of the system?
Best regards,
Phuc
Hi Phuc,
Quoted 14 lines · Bui Duc Phuc
Quoted 11 lines
drivers/thermal/renesas/rcar_gen3_thermal.c static int rcar_gen3_thermal_probe(struct platform_device *pdev) · line 534
Quoted 6 lines
drivers/thermal/renesas/rcar_gen3_thermal.c +4
-1-if (rcar_gen3_thermal_request_irqs (priv, pdev)) + ret =rcar_gen3_thermal_request_irqs (priv, pdev); +if (ret == -ENXIO ) priv->ops.set_trips =NULL ; +else if (ret) +return ret;I'm not sure I like this.
The old behavior is that for any reason we can't get the optional IRQ the driver still works, but without hardware trip points.
Regarding the old behavior, it was handled like this:
------------------------------
Quoted 8 lines
irq = platform_get_irq_optional(pdev, i); if (irq < 0) return irq;------------------------------
As I understand it, this is essentially the behavior ofplatform_get_irq()itself:https://elixir.bootlin.com/linux/v7.2-rc6/source/drivers/base/platform.c#L301
Except that platform_get_irq() prints an error message, too, which we want to suppress.
Quoted 6 lines
This could be understood as rcar-gen3 not actually supporting an optional IRQ. If you still want to keep the old behavior, then I think we should switch to
platform_get_irq()instead ofplatform_get_irq_optional(), since using the latter
could give a misleading impression that rcar-gen3 supports an optional IRQ.
Quoted 6 lines
Incidentally, I also don't quite understand why rcar-gen2 supports an optional IRQ
while rcar-gen3 does not. Is there a hardware limitation on rcar-gen3 that requires
the IRQ to be present, or is this just a difference in the driver implementation?
On R-Car Gen3, thermal has an interrupt.
On R-Car Gen4, thermal does not have an interrupt, but routes this signal to the ECM.
Quoted 12 lines
Regarding the benefit of the new behavior:
If rcar-gen3 actually supports an optional IRQ, I think the benefit is that it reflects
the actual state of the system. It allows the developer to know that something went
wrong and investigate or fix the underlying issue. In the case of-EPROBE_DEFER,
the benefit is even clearer, as it allows the kernel to defer the probe and retry it later
when the dependency becomes available.
Quoted 5 lines
If we silently ignore the error as we do currently, the driver may still be able to provide
thermal information as you mentioned. However, can we still guarantee the correctness
and safety of the system?
-EPROBE_DEFER should indeed be handled correctly.
Gr{oetje,eeting}s,
Geert
Signature · 5 lines
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected] 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