From: Philippe Gerum <rpm@xenomai.org>
To: Jeroen Van den Keybus <jeroen.vandenkeybus@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Handling PCI MSI interrupts
Date: Tue, 14 Feb 2006 18:50:31 +0100 [thread overview]
Message-ID: <43F21867.8070002@domain.hid> (raw)
In-Reply-To: <fd6a47a90602140744lc1d4365q@domain.hid>
Jeroen Van den Keybus wrote:
> I'm having problems using MSI interrupts in Xenomai.
>
> When using normal PCI interrupts, my PCI card + RTDM driver work
> flawlessly. However, I noticed the following while trying to enable MSI
> (by having Linux do all the administrative register-fill-ins using
> pci_enable_msi()):
>
> 1. The kernel is compiled for MSI. (PCI_CONFIG_MSI=yes)
> 2. My card correctly advertises the MSI capability (checked with 'lspci
> -v').
> 3. I do get a new IRQ number in the pci_dev struct (217 instead of 193)
> after invoking pci_enable_msi().
> 4. After pci_enable_smi(), 'lspci -v' correctly indicates that Message
> Signalled Interrupts are now enabled (Enable+).
> 5. I can register the new IRQ with rtdm_request_irq(). Return value is 0.
> 6. The IRQ number appears in /proc/xenomai/irq.
> 7. I can enable the new IRQ with rtdm_irq_enable(). Return value is 0.
> 8. I can disable the new IRQ with rtdm_irq_disable(). Return value is 0.
> 9. I can unregister the new IRQ with rtdm_irq_free(). Return value is 0.
> 10. I'm able to do pci_disable_pci() successfully.
>
> If I actually enable the card interrupt, it goes wrong after 7 after
> arrival of the first interrupt. The ISR is executed (checked that),
> which checks if the card was actually interrupting and, if so, returns
> with RTDM_IRQ_ENABLE. After that, the machine is absolutely dead (frozen).
>
> Any hints, suggestions or things I may check ?
>
Does calling rthal_disable_irq() instead of returning RTDM_IRQ_ENABLE, but rather
0, prevents the freeze?
> Jeroen.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core
--
Philippe.
next prev parent reply other threads:[~2006-02-14 17:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 15:44 [Xenomai-core] Handling PCI MSI interrupts Jeroen Van den Keybus
2006-02-14 17:50 ` Philippe Gerum [this message]
2006-02-14 18:07 ` Jeroen Van den Keybus
2006-02-14 18:17 ` Jan Kiszka
2006-02-14 18:26 ` Philippe Gerum
2006-02-14 18:52 ` Jeroen Van den Keybus
2006-02-14 19:22 ` Jeroen Van den Keybus
2006-02-14 19:33 ` Jeroen Van den Keybus
2006-02-14 21:41 ` Jeroen Van den Keybus
2006-02-14 21:56 ` Philippe Gerum
2006-02-15 11:00 ` Jeroen Van den Keybus
2006-02-15 18:02 ` Jeroen Van den Keybus
2006-02-15 18:34 ` Jeroen Van den Keybus
2006-02-15 20:09 ` Philippe Gerum
2006-02-15 20:50 ` Jeroen Van den Keybus
2006-02-15 22:48 ` Philippe Gerum
2006-02-15 22:58 ` Jeroen Van den Keybus
2006-02-15 23:09 ` Russell Johnson
2006-02-16 9:36 ` Philippe Gerum
2006-02-16 14:23 ` Russell Johnson
2006-02-17 12:54 ` Jeroen Van den Keybus
2006-02-17 13:08 ` Philippe Gerum
2006-02-17 14:43 ` Russell Johnson
2006-02-17 15:45 ` Philippe Gerum
2006-02-17 15:57 ` Jeroen Van den Keybus
2006-02-17 16:07 ` Philippe Gerum
2006-02-17 16:49 ` Jeroen Van den Keybus
2006-02-17 18:37 ` Jeroen Van den Keybus
2006-02-17 18:39 ` Philippe Gerum
2006-02-19 18:50 ` Philippe Gerum
2006-02-14 18:23 ` Philippe Gerum
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=43F21867.8070002@domain.hid \
--to=rpm@xenomai.org \
--cc=jeroen.vandenkeybus@domain.hid \
--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.