linux-toradex.git/kernel/irq/debugfs.c, branch v6.1-rc1

genirq: Return a const cpumask from irq_data_get_affinity_mask

2022-07-07T08:38:04+00:00

Now that the irq_data_update_affinity helper exists, enforce its use
by returning a a const cpumask from irq_data_get_affinity_mask.

Since the previous commit already updated places that needed to call
irq_data_update_affinity, this commit updates the remaining code that
either did not modify the cpumask or immediately passed the modified
mask to irq_set_affinity.

Signed-off-by: Samuel Holland 
Reviewed-by: Michael Kelley 
Signed-off-by: Marc Zyngier 
Link: https://lore.kernel.org/r/20220701200056.46555-8-samuel@sholland.org

gpio: Don't fiddle with irqchips marked as immutable

2022-04-19T14:22:25+00:00

In order to move away from gpiolib messing with the internals of
unsuspecting irqchips, add a flag by which irqchips advertise
that they are not to be messed with, and do solemnly swear that
they correctly call into the gpiolib helpers when required.

Also nudge the users into converting their drivers to the
new model.

Reviewed-by: Andy Shevchenko 
Reviewed-by: Bartosz Golaszewski 
Signed-off-by: Marc Zyngier 
Link: https://lore.kernel.org/r/20220419141846.598305-2-maz@kernel.org

genirq/debugfs: Use irq_print_chip() when provided by irqchip

2022-02-15T11:22:34+00:00

Since irqchips have the option to implement irq_print_chip, use this
when available to output the irqchip name in debugfs.

Signed-off-by: Marc Zyngier 
Link: https://lore.kernel.org/r/20220215112154.1360040-1-maz@kernel.org

Merge branch 'irq/qcom-pdc-wakeup' into irq/irqchip-next

2020-10-06T10:28:03+00:00

Signed-off-by: Marc Zyngier

genirq/PM: Introduce IRQCHIP_ENABLE_WAKEUP_ON_SUSPEND flag

2020-10-06T10:23:41+00:00

An interrupt that is disabled/masked but set for wakeup may still need to
be able to wake up the system from sleep states like "suspend to RAM".

To that effect, introduce the IRQCHIP_ENABLE_WAKEUP_ON_SUSPEND flag.
If the irqchip have this flag set, the irq PM code will enable/unmask
the irqs that are marked for wakeup, but that are in a disabled state.

On resume, such irqs will be restored back to their disabled state.

Suggested-by: Thomas Gleixner 
Signed-off-by: Maulik Shah 
[maz: commit message fix-up]
Signed-off-by: Marc Zyngier 
Tested-by: Stephen Boyd 
Reviewed-by: Thomas Gleixner 
Reviewed-by: Douglas Anderson 
Link: https://lore.kernel.org/r/1601267524-20199-4-git-send-email-mkshah@codeaurora.org

genirq: Allow interrupts to be excluded from /proc/interrupts

2020-09-13T16:04:38+00:00

A number of architectures implement IPI statistics directly,
duplicating the core kstat_irqs accounting. As we move IPIs to
being actual IRQs, we would end-up with a confusing display
in /proc/interrupts (where the IPIs would appear twice).

In order to solve this, allow interrupts to be flagged as
"hidden", which excludes them from /proc/interrupts.

Reviewed-by: Valentin Schneider 
Signed-off-by: Marc Zyngier

genirq/debugfs: Add missing irqchip flags

2020-07-27T14:20:40+00:00

Recently introduced irqchip flags lack the corresponding printouts in
debugfs. Add them.

Signed-off-by: Marc Zyngier 
Signed-off-by: Thomas Gleixner 
Link: https://lkml.kernel.org/r/874kpvydxc.wl-maz@kernel.org

genirq: Provide interrupt injection mechanism

2020-03-08T10:06:42+00:00

Error injection mechanisms need a half ways safe way to inject interrupts as
invoking generic_handle_irq() or the actual device interrupt handler
directly from e.g. a debugfs write is not guaranteed to be safe.

On x86 generic_handle_irq() is unsafe due to the hardware trainwreck which
is the base of x86 interrupt delivery and affinity management.

Move the irq debugfs injection code into a separate function which can be
used by error injection code as well.

The implementation prevents at least that state is corrupted, but it cannot
close a very tiny race window on x86 which might result in a stale and not
serviced device interrupt under very unlikely circumstances.

This is explicitly for debugging and testing and not for production use or
abuse in random driver code.

Signed-off-by: Thomas Gleixner 
Tested-by: Kuppuswamy Sathyanarayanan 
Reviewed-by: Kuppuswamy Sathyanarayanan 
Acked-by: Marc Zyngier 
Link: https://lkml.kernel.org/r/20200306130623.990928309@linutronix.de

genirq: Add return value to check_irq_resend()

2020-03-08T10:06:41+00:00

In preparation for an interrupt injection interface which can be used
safely by error injection mechanisms. e.g. PCI-E/ AER, add a return value
to check_irq_resend() so errors can be propagated to the caller.

Split out the software resend code so the ugly #ifdef in check_irq_resend()
goes away and the whole thing becomes readable.

Fix up the caller in debugfs. The caller in irq_startup() does not care
about the return value as this is unconditionally invoked for all
interrupts and the resend is best effort anyway.

Signed-off-by: Thomas Gleixner 
Acked-by: Marc Zyngier 
Link: https://lkml.kernel.org/r/20200306130623.775200917@linutronix.de

genirq/debugfs: Add missing sanity checks to interrupt injection

2020-03-08T10:06:40+00:00

Interrupts cannot be injected when the interrupt is not activated and when
a replay is already in progress.

Fixes: 536e2e34bd00 ("genirq/debugfs: Triggering of interrupts from userspace")
Signed-off-by: Thomas Gleixner 
Acked-by: Marc Zyngier 
Cc: stable@vger.kernel.org
Link: https://lkml.kernel.org/r/20200306130623.500019114@linutronix.de