On 12/03/2025 11:00:00+0100, Wolfram Sang wrote:
> It is good practice to clear running interrupts before removing the
> driver. This is not really a bugfix because on current systems RuntimePM
This is not completely true, most of the drivers would leave the
interrupt enabled after removing the driver because it can still
power on a device.
> will disable the module clock, so interrupts won't be initiated. The
> dependency on that behaviour is subtle, though. Better be self-contained
> and clean up when removing.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@xxxxxxxxxxxxxxxxxxxx>
> ---
>
> Change since v1: fix build failure by adding the 'rtc' variable. Build
> and tested on Renesas RZ/N1D.
>
> drivers/rtc/rtc-rzn1.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/rtc/rtc-rzn1.c b/drivers/rtc/rtc-rzn1.c
> index eeb9612a666f..3c2861983ff1 100644
> --- a/drivers/rtc/rtc-rzn1.c
> +++ b/drivers/rtc/rtc-rzn1.c
> @@ -444,6 +444,11 @@ static int rzn1_rtc_probe(struct platform_device *pdev)
>
> static void rzn1_rtc_remove(struct platform_device *pdev)
> {
> + struct rzn1_rtc *rtc = platform_get_drvdata(pdev);
> +
> + /* Disable all interrupts */
> + writel(0, rtc->base + RZN1_RTC_CTL1);
> +
> pm_runtime_put(&pdev->dev);
> }
>
> --
> 2.47.2
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
