Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1198382 > unrolled thread
| Started by | Thomas Gleixner <tglx@linutronix.de> |
|---|---|
| First post | 2015-08-02 11:20 +0200 |
| Last post | 2015-08-02 11:20 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH 1/3] clocksource: atmel-st: Remove irq handler when clock event is unused Thomas Gleixner <tglx@linutronix.de> - 2015-08-02 11:20 +0200
| From | Thomas Gleixner <tglx@linutronix.de> |
|---|---|
| Date | 2015-08-02 11:20 +0200 |
| Subject | Re: [PATCH 1/3] clocksource: atmel-st: Remove irq handler when clock event is unused |
| Message-ID | <pSXB0-80B-7@gated-at.bofh.it> |
On Mon, 20 Jul 2015, Thomas Gleixner wrote: > On Mon, 20 Jul 2015, Alexandre Belloni wrote: > > > On 20/07/2015 at 11:04:30 +0200, Thomas Gleixner wrote : > > > That's why I used setup/remove_irq() in the stale RT changes. > > > > > > > Hum, actually, you hit the same thing with setup/remove_irq (and I'm not sure > > to follow why): > > It's the kmalloc of the proc interface. So back to the drawing > board. I'll think about it tomorrow with brain awake. So the only idea I could come up with is the old approach of creating a dummy irq chip for the interrupts which share that timer/uart/rtc whatever line. I think Boris Brezillon had implemented it at some point, but it was shot down for reasons I can't remember. That would allow us to simply have disable_irq_nosync/enable_irq in the relevant code pathes and be done with it. I guess I need to find the references and give it a try again if nobody beats me to it. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to top | Article view | linux.kernel
csiph-web