From: michael <trimarchi@gandalf.sssup.it>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: Remy Bohmer <linux@bohmer.net>,
fabio@gandalf.sssup.it, Andrew Victor <linux@maxim.org.za>,
Chip Coldwell <coldwell@redhat.com>,
Marc Pignat <marc.pignat@hevs.ch>,
David Brownell <david-b@pacbell.net>,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH -mm v4 6/9] atmel_serial: Split the interrupt handler
Date: Thu, 31 Jan 2008 02:53:50 +0100 [thread overview]
Message-ID: <47A12A2E.5040309@gandalf.sssup.it> (raw)
In-Reply-To: <20080130164631.7de4f6bd@dhcp-252-066.norway.atmel.com>
Hi,
Haavard Skinnemoen wrote:
> On Wed, 30 Jan 2008 16:26:27 +0100
> michael <trimarchi@gandalf.sssup.it> wrote:
>
>
>>> I have no idea. Could you post some more specifics about what you
>>> modified, for example a diff?
>>>
>>>
>>>
>> ...
>> /* The interrupt handler does not take the lock */
>> spin_lock_irqsave(&port->lock, flags);
>> atmel_tx_chars(port);
>> spin_unlock_irqrestore(&port->lock, flags);
>>
>
> Sorry, this isn't going to work.
>
> Please post a diff with the changes you did to the driver, and whatever
> output you got when it crashed.
>
> It's really difficult to help you when I don't know (a) what code
> you're actually running, or (b) anything about the crash.
>
>
Ok, but the problem is that I have some added code for using the uart with
smart card in iso mode, (is never called) and the patch is not so clean.
Now I return to the original patch without the spin_lock_irqsave and with
the fix of buffer allocation,and I don't see the crash anymore.
In full preemptive all works with threading hardirqs and sofirqs. I will
do other testing before posting again.
>> The atmel_tx_chars using the serial device registers like the interrupt
>> routine
>> and so I think that it is possible to have interference during send
>> operation.
>>
>
> No, it's only called from the tasklet, and the interrupt handler doesn't
> touch the TX data register. There shouldn't be any need to disable
> interrupts around the call to atmel_tx_chars(). In fact, this may very
> well be the cause of the overruns you're seeing.
>
> Haavard
>
>
The overrun still remain. An lrz receive session is impossible using
full preemption. I will try the dma patch too and test in iso mode for
smart card.
Thanks
next prev parent reply other threads:[~2008-01-31 1:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080129224316.GA23155@gandalf.sssup.it>
2008-01-29 23:12 ` michael
2008-01-30 9:41 ` Haavard Skinnemoen
2008-01-30 10:21 ` Remy Bohmer
2008-01-30 10:34 ` Haavard Skinnemoen
2008-01-30 11:05 ` Remy Bohmer
2008-01-30 12:43 ` Haavard Skinnemoen
2008-01-30 15:25 ` michael
2008-01-30 10:29 ` michael
2008-01-30 12:36 ` Haavard Skinnemoen
2008-01-30 15:26 ` michael
2008-01-30 15:46 ` Haavard Skinnemoen
2008-01-31 1:53 ` michael [this message]
2008-01-31 15:07 ` Haavard Skinnemoen
2008-01-31 19:36 ` Remy Bohmer
2008-02-04 12:39 ` Haavard Skinnemoen
2008-02-04 19:44 ` Remy Bohmer
2008-02-06 12:19 ` michael
2008-02-06 19:41 ` Remy Bohmer
2008-02-13 11:07 ` michael
2008-02-13 20:13 ` Remy Bohmer
2008-02-14 7:30 ` michael
2008-02-04 19:01 ` michael
2008-02-04 20:25 ` Haavard Skinnemoen
2008-02-05 12:29 ` michael
2008-02-06 12:30 ` Haavard Skinnemoen
2008-02-06 13:41 ` michael
2008-02-06 15:22 ` Haavard Skinnemoen
2008-01-24 12:41 [PATCH -mm v4 0/9] atmel_serial cleanups and improvements Haavard Skinnemoen
2008-01-24 12:41 ` [PATCH -mm v4 1/9] MAINTAINERS: Add myself as maintainer of the atmel_serial driver Haavard Skinnemoen
2008-01-24 12:41 ` [PATCH -mm v4 2/9] atmel_serial: Clean up the code Haavard Skinnemoen
2008-01-24 12:41 ` [PATCH -mm v4 3/9] atmel_serial: Use cpu_relax() when busy-waiting Haavard Skinnemoen
2008-01-24 12:41 ` [PATCH -mm v4 4/9] atmel_serial: Use existing console options only if BRG is running Haavard Skinnemoen
2008-01-24 12:41 ` [PATCH -mm v4 5/9] atmel_serial: Fix bugs in probe() error path and remove() Haavard Skinnemoen
2008-01-24 12:41 ` [PATCH -mm v4 6/9] atmel_serial: Split the interrupt handler 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=47A12A2E.5040309@gandalf.sssup.it \
--to=trimarchi@gandalf.sssup.it \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=coldwell@redhat.com \
--cc=david-b@pacbell.net \
--cc=fabio@gandalf.sssup.it \
--cc=hskinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@bohmer.net \
--cc=linux@maxim.org.za \
--cc=marc.pignat@hevs.ch \
/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®