From: johnlinn@comcast.net
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
michal simek <michal.simek@petalogix.com>,
joe@perches.com, grant likely <grant.likely@secretlab.ca>,
greg@kroah.com
Subject: Re: [PATCH V3] tty/serial: add support for Xilinx PS UART
Date: Wed, 27 Apr 2011 13:21:36 +0000 (UTC) [thread overview]
Message-ID: <126598808.1934339.1303910496698.JavaMail.root@sz0140a.emeryville.ca.mail.comcast.net> (raw)
In-Reply-To: <20110427103340.2554df83@lxorguk.ukuu.org.uk>
----- "Alan Cox" <alan@lxorguk.ukuu.org.uk> wrote:
> > I thought I was improving but now as I look at it further, that
> seems like it
> > was better and I should have stuck to that method.
> >
> > Thoughts?
>
> Go for nearest is the right behaviour. The whole tty layer works on
> that
> basis as do soem other things. It means you don't have to have a set
> of
> calls to do things like "enumerate valid data rates" instead you ask
> and
> compare.
I wasn't very clear on that, sorry about that.
I meant we were not detecting if the error was too much and finding the
nearest baud rate that had an acceptable amount of error.
We were just finding the best baud rate generator values for the baud and
then using them without any kind of error.
Thanks,
John
>
> > > > + uart_update_timeout(port, termios->c_cflag, baud);
> > >
> > > [which would also fix this timeout!]
> >
> > Maybe you were meaning that if the baud rate was not really set
> because of the
> > error this timeout would be wrong also, and if so that makes sense.
>
> Correct
>
> Alan
next prev parent reply other threads:[~2011-04-27 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <381805170.1906645.1303859011392.JavaMail.root@sz0140a.emeryville.ca.mail.comcast.net>
2011-04-26 23:15 ` johnlinn
2011-04-27 9:33 ` Alan Cox
2011-04-27 13:21 ` johnlinn [this message]
2011-04-27 14:15 ` Alan Cox
2011-04-22 19:13 John Linn
2011-04-26 19:58 ` Alan Cox
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=126598808.1934339.1303910496698.JavaMail.root@sz0140a.emeryville.ca.mail.comcast.net \
--to=johnlinn@comcast.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=grant.likely@secretlab.ca \
--cc=greg@kroah.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=michal.simek@petalogix.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
all inboxes | Powered by JetHome®