From: Haavard Skinnemoen <hskinnemoen@atmel.com>
To: "Remy Bohmer" <linux@bohmer.net>
Cc: "Andrew Victor" <linux@maxim.org.za>,
"ARM Linux Mailing List"
<linux-arm-kernel@lists.arm.linux.org.uk>,
"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] atmel_serial: Split the interrupt handler
Date: Tue, 18 Dec 2007 18:19:21 +0100 [thread overview]
Message-ID: <20071218181921.2478baa9@dhcp-252-066.norway.atmel.com> (raw)
In-Reply-To: <3efb10970712180723x2cd22c5ei6b342f0ab7cc39c2@mail.gmail.com>
Crud...my mailer helpfully filtered this into the huge linux-kernel
bin instead of leaving it in my inbox...
On Tue, 18 Dec 2007 16:23:11 +0100
"Remy Bohmer" <linux@bohmer.net> wrote:
> Hello Haavard,
>
> A few remarks:
>
> > From: Remy Bohmer <hskinnemoen@atmel.com>
>
> My name, at your address ;-)))
Right. Wonder how that happened...I'll try to fix it manually before I
send the next patchbomb.
> > This patch splits up the interrupt handler of the serial port
> > into a interrupt top-half and a tasklet.
>
> I see you moved the handling of the sysrq-key to the tasklet. This was
> actually a very nice feature in the IRQ-top half on preempt-RT. This
> helps debugging running away RT-processes.
Ah. Good point. I guess we should move it back, then.
> > In this version of the patch, we try to only do things that are
> > absolutely necessary in the interrupt handler, storing away the
> > status register along with the received character and letting the
> > tasklet handle break, sysrq, error flags, etc.
>
> Preempt-RT now absolutely requires my (4th) IRQ_NODELAY patch, because
> the spinlock now is always inside the code, and not only in
> theexception path, and thus without my NO_DELAY patch we have a panic
> during boot.
> On preempt-RT this spinlock must be a raw-spinlock. (If this type is
> known in the mainline kernel, you can apply that patch it anyway)
I'll see if that works.
> BTW: Attached I have added a 2nd patch that I use for Preempt-RT. (For
> cleaner startup, and to get rid of useless IRQ-threads.
Hrm. That assumption isn't valid on AVR32...on AP7000, for example,
IRQ1 is used by the LCD controller.
> > This patch should apply on top of the cleanup patch I sent earlier
>
> For the cleanup patch:
> Acked-by: Remy Bohmer <linux@bohmer.net>
>
> > today. Or at least I think so...I'll send the full series once
> > everyone are happy.
>
> So, for this patch: I am almost happy ;-)
Great :-)
Haavard
next prev parent reply other threads:[~2007-12-18 17:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 14:14 Haavard Skinnemoen
2007-12-18 15:23 ` Remy Bohmer
2007-12-18 17:19 ` Haavard Skinnemoen [this message]
2007-12-18 19:18 ` Remy Bohmer
2007-12-19 12:34 ` Haavard Skinnemoen
2007-12-19 12:50 ` Remy Bohmer
2007-12-19 13:11 ` Haavard Skinnemoen
2007-12-19 13:18 ` Remy Bohmer
2007-12-19 13:24 ` Haavard Skinnemoen
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=20071218181921.2478baa9@dhcp-252-066.norway.atmel.com \
--to=hskinnemoen@atmel.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@bohmer.net \
--cc=linux@maxim.org.za \
/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
all inboxes | Powered by JetHome®