From: Thomas Koeller <thomas.koeller@baslerweb.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH] 8250 driver interrupt sharing
Date: Thu, 28 Oct 2004 13:17:41 +0200 [thread overview]
Message-ID: <200410281317.41817.thomas.koeller@baslerweb.com> (raw)
In-Reply-To: <20041028120026.B3327@flint.arm.linux.org.uk>
On Thursday 28 October 2004 13:00, Russell King wrote:
> On Thu, Oct 28, 2004 at 01:01:58PM +0200, Thomas Koeller wrote:
> > here is a little patch that causes the driver to no longer pretend having
> > handled an interrupt if none of the ports actually interrupted. I am
> > currently doing a port to a platform where I want (actually, have) to
> > share a single interrupt between serial ports and other devices. The
> > patch is against kernel version 2.6.9.
>
> You can only share serial port interrupts with other devices if the
> interrupt controller input is level sensitive rather than edge
> sensitive. If it is edge sensitive, then you'll run into problems.
On my target platform, interrupts are indeed level sensitive, so this
should not be a problem (for me).
Does this problem somehow invalidate my patch? Even if interrupts were
edge sensitive, returning IRQ_NONE should ok, or not?
tk
--
--------------------------------------------------
Thomas Koeller, Software Development
Basler Vision Technologies
thomas dot koeller at baslerweb dot com
http://www.baslerweb.com
==============================
next prev parent reply other threads:[~2004-10-28 11:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 11:01 [PATCH] 8250 driver interrupt sharing Thomas Koeller
2004-10-28 11:00 ` Russell King
2004-10-28 11:17 ` Thomas Koeller [this message]
2004-10-28 11:18 ` Russell King
2004-11-01 12:10 ` Russell King
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=200410281317.41817.thomas.koeller@baslerweb.com \
--to=thomas.koeller@baslerweb.com \
--cc=linux-serial@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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.