linux-kernel - Re: [PATCH v4] pch_gpio: Support interrupt function

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110715201414.GK2833@ponder.secretlab.ca>
Date:	Fri, 15 Jul 2011 14:14:14 -0600
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Tomoya MORINAGA <tomoya-linux@....okisemi.com>
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

On Mon, Jul 11, 2011 at 05:27:35PM +0900, Tomoya MORINAGA wrote:
> Hi Grant,
> 
> (2011/07/05 14:52), Tomoya MORINAGA wrote:
> >(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
> >
> How is it going ?

Sounds like the platform is not correctly reserving the irq descs it
is using.  You'll need to dig into the irq desc allocation code to
debug it.

g.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/