From: Chris Budd <budorola@gmail.com>
To: Chris Budd <budorola@gmail.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: 2.4.21: Sharing interrupts with serial console
Date: Thu, 4 Aug 2005 07:29:06 -0700 [thread overview]
Message-ID: <92fc8b8105080407297d8ced80@mail.gmail.com> (raw)
In-Reply-To: <20050804085440.A22910@flint.arm.linux.org.uk>
On 8/4/05, Russell King <rmk+lkml@arm.linux.org.uk> wrote:
> On Wed, Aug 03, 2005 at 06:36:51PM -0700, Chris Budd wrote:
> > 1. The rs_init function in ./linux-2.4.21/drivers/char/serial.c
> > explicitly states "The interrupt of the serial console port can't be
> > shared." Does this include *ALL* interrupts? The code checks for
> > sharing only with other serial devices, not *ALL* types of devices
> > like I2C, RTC, etc.
<snip>
> > 2. While the presence of the comment about not sharing was nice, it
> > does not explain "why?"
>
> Connecting a level-active interrupt output to an edge-triggered
> interrupt controller input is Bad News(tm) for missing interrupts.
>
Of course. I thought it was something more serious in the bowels of
the kernel. All the comment needed was just that one adjective "The
*edge-triggered* interrupt of the serial console port can't be
shared." I know many programmers do not like to write comments, but
good comments make the code more robust and stable: the code clearly
shows *what* you did, but comments are necessary to indicate *why*.
<snip>
> If your Intel hardware doesn't have level triggered input capabilities,
> please apply customer pressure to Intel to ensure that they consider it
> for their future ARM-based designs.
You will be happy to know that the Intel IOP80321 has level-sensitive
interrupts.
Thank you for the detailed explanation.
Chris.
next prev parent reply other threads:[~2005-08-04 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 1:36 2.4.21: Sharing interrupts with serial console Chris Budd
2005-08-04 7:54 ` Russell King
2005-08-04 14:29 ` Chris Budd [this message]
2005-08-04 11:16 ` linux-os (Dick Johnson)
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=92fc8b8105080407297d8ced80@mail.gmail.com \
--to=budorola@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox