linux-toradex.git/kernel/irq/resend.c, branch v3.0.44

genirq: Remove compat code

2011-03-29T12:48:19+00:00

Signed-off-by: Thomas Gleixner

genirq: Mirror irq trigger type bits in irq_data.state

2011-02-19T11:58:20+00:00

That's the data structure chip functions get provided. Also allow them
to signal the core code that they updated the flags in irq_data.state
by returning IRQ_SET_MASK_OK_NOCOPY. The default is unchanged.

The type bits should be accessed via:

val = irqd_get_trigger_type(irqdata);
and
irqd_set_trigger_type(irqdata, val);

Coders who access them directly will be tracked down and slapped with
stinking trouts.

Signed-off-by: Thomas Gleixner

genirq: Move IRQ_PENDING flag to core

2011-02-19T11:58:17+00:00

Keep status in sync until all users are fixed.

Signed-off-by: Thomas Gleixner

genirq: Move IRQ_REPLAY and IRQ_WAITING to core

2011-02-19T11:58:16+00:00

No users outside of core.

Signed-off-by: Thomas Gleixner

genirq: Consolidate IRQ_DISABLED

2011-02-19T11:58:11+00:00

Handle IRQ_DISABLED consistent.

Signed-off-by: Thomas Gleixner

genirq: Consolidate disable/enable

2011-02-19T11:58:10+00:00

Create irq_disable/enable and use them to keep the flags consistent.

Signed-off-by: Thomas Gleixner

genirq: Prevent access beyond allocated_irqs bitmap

2011-02-19T11:10:51+00:00

Lars-Peter Clausen pointed out:

   I stumbled upon this while looking through the existing archs using
   SPARSE_IRQ.  Even with SPARSE_IRQ the NR_IRQS is still the upper
   limit for the number of IRQs.

   Both PXA and MMP set NR_IRQS to IRQ_BOARD_START, with
   IRQ_BOARD_START being the number of IRQs used by the core.

   In various machine files the nr_irqs field of the ARM machine
   defintion struct is then set to "IRQ_BOARD_START + NR_BOARD_IRQS".

   As a result "nr_irqs" will greater then NR_IRQS which then again
   causes the "allocated_irqs" bitmap in the core irq code to be
   accessed beyond its size overwriting unrelated data.

The core code really misses a sanity check there.

This went unnoticed so far as by chance the compiler/linker places
data behind that bitmap which gets initialized later on those affected
platforms.

So the obvious fix would be to add a sanity check in early_irq_init()
and break all affected platforms. Though that check wants to be
backported to stable as well, which will require to fix all known
problematic platforms and probably some more yet not known ones as
well. Lots of churn.

A way simpler solution is to allocate a slightly larger bitmap and
avoid the whole churn w/o breaking anything. Add a few warnings when
an arch returns utter crap.

Reported-by: Lars-Peter Clausen 
Signed-off-by: Thomas Gleixner 
Cc: stable@kernel.org # .37
Cc: Haojian Zhuang 
Cc: Eric Miao 
Cc: Peter Zijlstra

genirq: Provide compat handling for chip->retrigger()

2010-10-04T10:43:50+00:00

Wrap the old chip function retrigger() until the migration is complete
and the old chip functions are removed.

Signed-off-by: Thomas Gleixner 
Cc: Peter Zijlstra 
LKML-Reference: <20100927121843.025801092@linutronix.de>
Reviewed-by: H. Peter Anvin 
Reviewed-by: Ingo Molnar

genirq: Provide compat handling for chip->enable()

2010-10-04T10:43:42+00:00

Wrap the old chip function enable() until the migration is complete and
the old chip functions are removed.

Signed-off-by: Thomas Gleixner 
Cc: Peter Zijlstra 
LKML-Reference: <20100927121842.437159182@linutronix.de>
Reviewed-by: H. Peter Anvin 
Reviewed-by: Ingo Molnar

genirq: Convert core code to irq_data

2010-10-04T10:36:26+00:00

Convert all references in the core code to orq, chip, handler_data,
chip_data, msi_desc, affinity to irq_data.*

Signed-off-by: Thomas Gleixner 
Reviewed-by: Ingo Molnar