From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Michal Simek <michal.simek@xilinx.com>
Cc: linux-kernel@vger.kernel.org, Michal Simek <monstr@monstr.eu>,
linux-serial@vger.kernel.org, arnd@arndb.de,
Peter Korsgaard <jacmet@sunsite.dk>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
Jiri Slaby <jslaby@suse.cz>
Subject: Re: [RFC PATCH] tty: serial: uartlite: Extend time for sending chars through mdm IP
Date: Mon, 30 Sep 2013 05:54:33 -0700 [thread overview]
Message-ID: <20130930125433.GC13654@kroah.com> (raw)
In-Reply-To: <fec1c418d7d8933a9729ea1926c76e404f8c3020.1380541829.git.michal.simek@xilinx.com>
On Mon, Sep 30, 2013 at 01:50:35PM +0200, Michal Simek wrote:
> From: Michal Simek <monstr@monstr.eu>
>
> Serial over jtag via mdm is compatible with uartlite driver
> just need to extend time for reading chars because connection
> is slow.
>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> ---
> drivers/tty/serial/uartlite.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/tty/serial/uartlite.c b/drivers/tty/serial/uartlite.c
> index 5f90ef2..f55c342 100644
> --- a/drivers/tty/serial/uartlite.c
> +++ b/drivers/tty/serial/uartlite.c
> @@ -422,7 +422,7 @@ static void ulite_console_wait_tx(struct uart_port *port)
> u8 val;
>
> /* Spin waiting for TX fifo to have space available */
> - for (i = 0; i < 100000; i++) {
> + for (i = 0; i < 10000000; i++) {
> val = uart_in32(ULITE_STATUS, port);
> if ((val & ULITE_STATUS_TXFULL) == 0)
> break;
Ick, what happens next year when we get a faster cpu?
Please make this a time delay, not a 'loop till we can count to this
number', so we know exactly what is going on here.
thanks,
greg k-h
next prev parent reply other threads:[~2013-09-30 12:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 11:50 [RFC PATCH] tty: serial: uartlite: Extend time for sending chars through mdm IP Michal Simek
2013-09-30 12:54 ` Greg Kroah-Hartman [this message]
2013-09-30 14:28 ` 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=20130930125433.GC13654@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=grant.likely@secretlab.ca \
--cc=jacmet@sunsite.dk \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=rob.herring@calxeda.com \
/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