Messages in this thread | | | Date | Mon, 12 Dec 2011 23:00:01 +0200 | Subject | Re: IRQF_TIMER | IRQF_SHARED ? | From | Martin-Éric Racine <> |
| |
12. joulukuuta 2011 22.31 Andres Salomon <dilinger@queued.net> kirjoitti: > On Mon, 12 Dec 2011 16:41:25 +0100 > Jens Rottmann <JRottmann@LiPPERTEmbedded.de> wrote: >> one of our customers tripped over the fact that the MFGPT driver >> won't share its IRQ with anyone else. (MFGPT defaulted to same IRQ as >> audio, MFGPT driver loaded first, audio fails.) *No big deal!* They >> don't actually need MFGPT and will simply disable it. It just made me >> wonder ... >> >> Why would it be such a bad idea to use IRQF_TIMER | IRQF_SHARED (see >> patch below)? mfgpt_tick() already does properly return IRQ_NONE when >> it feels unresponsible. I tested it with either driver loaded first >> and it seemed to work (well, at least audio worked, don't know how to >> explicitly test cs5535-clockevt). > > Just loading cs5535-clockevt should start the periodic timer. On my > XO-1, IRQ 7 starts firing immediately.
Could it be a good idea to inform udev maintainers of this?
Martin-Éric -- 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/
| |