public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4] serial: uartlite: Support for SERIAL_MULTI
Date: Wed, 21 Sep 2011 14:21:35 +0200	[thread overview]
Message-ID: <4E79D6CF.3020804@monstr.eu> (raw)
In-Reply-To: <201109200933.33174.marek.vasut@gmail.com>

Marek Vasut wrote:
> On Tuesday, September 20, 2011 09:19:23 AM Michal Simek wrote:
>> Michal Simek wrote:
>>> Add support for SERIAL MULTI for uartlite.
>>>
>>> Signed-off-by: Michal Simek <monstr@monstr.eu>
>>>
>>> ---
>>> v2: Use in/out_be32 functions
>>>
>>> v3: Clean coding style
>>>
>>> v4: Simplify userial_ports array initialization
>>> ---
>>>
>>>  common/serial.c                   |   14 ++++
>>>  drivers/serial/serial_xuartlite.c |  134
>>>  ++++++++++++++++++++++++++++++++----- include/serial.h                 
>>>  |    7 ++
>>>  3 files changed, 137 insertions(+), 18 deletions(-)
>> Any comment?
> 
> Avoid endless loops

No problem to do it for putc but for getc?
What would you like to return if there is no character available?

If generic code always checked if there is any character available through tstc
and then call getc I can keep there just reading buffer but from my test I see that
it doesn't do that.

Please point me to any existing u-boot serial driver which does it in way you like.
I wasn't able to find it out.

Thanks,
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

  reply	other threads:[~2011-09-21 12:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-15 13:50 [U-Boot] [PATCH v4] serial: uartlite: Support for SERIAL_MULTI Michal Simek
2011-09-20  7:19 ` Michal Simek
2011-09-20  7:33   ` Marek Vasut
2011-09-21 12:21     ` Michal Simek [this message]
2011-09-21 14:15       ` Mike Frysinger
2011-09-20 17:03 ` Mike Frysinger
2011-09-21 11:31   ` Michal Simek

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=4E79D6CF.3020804@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=u-boot@lists.denx.de \
    /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