public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James-l7zRWeYnyd2TY6FTCsQk+9Bc4/FLrbF6@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	linux-acpi <linux-acpi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: ACPI vs. ISA IRQs
Date: Wed, 05 Nov 2003 00:03:08 +0000	[thread overview]
Message-ID: <3FA83E3C.6070907@superbug.demon.co.uk> (raw)
In-Reply-To: <1067981294.6057.20.camel-D2Zvc0uNKG8@public.gmane.org>

Len Brown wrote:
> Assumption: sharing interrupts is bad.
> 
> Plan:
> ACPI should attempt to distribute interrupts across
> the available IRQs.
> 
> This mostly applies to PIC mode, where PCI
> IRQ Link Devices are available to route PCI
> interrupts to open IRQs on the PIC.
> (In IO-APIC mode, we generally get no choice
>  which IO-APIC pins devices are attached to)
> 
> We have acpi_irq_penalty[] (disabled at the moment)
> in pci_link.c hard-coded to tell ACPI to avoid some IRQs
> that are commonly used by ISA devices.
> 
> But if,say, a sound-blaster card requests exclusive access
> to an IRQ that we didn't happen to reserve, and we happened
> to set a PCI link device to that IRQ, then sound doesn't
> work.
> 
> How to fix?
> 
> We can manually reserve IRQs to over-ride acpi_irq_penalty[],
> say "acpi_irq_used=5,10" to tell ACPI not to use IRQs that
> it thought by default were available.
> 
> Conversely, we could us, say, "acpi_irq_free=3,15" to tell
> ACPI that some IRQs it assumed were reserved for ISA are
> actually available for PCI.
> 
> I don't know of an automatic way to handle this.
> Seems that the ISA devices use Plug-and-Play methods
> to request IRQs, but there is no mechanism for such
> an event to boot a PIRQ off an IRQ if ACPI has put it there.
> Also, if such a mechanism existed, it wouldn't work
> if PNP were not available to ask for an IRQ.
> 
> thoughts?
> 
> thanks,
> -Len
> 
> ref:
> http://bugzilla.kernel.org/show_bug.cgi?id=430
> http://bugzilla.kernel.org/show_bug.cgi?id=1139
> http://bugzilla.kernel.org/show_bug.cgi?id=1391
> 
> 
This explains IRQs a bit: -
http://www.microsoft.com/whdc/hwdev/platform/proc/IO-APIC.mspx




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

  parent reply	other threads:[~2003-11-05  0:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-04 21:28 ACPI vs. ISA IRQs Len Brown
     [not found] ` <1067981294.6057.20.camel-D2Zvc0uNKG8@public.gmane.org>
2003-11-05  0:03   ` James Courtier-Dutton [this message]
2003-11-06  8:49   ` Yury V. Umanets
  -- strict thread matches above, loose matches on Subject: below --
2003-11-04 23:28 Grover, Andrew

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=3FA83E3C.6070907@superbug.demon.co.uk \
    --to=james-l7zrweynyd2ty6ftcsqk+9bc4/flrbf6@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=linux-acpi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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