Hi, (always use reply-all) On Thu, Jan 31, 2013 at 11:12:07AM +0100, stl wrote: > Hi, > thanks for yours answers > > > which kernel version are you using ? usb_gadget_register_driver() has > > been re-factored into generic code long ago. > > Indeed, I am unfortunately using an old kernel version (2.6.19). sorry you're on your own. 2.6.19 is from 2006, can't help you. > Because of some deadlines, we have chosen to work on this, but an update to > a recent version is in progress, but it still need a certain amount of work to > be in an acceptable state. > It is for this reason that I know it will be difficult to have support. > But, even if certain function names have changed, I only want to > understand the concept > behind all of this. > > >> I have seen in some udc drivers that "resource_get_irq()" is called > > > > there is no such function in the kernel. Do you mean platform_get_irq()? > > Yes I mean platform_get_irq(), sorry for the mistake. > > >> before registering IRQ > >> with "request_irq()". > >> What is the purpose of this function? > > > > to get the proper IRQ number which is passed by platform code using > > struct resource. > > Why does the driver need to know the IRQ numbers? > request_irq() procedure is not enough to point to ISR during hardware > interrupt event? you need to attach ISR to a certain IRQ number. We don't want your ISR to be called when the MMC controller generates IRQ events. -- balbi
Attachment:
signature.asc
Description: Digital signature
