public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: Andrew de Quincey <adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI ignoring IRQ flags in PRT
Date: Sun, 13 Jul 2003 15:23:21 +0100	[thread overview]
Message-ID: <20030713142321.GC20424@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200307131452.39000.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>

On Sun, Jul 13, 2003 at 02:52:38PM +0100, Andrew de Quincey wrote:
> 
> Hi, from my understanding of the ACPI spec, each IRQ as specified in the _PRT 
> has additional flags associated with it (e.g. specifying the polarity, level 
> etc) that should be used for this IRQ. 
> 
> The Linux ACPI code seems to be ignoring these, and hardcodes them to the 
> values that cause problems for me. Is there a reason, or has that code just 
> not been written yet?

you can't mean the _PRT.  the _PRT describes PCI interrupts, and those
have their polarity and trigger specified by the PCI spec.  i suspect you
mean someting else, but i'm not sure what.  can't be the SCI interrupt
since that's defined to be level, low, sharable.

some of the ia64 acpi code pays attention to polarity and edge vs level.
now that we know this is an issue on x86, maybe some more people will be
interested in thinking about how to fix this properly.  here's what we
currently have on ia64:

int acpi_register_irq (u32 gsi, u32 polarity, u32 trigger);

-- 
"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 sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1

  parent reply	other threads:[~2003-07-13 14:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-13 13:52 ACPI ignoring IRQ flags in PRT Andrew de Quincey
     [not found] ` <200307131452.39000.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-13 14:23   ` Matthew Wilcox [this message]
     [not found]     ` <20030713142321.GC20424-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2003-07-13 16:45       ` Andrew de Quincey
     [not found]         ` <200307131745.42153.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-13 18:08           ` Rob North
2003-07-13 19:36             ` Andrew de Quincey
2003-07-13 19:49       ` Andrew de Quincey
  -- strict thread matches above, loose matches on Subject: below --
2003-07-14  0:56 Grover, Andrew
2003-07-14  8:51 ` Andrew de Quincey
     [not found]   ` <200307140951.18569.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-07-14 11:07     ` Rob North

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