From: Michal Simek <monstr@monstr.eu>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: Grant Likely <grant.likely@secretlab.ca>, linux-serial@vger.kernel.org
Subject: Re: Uartlite - ulite_transmit
Date: Thu, 06 Jan 2011 10:10:53 +0100 [thread overview]
Message-ID: <4D25871D.2000408@monstr.eu> (raw)
In-Reply-To: <87r5cqh0bn.fsf@macbook.be.48ers.dk>
Peter Korsgaard wrote:
>>>>>> "Michal" == Michal Simek <monstr@monstr.eu> writes:
>
> Hi,
>
> >> That would make us spin in the interrupt for potentially quite a
> >> while, E.G. until all data is transferred to the TX fifo.
>
> Michal> yep. That's truth but shouldn't be a problem for standard
> Michal> systems. Maybe worth to count how many times is tx fifo full on
> Michal> standard systems.
>
> But I still don't understand why you would want to burn CPU spinning
> when you know the UART will be busy for a while. Leaving it alone until
> it generates the TX fifo empty interrupt seems more logical to me.
I didn't know when tx fifo was full and then empty interrupt is
generated. I have added some debug things to driver and I am going to
look into.
I just changed return value and I have got correct output and then I
sent this email to check if is correct or not.
>
> >> What kind of problem are you trying to fix in the first place? You
> >> should get an interrupt when the TX fifo empties, which fill completely
> >> fill up the fifo again and so on - That should work just fine even with
> >> a low baud rate.
>
> Michal> I am trying to solve the problem for xilinx mdm IP (compatible
> Michal> with uartlite) where there are some missing characters on
> Michal> serial console.
>
> Strange. It's been a few years since I worked with Xilinx stuff and
> never used microblaze, so I don't know anything about MDM.
It is console over jtag. Just different connection.
>
> Michal> Maybe there is something wrong in different place but there are
> Michal> definitely missing characters.
>
> Michal> Just for the record: I also have to extend for loop in
> Michal> ulite_console_wait_tx to get all chars for console.
>
> Yeah, that loop should probably be time based (and perhaps calculated
> from baud rate).
It is hard to say if you can find out any accurate number of loops which
is baud rate dependent.
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next prev parent reply other threads:[~2011-01-06 9:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D2465E0.2000707@monstr.eu>
2011-01-05 12:39 ` Uartlite - ulite_transmit Michal Simek
2011-01-06 7:56 ` Peter Korsgaard
2011-01-06 8:29 ` Michal Simek
2011-01-06 9:02 ` Peter Korsgaard
2011-01-06 9:10 ` Michal Simek [this message]
2011-01-06 9:49 ` Peter Korsgaard
2011-01-07 7:48 ` Michal Simek
2011-01-07 9:06 ` Michal Simek
[not found] ` <4D2D78F3.2040903@monstr.eu>
[not found] ` <87aaj6zays.fsf@macbook.be.48ers.dk>
[not found] ` <4D2D8113.1020504@monstr.eu>
[not found] ` <8739oyza2n.fsf@macbook.be.48ers.dk>
2011-01-16 9:08 ` Michal Simek
2011-01-16 9:08 ` Michal Simek
2011-01-16 21:02 ` Peter Korsgaard
2011-01-17 6:35 ` Michal Simek
2011-01-17 15:17 ` Michal Simek
2011-01-19 15:27 ` Peter Korsgaard
2011-01-20 8:04 ` Michal Simek
2011-01-20 8:06 ` Peter Korsgaard
2011-01-20 8:08 ` Michal Simek
2011-01-12 9:40 ` Peter Korsgaard
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=4D25871D.2000408@monstr.eu \
--to=monstr@monstr.eu \
--cc=grant.likely@secretlab.ca \
--cc=jacmet@sunsite.dk \
--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 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.