All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Hänel-Baas, Alexander" <alexander.haenel-baas@sieb-meyer.de>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] arch arm no pci irq
Date: Thu, 15 Jan 2015 12:20:13 +0100	[thread overview]
Message-ID: <20150115112013.GD22199@hermes.click-hack.org> (raw)
In-Reply-To: <9BA84827B30CBE4996725F98F7DC9123428FAE5D@SMExchange01.siebmeyer.org>

On Thu, Jan 15, 2015 at 11:09:11AM +0000, Hänel-Baas, Alexander wrote:
> Hi
> 
> I have the kernel 3.14.17 with xenomai 2.6.4 and my own pci-fpga card that generates interrupts.
> 
> When i registry my pci irq with rt_intr_create() than i get the following warning and no irq was fired.
> 
> The same configuration under x86 arch works fine.
> 
> Dmesg output:
> sm36500001: ioctl(SM36500001_IOCGIRQ) =  385 <- this is the irq number that i get after i called pci_enable_msi() in the driver
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 766 at arch/arm/kernel/ipipe.c:158 ipipe_set_irq_affinity+0xa0/0xe0()

You are running an SMP kernel, is this really what you want ? (note
that this is unrelated to the problem you have).

> (...)
> 
> Any idias what is going wrong?

Does it work if you call rt_intr_enable after rt_intr_create ? 
If no, does it work if you call request_irq for the same interrupt ? 
If yes, does it work work if you use the I-pipe kernel from the
for-ipipe-3.14 branch of the ipipe-gch git repository ?

-- 
					    Gilles.


      reply	other threads:[~2015-01-15 11:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15 11:09 [Xenomai] arch arm no pci irq Hänel-Baas, Alexander
2015-01-15 11:20 ` Gilles Chanteperdrix [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150115112013.GD22199@hermes.click-hack.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=alexander.haenel-baas@sieb-meyer.de \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.