All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Hockin <thockin@hockin.org>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: APIC, changing level/edge interrupt
Date: Sat, 1 Jan 2005 12:24:50 -0800	[thread overview]
Message-ID: <20050101202450.GA19360@hockin.org> (raw)
In-Reply-To: <41D6C81F.1090106@drzeus.cx>

On Sat, Jan 01, 2005 at 04:56:15PM +0100, Pierre Ossman wrote:
> >BIOS should set this up.  Maybe ACPI has a way to do this?

> Should doesn't always mean that it actually does ;)

Of course.  My point was that if it does not, it's a bug in the BIOS.  

> But since BIOS can configure the APIC then the kernel should be able to 

Of course, but the kernel has no way to know whether a device should be
edge or level triggered unless you have a driver for that device.  And
even if you do, I don't know that there is an API in kernel to say
set_irq_mode(IRQ_EDGE) (though there could be).

> What is the default mode and what does the XT-PIC expect? (it works fine 
> with the apic disabled).

I think default is PIC-compatible which is edge by default.  I think.  I
don;t have the book here.

> ACPI might have some functions to configure the APIC correctly but right 
> now the connection between ACPI and drivers is rather weak (non-existant 
> for this driver) so that's not really a viable solution when testing. 
> Might be a good long term solution though.

I know ACPI can get the information with the _PRS and _CRS methods.  The
OSPM core should probably be re-programming the (A)PIC appropriately.  Of
course, that depends on the BIOS vendor getting the ACPI correct, too.

  reply	other threads:[~2005-01-01 20:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-28 17:27 APIC, changing level/edge interrupt Pierre Ossman
2005-01-01  5:49 ` Tim Hockin
2005-01-01 15:56   ` Pierre Ossman
2005-01-01 20:24     ` Tim Hockin [this message]
2005-01-01 21:22       ` Pierre Ossman

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=20050101202450.GA19360@hockin.org \
    --to=thockin@hockin.org \
    --cc=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.