public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew de Quincey <adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
To: "Grover,
	Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Rob North <tzwvgwv2001-O/bDAPVd7B0N+BqQ9rBEUg@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: ACPI ignoring IRQ flags in PRT
Date: Mon, 14 Jul 2003 09:51:18 +0100	[thread overview]
Message-ID: <200307140951.18569.adq_dvb@lidskialf.net> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A8470255EE87-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>


> Great to see someone's digging into this. BTW have you looked at the
> ACPI 2.0 spec section 6.2.8? It talks about the contents of _PRT.
> Basically, it can contain either the interrupt number itself OR point to
> a link device, which in turn lets ACPI read (via _CRS) write (via _SRS)
> and see the possiblities (_BRS) for controlling the interrupt routing
> for that device.
>
> The code *should* be handling both these cases, but obviously there are
> still some bugs lurking.

I think its handling both cases OK, its just that it was ignoring the polarity 
and mode settings for link device IRQs.

What I was wondering was if/where these settings were for global IRQs... i.e. 
when the _PRT contains the actual interrupt number, what settings should be 
used.

I suppose since its the PCI routing table, it might just expect you to default 
to PCI settings, but as I found link-device IRQs specified in the PRT don't 
necessary follow the PCI standard... problem is, my board doesn't specify 'em 
in this way.



-------------------------------------------------------
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-14  8:51 UTC|newest]

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

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=200307140951.18569.adq_dvb@lidskialf.net \
    --to=adq_dvb-fmpxvn3awwjajazl26g0sa@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=tzwvgwv2001-O/bDAPVd7B0N+BqQ9rBEUg@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