public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: Matthew Wilcox <willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	linux-ia64-WygotPe7DYIabbyE177sbg@public.gmane.org
Subject: Re: acpi_irq_to_vector()
Date: Wed, 11 Jun 2003 19:27:26 +0100	[thread overview]
Message-ID: <20030611182726.GH28581@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030605192253.GS28581-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>

On Thu, Jun 05, 2003 at 08:22:53PM +0100, Matthew Wilcox wrote:
> ok, we renamed gsi_to_vector to acpi_irq_to_vector(); that's fine.
> But we still have that ugly ifdef in there.  Any resistance to defining
> acpi_irq_to_vector to simply return its value on non-ia64 platforms?
> 
> Then it'd look like:
> 
> 	irq = acpi_fadt.sci_int;
> 	vector = acpi_irq_to_vector(irq);
> 	if (vector < 0) {
> 		printk(KERN_ERR PREFIX "SCI (IRQ%d) not registered\n", irq);
> 		return AE_OK;
> 	}
> 	acpi_irq_irq = vector;
> 	acpi_irq_handler = handler;
> 	acpi_irq_context = context;
> 	if (request_irq(vector, acpi_irq, SA_SHIRQ, "acpi", acpi_irq)) {

Since nobody's arguing with me, I'm going to argue with myself ;-)

For PCI devices, we just read the irq out of the struct pci_dev.
The platform code gets the opportunity to mangle the irq in whatever
way it chooses before the pci_dev is passed to the driver.  Can we do
something similar for ACPI instead?

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk


-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5

      parent reply	other threads:[~2003-06-11 18:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05 19:22 acpi_irq_to_vector() Matthew Wilcox
     [not found] ` <20030605192253.GS28581-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2003-06-11 18:27   ` Matthew Wilcox [this message]

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=20030611182726.GH28581@parcelfarce.linux.theplanet.co.uk \
    --to=willy-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-ia64-WygotPe7DYIabbyE177sbg@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