[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4E12A69C.8030709@dsn.okisemi.com>
Date: Tue, 05 Jul 2011 14:52:28 +0900
From: Tomoya MORINAGA <tomoya-linux@....okisemi.com>
To: Grant Likely <grant.likely@...retlab.ca>
CC: linux-kernel@...r.kernel.org,
alexander.stein@...tec-electronic.com, qi.wang@...el.com,
yong.y.wang@...el.com, joel.clark@...el.com,
kok.howg.ewe@...el.com, toshiharu-linux@....okisemi.com,
tglx@...utronix.de
Subject: Re: [PATCH v4] pch_gpio: Support interrupt function
(2011/07/05 12:59), Grant Likely wrote:
>> As we discussed before,
>> without specifying PCH_IRQ_BASE,
>> it seemed IRQ number collision issue occurred.
>> Thus, I added PCH_IRQ_BASE.
>
> Then fix the irq collision. If the core code hands out an irq range
> that is in-use by some other driver, then the other driver isn't
> reserving it's irqs correctly and it needs to be fixed. Hacking
> around the problem doesn't help anything in the long run.
>
I tried to work irq_alloc_descs with dynamic allocation.(Set 2nd
parameter as 0).
However it seems the issue remains to be seen.
I attached dmesg output log, /proc/interrupts log and modified PCH-GPIO
source code.
Could you give me your opinion or information ?
NOTE: I tested on linux-3.0-rc3
--
tomoya
OKI SEMICONDUCTOR CO., LTD.
View attachment "dmesg" of type "text/plain" (69150 bytes)
View attachment "interrupts" of type "text/plain" (1555 bytes)
View attachment "pch_gpio.c" of type "text/plain" (12281 bytes)
Powered by blists - more mailing lists