Skip to main content

Browse the archive

https://github.com/torvalds/linux
23 October 2021, 00:29:24 UTC
Revision ed625b9143ee53fe610320908c89e22635ee6e87 authored by Omar Ramirez Luna on 18 November 2011, 22:18:54 UTC, committed by Greg Kroah-Hartman on 14 December 2011, 00:12:06 UTC 
staging: tidspbridge: request dmtimer clocks on init
 
Given that dm timer framework doesn't support request of clocks
by soft | hard irqs because some recent changes, tidspbridge needs
to request its clocks on init and enable/disable them on demand.

This was first seen on 3.2-rc1.

Signed-off-by: Omar Ramirez Luna <omar.ramirez@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
1 parent 0a7e22e
Raw File
Tip revision: ed625b9143ee53fe610320908c89e22635ee6e87 authored by Omar Ramirez Luna on 18 November 2011, 22:18:54 UTC
staging: tidspbridge: request dmtimer clocks on init
Tip revision: ed625b9
IRQ.txt 
What is an IRQ?

An IRQ is an interrupt request from a device.
Currently they can come in over a pin, or over a packet.
Several devices may be connected to the same pin thus
sharing an IRQ.

An IRQ number is a kernel identifier used to talk about a hardware
interrupt source.  Typically this is an index into the global irq_desc
array, but except for what linux/interrupt.h implements the details
are architecture specific.

An IRQ number is an enumeration of the possible interrupt sources on a
machine.  Typically what is enumerated is the number of input pins on
all of the interrupt controller in the system.  In the case of ISA
what is enumerated are the 16 input pins on the two i8259 interrupt
controllers.

Architectures can assign additional meaning to the IRQ numbers, and
are encouraged to in the case  where there is any manual configuration
of the hardware involved.  The ISA IRQs are a classic example of
assigning this kind of additional meaning.
back to top