Re: interrupt handler problem (request_irq in module)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



AFAIK, it is not a problem.
BTW, what irq line are you requesting for? If this irq line is shared 
with some other device, then please add a statement in your interrupt 
handler checking wether this interrupt is for your device. You can 
check this using the device id.

Hope this helps,

Thanks,
Sumit
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1EC24.9567967A"


------_=_NextPart_001_01C1EC24.9567967A
Content-Type: text/plain;
	charset="ks_c_5601-1987"

Hi all,
 
I'm developing device driver which handles IR interrupt.
I started it with well-operating qtronix 990p keyboard driver source code 
that is built static in the kernel.
I said N for the device in kernel configuation, and modified the source code
in order to make it insmod-able.
and i placed request_irq and some other initializations in the
module_init();
and then i modified the handler to do printk("interrupt...\n"); only.
 
I compiled and insmoded the module (i checked that it was in
/proc/interrupts).
When I pressed the keyboard the answer was,
 
interrupt...
interrupt...
interrupt...
...(forever, sometimes hangs in a few seconds of scrolling down, 
    either way i have to reset the board.)
 
while it is supposed to be only one "interrupt..."
 
Is it illegal to place request_irq in the init_module?
Please help.
 
Thanks in advance.
 
   Theo.
 
 
 

------_=_NextPart_001_01C1EC24.9567967A
Content-Type: text/html;
	charset="ks_c_5601-1987"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ks_c_5601-1987">
<TITLE>linen_small Stationery</TITLE>

<META content="MSHTML 5.50.4913.1100" name=GENERATOR></HEAD>
<BODY 
style="FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY: Courier New; BACKGROUND-COLOR: #ffffff" 
bgColor=#ffffff background=cid:518582806@25042002-14b5>
<DIV><SPAN class=518582806-25042002>Hi all,</SPAN></DIV>
<DIV><SPAN class=518582806-25042002></SPAN>&nbsp;</DIV>
<DIV><SPAN class=518582806-25042002>I'm developing device driver&nbsp;which 
handles IR interrupt.</SPAN></DIV>
<DIV><SPAN class=518582806-25042002>I started it with well-operating qtronix 
990p keyboard driver source code </SPAN></DIV>
<DIV><SPAN class=518582806-25042002>that is built static in the 
kernel.</SPAN></DIV>
<DIV><SPAN class=518582806-25042002>I said N for the device in kernel 
configuation, and modified the source code</SPAN></DIV>
<DIV><SPAN class=518582806-25042002>in order to make it 
insmod-able.</SPAN></DIV>
<DIV><SPAN class=518582806-25042002>and i&nbsp;placed request_irq and some other 
initializations in the module_init();</SPAN></DIV>
<DIV><SPAN class=518582806-25042002>and then i modified the handler to&nbsp;do 
printk("interrupt...\n"); only.</SPAN></DIV>
<DIV><SPAN class=518582806-25042002></SPAN>&nbsp;</DIV>
<DIV><SPAN class=518582806-25042002>I&nbsp;compiled and insmoded the 
module&nbsp;(i checked that it was&nbsp;in /proc/interrupts).</SPAN></DIV>
<DIV><SPAN class=518582806-25042002>When I pressed the keyboard the answer 
was,</SPAN></DIV>
<DIV><SPAN class=518582806-25042002></SPAN>&nbsp;</DIV>
<DIV><SPAN class=518582806-25042002>interrupt...</SPAN></DIV>
<DIV><SPAN class=518582806-25042002>interrupt...</SPAN></DIV>
<DIV><SPAN class=518582806-25042002>
<DIV><SPAN class=518582806-25042002>interrupt...</SPAN></DIV>
<DIV><SPAN class=518582806-25042002>...</SPAN><SPAN 
class=518582806-25042002>(forever, sometimes hangs in a few seconds of scrolling 
down,&nbsp;</SPAN></DIV>
<DIV><SPAN class=518582806-25042002>&nbsp;&nbsp;&nbsp;&nbsp;either way&nbsp;i 
have to reset the board.)</SPAN></DIV>
<DIV><SPAN class=518582806-25042002></SPAN>&nbsp;</DIV>
<DIV><SPAN class=518582806-25042002>while it is supposed to&nbsp;be&nbsp;only 
one "interrupt..."</SPAN></DIV>
<DIV><SPAN class=518582806-25042002></SPAN>&nbsp;</DIV>
<DIV><SPAN class=518582806-25042002>
<DIV><SPAN class=518582806-25042002>Is it illegal to&nbsp;place request_irq in 
the init_module?</SPAN></DIV></SPAN></DIV>
<DIV><SPAN class=518582806-25042002>Please help.</SPAN></DIV>
<DIV><SPAN class=518582806-25042002></SPAN>&nbsp;</DIV>
<DIV><SPAN class=518582806-25042002>Thanks in advance.</SPAN></DIV>
<DIV><SPAN class=518582806-25042002></SPAN>&nbsp;</DIV>
<DIV><SPAN class=518582806-25042002>&nbsp;&nbsp; Theo.</SPAN></DIV>
<DIV><SPAN class=518582806-25042002></SPAN>&nbsp;</DIV>
<DIV><SPAN class=518582806-25042002></SPAN><SPAN 
class=518582806-25042002></SPAN><SPAN class=518582806-25042002></SPAN><SPAN 
class=518582806-25042002></SPAN><SPAN 
class=518582806-25042002></SPAN>&nbsp;</DIV></SPAN></DIV>
<DIV><SPAN class=518582806-25042002></SPAN>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C1EC24.9567967A--
begin:vcard
n:Agarwal;Sumit
fn:Sumit Agarwal
tel;cell:+919845205210
tel;fax:+91-80-5732696
tel;home:+919845205210
tel;work:+91-805732296 / 93 extn. 5243
url:www.wipro.com
org:Wipro Technologies;SIDC, Embedded and Internet Division
adr:;;Wipro Technologies, Chamundi Complex, No.26, Hosur Main Road, Bommanahalli;Bangalore;Karnataka;560068;INDIA
version:2.1
email;internet:sumit.agarwal@wipro.com
title:Senior Software Engineer
end:vcard


**************************Disclaimer************************************
Information contained in this E-MAIL being proprietary to Wipro Limited
is 'privileged' and 'confidential' and intended for use only by the
individual or entity to which it is addressed. You are notified that any
use, copying or dissemination of the information contained in the E-MAIL
in any manner whatsoever is strictly prohibited.
********************************************************************

[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux