RE: [PATCH 1/1] arm64: kexec: no need to do irq_chip->irq_mask if it already masked
From: Jason Liu
Date: Wed Aug 05 2020 - 02:30:20 EST
> -----Original Message-----
> From: Sudeep Holla <sudeep.holla@xxxxxxx>
> Sent: Tuesday, August 4, 2020 6:20 PM
> To: Jason Liu <jason.hui.liu@xxxxxxx>
> Cc: will@xxxxxxxxxx; catalin.marinas@xxxxxxx; ashal@xxxxxxxxxx;
> maz@xxxxxxxxxx; linux-arm-kernel@xxxxxxxxxxxxxxxxxxx;
> Subject: Re: [PATCH 1/1] arm64: kexec: no need to do irq_chip->irq_mask if it
> already masked
> +Marc Z
> On Tue, Aug 04, 2020 at 04:56:57PM +0800, Jason Liu wrote:
> > No need to do the irq_chip->irq_mask() if it already masked.
> > BTW, unconditionally do the irq_chip->irq_mask() will also bring
> > issues when the irq_chip in the runtime PM suspend. Accessing
> > registers of the irq_chip will bring in the exceptions. For example on the i.MX:
> The change looks good and is inline with the additional checks we do for eoi
> and disable. However, the imx_irqsteer_irq_mask is not safe to be called with
> runtime suspend.
Yes, you are right. imx_irqsteer_irq_mask can not be called with irqchip runtime suspend.
IMO, this might apply to all platforms which implement the irq_chip->mask function with
directly access the registers.
> What happens if some driver using the irq on this chip calls
> disable_irq when this irqchip is suspended ?
IMO, only free_irq will call the irq_chip_pm_put which will bring the irqchip to suspend if that irq is the last user.
Otherwise, the irqchip is in active state. free_irq will set the IRQ state to DISABLED and MASKED.
So, if the irqchip in suspend state, which means all the irqs(associated with irqchip) were DISABLED and MASKED.
If call the common API disable_irq, that is fine due to the disable_irq will nop if the irq was DISABLED and masked.