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>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Ingo Molnar" <mingo@elte.hu>
Subject: Re: sharing interrupt between PCI device
Date: Mon, 10 Nov 2008 21:12:05 +0530 [thread overview]
Message-ID: <8d6898730811100742g31711b9ck9e046d77273d0113@mail.gmail.com> (raw)
In-Reply-To: <8d6898730811100231j2ca5e8ceub0d5137c1ef1f9d0@mail.gmail.com>
I could not find the definition of acpi_unregister_gsi in i386/x86_64
code, it is defined only for ia64.
Since it is defined as a weak symbol, I feel it is not getting called
(correct if I am wrong, I searched in google for this).
/* FIXME: implement x86/x86_64 version */
void __attribute__ ((weak)) acpi_unregister_gsi(u32 i)
{
}
How this weak symbols work, is it something like
acpi_pci_irq_disable() will not call acpi_unregister_gsi() in some
platforms.
Thanks
Nobin Mathew.
On Mon, Nov 10, 2008 at 4:01 PM, Nobin Mathew <nobin.mathew@gmail.com> wrote:
> Yes USB Virtual Controller has input devices like keyboard and mouse
> (routed through hpilo card (remote console)), so those things stops
> working when we remove hpilo driver.
>
> Thanks
> Nobin Mathew
>
> On Mon, Nov 10, 2008 at 1:28 PM, Ingo Molnar <mingo@elte.hu> wrote:
>>
>> * Grant Grundler <grundler@parisc-linux.org> wrote:
>>
>>> [+ingo - question for you about disable_irq() below]
>>
>>> The same problem exists with disable_irq() : only takes a global
>>> IRQ# and no additional identifying information to prevent disabling
>>> a shared IRQ. So I'm not sure if this is a bug with ACPI or design
>>> flaw in generic IRQ APIs. Ingo?
>>
>> that's how disable_irq() always worked: it disables all handlers on
>> that IRQ#. If the IRQ# is shared, it disables all handlers.
>>
>> Ingo
>>
>
next prev parent reply other threads:[~2008-11-10 15:42 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
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 [this message]
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=8d6898730811100742g31711b9ck9e046d77273d0113@mail.gmail.com \
--to=nobin.mathew@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--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 \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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).