Re: PCI Interrupt

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 18 Sep 2007 [email protected] wrote:

> The driver already does that ...
>
> result =
>        request_irq(irq, can_pci_interrupt, SA_INTERRUPT | SA_SHIRQ,
>                    pDevice->au8IrqName, pDevice);
>
>
> Any other ideas?
>
> Duncan
>
>
>             "linux-os \(Dick
>             Johnson\)"
>             <linux-os@analogi                                          To
>             c.com>                    <[email protected]>
>                                                                        cc
>             18/09/2007 14:57          "Linux kernel"
>                                       <[email protected]>
>                                                                   Subject
>             Please respond to         Re: PCI Interrupt
>             "linux-os \(Dick
>                Johnson\)"
>             <linux-os@analogi
>                  c.com>
>
> On Tue, 18 Sep 2007 [email protected] wrote:
>
>>
>> I have a CAN PCI card installed on my Ubuntu box.
>> I understand that PCI interrupts should be level rather than edge
>> triggered.
>>
>> The output of cat /proc/interrupts is :-
>>
>>           CPU0
>>  0:    1614601    IO-APIC-edge  timer
>>  1:        164    IO-APIC-edge  i8042
>>  8:          3    IO-APIC-edge  rtc
>>  9:          1   IO-APIC-level  acpi
>> 12:          0    IO-APIC-edge  CAN-ACx-PCI_01
>> 14:      65786    IO-APIC-edge  ide0
>> 169:       3220   IO-APIC-level  eth0, i915@pci:0000:00:02.0
>> 177:      46459   IO-APIC-level  eth1
>> 209:          0   IO-APIC-level  uhci_hcd:usb3, eth2
>> 217:          2   IO-APIC-level  uhci_hcd:usb1, ehci_hcd:usb4
>> 225:        697   IO-APIC-level  uhci_hcd:usb2
>> NMI:          0
>> LOC:    1614399
>> ERR:          0
>> MIS:          0
>>
>> You see that irq 12 CAN-ACx-PCI_01 is edge triggered.
>> Is there any way of forcing the BIOS to see the interrupt as a
>> level-triggered one?
>
> It's done in the driver. IRQ12 can be shared, so the driver
> needs to request the IRQ as a shared interrupt.
>
>
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.6.22.1 on an i686 machine (5588.30 BogoMips).
> My book : http://www.AbominableFirebug.com/
> _

Okay, then in the BIOS, make sure that IRQ12 is not assigned to
a specific device. In other words, set it to PnP (if available).
As you well know, PCI requires sharable interrupts and edges
are not sharable so something is broken. As a last resort,
move your PCI board to abother slot which should pick up another
interrupt, which may not be broken. If that doesn't work, see
if a new BIOS is available for download.


Cheers,
Dick Johnson
Penguin : Linux version 2.6.22.1 on an i686 machine (5588.30 BogoMips).
My book : http://www.AbominableFirebug.com/
_


****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to [email protected] - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux