LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Nobin Mathew" <nobin.mathew@gmail.com>
To: "Grant Grundler" <grundler@parisc-linux.org>
Cc: "Jiri Slaby" <jirislaby@gmail.com>,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	"Robert Hancock" <hancockr@shaw.ca>
Subject: Re: sharing interrupt between PCI device
Date: Mon, 10 Nov 2008 12:17:10 +0530	[thread overview]
Message-ID: <8d6898730811092247u2d376f60u6bb74dd40fe81326@mail.gmail.com> (raw)
In-Reply-To: <8d6898730811092239s3397ef6bw4bb5934de258786e@mail.gmail.com>

Version of the running kernel 2.6.18-92.el5.

Thanks

On Mon, Nov 10, 2008 at 12:09 PM, Nobin Mathew <nobin.mathew@gmail.com> wrote:
> lspci -vs 1:4 is taken before inserting the drivers.
>
> Thanks
>
> On Mon, Nov 10, 2008 at 12:05 PM, Nobin Mathew <nobin.mathew@gmail.com> wrote:
>> lspci output
>>
>> [root@localhost ~]# lspci -vs 1:4
>> 01:04.0 System peripheral: Compaq Computer Corporation Integrated
>> Lights Out Controller (rev 03)
>>        Subsystem: Hewlett-Packard Company Unknown device 3305
>>        Flags: medium devsel, IRQ 11
>>        I/O ports at 2800 [size=256]
>>        Memory at fdee0000 (32-bit, non-prefetchable) [size=512]
>>        Capabilities: [f0] Power Management version 3
>>
>> 01:04.2 System peripheral: Compaq Computer Corporation Integrated
>> Lights Out  Processor (rev 03)
>>        Subsystem: Hewlett-Packard Company Unknown device 3305
>>        Flags: medium devsel, IRQ 225
>>        BIST result: 00
>>        I/O ports at 1400 [disabled] [size=256]
>>        Memory at fded0000 (32-bit, non-prefetchable) [disabled] [size=2K]
>>        Memory at fdec0000 (32-bit, non-prefetchable) [disabled] [size=8K]
>>        Memory at fde00000 (32-bit, non-prefetchable) [disabled] [size=512K]
>>        [virtual] Expansion ROM at fdd20000 [disabled] [size=64K]
>>        Capabilities: [f0] Power Management version 3
>>
>> 01:04.4 USB Controller: Hewlett-Packard Company Proliant iLO2 virtual
>> USB controller (prog-if 00 [UHCI])
>>        Subsystem: Hewlett-Packard Company Unknown device 3305
>>        Flags: medium devsel, IRQ 225
>>        I/O ports at 1800 [disabled] [size=32]
>>        Capabilities: [f0] Power Management version 3
>>
>> 01:04.6 IPMI SMIC interface: Hewlett-Packard Company Proliant iLO2
>> virtual UART (prog-if 01)
>>        Subsystem: Hewlett-Packard Company Unknown device 3305
>>        Flags: medium devsel, IRQ 50
>>        Memory at fddf0000 (32-bit, non-prefetchable) [size=256]
>>        Capabilities: [f0] Power Management version 3
>>
>> dmesg messages and /proc/interupts are attached.
>>
>>
>> command sequence just for reference
>>
>> insmod hpilo
>> insmod uhci_hcd
>> cat /proc/interrupts
>> dmesg
>> rmmod hpilo
>> rmmod uhci_hcd
>> dmesg
>>
>> Thanks
>> Nobin Mathew
>>
>> On Sun, Nov 9, 2008 at 12:45 AM, Grant Grundler
>> <grundler@parisc-linux.org> wrote:
>>> On Sat, Nov 08, 2008 at 08:10:54PM +0100, Jiri Slaby wrote:
>>>> Grant Grundler napsal(a):
>>>> > So I see how the IRQ is enabled and disabled. I still don't see where
>>>> > an interrupt handler is bound to IRQ 225 (output you posted today in
>>>> > another email).
>>>>
>>>> This irq setup is done during pci_enable_device.
>>>
>>> Sorry, I wasn't quite correct: pci_enable_device() should only assign IRQs,
>>> not enable them. request_irq() would enable them.
>>>
>>>> > Nobin, can you dump /proc/interrupts when both drivers
>>>> > are loaded and also send the dmesg output after both are loaded?
>>>>
>>>> This won't show the hp driver as it doesn't request_irq.
>>>
>>> Yup - that's what I expect too. But I was afraid something else might
>>> be calling request_irq() and I'm just not seeing it. :)
>>>
>>> grant
>>>
>>
>

  reply	other threads:[~2008-11-10  6:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.h7+lofM1lpbRM5V4/ti5d7RwXuM@ifi.uio.no>
2008-11-05  0:28 ` sharing interrupt between PCI device Robert Hancock
2008-11-05  7:49   ` Nobin Mathew
2008-11-05  8:36     ` Jiri Slaby
2008-11-05  9:20       ` Nobin Mathew
2008-11-06  6:11         ` Nobin Mathew
2008-11-06  7:44           ` Nobin Mathew
2008-11-06 21:24             ` Jiri Slaby
2008-11-07  5:46               ` Nobin Mathew
2008-11-08  7:57         ` Grant Grundler
2008-11-08  9:49           ` Jiri Slaby
2008-11-08 11:53             ` Nobin Mathew
2008-11-08 11:57               ` Jiri Slaby
2008-11-08 17:27     ` Grant Grundler
2008-11-08 19:10       ` Jiri Slaby
2008-11-08 19:15         ` Grant Grundler
2008-11-10  6:35           ` Nobin Mathew
2008-11-10  6:39             ` Nobin Mathew
2008-11-10  6:47               ` Nobin Mathew [this message]
2008-11-10  7:51             ` Grant Grundler
2008-11-10  7:58               ` Ingo Molnar
2008-11-10 10:31                 ` Nobin Mathew
2008-11-10 15:42                   ` Nobin Mathew
2008-11-10 20:34                     ` Grant Grundler
2008-11-11  4:57                       ` Nobin Mathew
2008-11-11 16:24                         ` Altobelli, David
2008-11-11 18:49                           ` Robert Hancock
2008-11-10 20:33                 ` Grant Grundler
2008-11-03 13:32 Nobin Mathew
2008-11-03 14:44 ` Jiri Slaby

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=8d6898730811092247u2d376f60u6bb74dd40fe81326@mail.gmail.com \
    --to=nobin.mathew@gmail.com \
    --cc=grundler@parisc-linux.org \
    --cc=hancockr@shaw.ca \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).