public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Tim Hockin <thockin@hockin.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: APIC, changing level/edge interrupt
Date: Sat, 01 Jan 2005 16:56:15 +0100	[thread overview]
Message-ID: <41D6C81F.1090106@drzeus.cx> (raw)
In-Reply-To: <20050101054925.GA13925@hockin.org>

Tim Hockin wrote:

>On Tue, Dec 28, 2004 at 06:27:25PM +0100, Pierre Ossman wrote:
>  
>
>>How do you tell the APIC that a device uses level triggered interrupts, 
>>not edge triggered? I have a flash reader on the LPC bus which uses 
>>level triggered interrupts and /proc/interrupts show edge triggered. 
>>Some interrupts are missed by the APIC so I figured this might be why.
>>    
>>
>
>BIOS should set this up.  Maybe ACPI has a way to do this?
>  
>
Should doesn't always mean that it actually does ;)
But since BIOS can configure the APIC then the kernel should be able to 
also. A quick and dirty hack will suffice ATM since I just want to 
pinpoint where the problem is.
What is the default mode and what does the XT-PIC expect? (it works fine 
with the apic disabled).

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.

Rgds
Pierre


  reply	other threads:[~2005-01-01 15:56 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 [this message]
2005-01-01 20:24     ` Tim Hockin
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=41D6C81F.1090106@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thockin@hockin.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