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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1156966715.6271.211.camel@localhost.localdomain>
Date:	Wed, 30 Aug 2006 20:38:35 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Rick Brown <rick.brown.3@...il.com>
Cc:	linux-newbie@...r.kernel.org, kernelnewbies@...linux.org,
	linux-kernel@...r.kernel.org
Subject: Re: Interrupt handler registration for multiple devices

Ar Mer, 2006-08-30 am 20:42 +0530, ysgrifennodd Rick Brown:
> Hi,
> 
> I want to write a driver that will handle multiple devices. These
> devices will share the IRQ line. Do I need to register my (same)
> interrupt handler as many times as the number of devices(by calling
> request_irq())?

Up to you. If you are working with standard devices that need no special
handling to share interrupts (eg PCI bus), the device model makes it
more natural to do that and let the kernel call your handler once for
each device (passing a different dev_id).


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ