Commit a1b7febd authored by Maxime Ripard's avatar Maxime Ripard Committed by David S. Miller

genirq: Fix the documentation of request_percpu_irq

The documentation of request_percpu_irq is confusing and suggest that the
interrupt is not enabled at all, while it is actually enabled on the local
CPU.

Clarify that.
Signed-off-by: default avatarMaxime Ripard <maxime.ripard@free-electrons.com>
Signed-off-by: default avatarGregory CLEMENT <gregory.clement@free-electrons.com>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent 8a4683a5
...@@ -1790,9 +1790,10 @@ int setup_percpu_irq(unsigned int irq, struct irqaction *act) ...@@ -1790,9 +1790,10 @@ int setup_percpu_irq(unsigned int irq, struct irqaction *act)
* @devname: An ascii name for the claiming device * @devname: An ascii name for the claiming device
* @dev_id: A percpu cookie passed back to the handler function * @dev_id: A percpu cookie passed back to the handler function
* *
* This call allocates interrupt resources, but doesn't * This call allocates interrupt resources and enables the
* automatically enable the interrupt. It has to be done on each * interrupt on the local CPU. If the interrupt is supposed to be
* CPU using enable_percpu_irq(). * enabled on other CPUs, it has to be done on each CPU using
* enable_percpu_irq().
* *
* Dev_id must be globally unique. It is a per-cpu variable, and * Dev_id must be globally unique. It is a per-cpu variable, and
* the handler gets called with the interrupted CPU's instance of * the handler gets called with the interrupted CPU's instance of
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment