public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: Peter Korsgaard <peter@korsgaard.com>,
	Michal Simek <michal.simek@xilinx.com>
Cc: linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	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: [PATCH] tty: serial: uartlite: Specify time for sending chars
Date: Mon, 05 May 2014 20:24:42 +0200	[thread overview]
Message-ID: <5367D76A.2040206@monstr.eu> (raw)
In-Reply-To: <874n14i7yn.fsf@dell.be.48ers.dk>

[-- Attachment #1: Type: text/plain, Size: 1871 bytes --]

On 05/05/2014 05:03 PM, Peter Korsgaard wrote:
>>>>>> "Michal" == Michal Simek <michal.simek@xilinx.com> writes:
> 
>  > Xilinx MDM (Microblaze Debug Module) also contains
>  > uart interface via JTAG which is compatible with
>  > uartlite driver. This interface is really slow
>  > that's why timeout is setup to 1s.
> 
>  > Make this time delay not to be cpu speed dependent.
> 
>  > Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>  > ---
> 
>  > RFC sent here:
>  > https://lkml.org/lkml/2013/9/30/250
>  > I finally got HW design which is just slow to be able
>  > to test it.
> 
>  > ---
>  >  drivers/tty/serial/uartlite.c | 10 ++++++++--
>  >  1 file changed, 8 insertions(+), 2 deletions(-)
> 
>  > diff --git a/drivers/tty/serial/uartlite.c b/drivers/tty/serial/uartlite.c
>  > index 5f90ef24d475..723a6b79cd14 100644
>  > --- a/drivers/tty/serial/uartlite.c
>  > +++ b/drivers/tty/serial/uartlite.c
>  > @@ -418,14 +418,20 @@ static struct uart_ops ulite_ops = {
>  >  #ifdef CONFIG_SERIAL_UARTLITE_CONSOLE
>  >  static void ulite_console_wait_tx(struct uart_port *port)
>  >  {
>  > -	int i;
>  >  	u8 val;
>  > +	unsigned long timeout;
> 
>  >  	/* Spin waiting for TX fifo to have space available */
>  > -	for (i = 0; i < 100000; i++) {
> 
> It would be good to add a note about the slow jtag variant here.

What exactly you would like to see here?
Just that this 1s is here because of mdm uart.

You can find out commit ID via git blame and description
is in commit message.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2014-05-05 18:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 14:48 [PATCH] tty: serial: uartlite: Specify time for sending chars Michal Simek
2014-05-05 15:03 ` Peter Korsgaard
2014-05-05 18:24   ` Michal Simek [this message]
2014-05-05 19:42     ` Peter Korsgaard
2014-05-06  4:48       ` 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=5367D76A.2040206@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=arnd@arndb.de \
    --cc=grant.likely@secretlab.ca \
    --cc=gregkh@linuxfoundation.org \
    --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=peter@korsgaard.com \
    --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