From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 16 Feb 2015 11:48:31 +0100 From: Gilles Chanteperdrix Message-ID: <20150216104831.GD1914@hermes.click-hack.org> References: <20150216092513.GA1914@hermes.click-hack.org> <20150216100128.GC1914@hermes.click-hack.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Xenomai] rtdm_irq_request not registering irq List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: JAY KOTHARI Cc: xenomai On Mon, Feb 16, 2015 at 04:10:56PM +0530, JAY KOTHARI wrote: > On 2/16/15, Gilles Chanteperdrix wrote: > > On Mon, Feb 16, 2015 at 03:22:07PM +0530, JAY KOTHARI wrote: > >> I am using beaglebone black with Linux 3.8.13 and Xenomai 2.6.3. > > > > There is no reason to use Xenomai 2.6.3, you should be using xenomai > > 2.6.4. Both releases are ABI compatible. > > > >> In > >> the original Linux driver (without RTDM driver) they are implementing > >> same irq_number for request_irq API. So I believe the same irq number > >> must work for rtdm_irq_request in my RTDM driver. > >> > >> I looked into /proc/xenomai/irq my irq is shown registered but its not > >> working. > >> > >> How I use to request_irq and rtrm_irq_request together to solve this > >> approach?? Do you mean I request irq with both api?? > >> Then how do I implement irq handler and get argument like > >> dev_id(request_irq) or void * arg(rtdm_irq_request)???? > > > > Please, no top posting. No need for bazillions of question marks > > either. > > > Sorry for it. > > > Yes, I mean request the irq with both API, pass a dummy handler to > > request_irq, it will never be called anyway if the handler > > registered with rtdm_irq_request do not return XN_ISR_PROPAGATE. > > > > Again I have query about rtdm_irq_request. As my RTDM driver is not > getting interrupted then how will it go into handler of > rtdm_irq_request and return XN_ISR_PROPAGATE? Interrupt is registered > in /proc/xenomai/isr but not responding. You have misunderstood my answer. Please read it again. -- Gilles.