linux-kernel - RE: Question: GPIO driver how to get irq

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]

Date:	Thu, 12 May 2011 21:01:04 +0900
From:	"Tomoya MORINAGA" <tomoya-linux@....okisemi.com>
To:	"'Lars-Peter Clausen'" <lars@...afoo.de>,
	"'Grant Likely'" <grant.likely@...retlab.ca>
Cc:	<linux-kernel@...r.kernel.org>, <toshiharu-linux@....okisemi.com>
Subject: RE: Question: GPIO driver how to get irq_base

 Hi Lars, Grant

According to "/proc/interrupts", IRQ18 is not empty.
However, irq_alloc_descs returns "18".
I suspect irq_alloc_descs returns should not return "18".

> Grant,
Let me know your opinion.

With Best Regards,
-----------------------------------------
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.

> -----Original Message-----
> From: Lars-Peter Clausen [mailto:lars@...afoo.de] 
> Sent: Thursday, May 12, 2011 4:20 AM
> To: Tomoya MORINAGA
> Cc: 'Grant Likely'; linux-kernel@...r.kernel.org; 
> toshiharu-linux@....okisemi.com
> Subject: Re: Question: GPIO driver how to get irq_base
> 
> On 05/09/2011 10:54 PM, Tomoya MORINAGA wrote:
> > Hi Lars,
> > 
> > Did you see this email ?
> > I'm waiting for your response.
> > 
> 
> Hi
> 
> Well, it looks as if io-apic assumes that IRQ18 is reserved 
> for itself, while it actually is requested by your driver. 
> But that's all I can say. I'm not familiar with the x86 irq 
> code, so I've no idea what the proper fix would be.
> 
> - Lars
> 

--
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/