public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alexey Pelykh <alexey.pelykh@gmail.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: Fwd: [PULL REQUEST] Tweak to support 1Mbaud and similar baudrates that require Mode16 instead of Mode13
Date: Tue, 27 Nov 2012 16:42:04 -0800	[thread overview]
Message-ID: <20121128004204.GB3857@kroah.com> (raw)
In-Reply-To: <CAOmKuSrQW1j_tmQNbXMO-GUH7zrUR0WR3K4rJNok=2LZmRKVYg@mail.gmail.com>

On Tue, Nov 27, 2012 at 11:56:06PM +0200, Alexey Pelykh wrote:
> Hello everyone,
> 
> Original table in OMAP TRM named "UART Mode Baud Rates, Divisor
> Values, and Error Rates" determines modes not for all common baud
> rates. E.g. for 1000000 baud rate mode should be 16x, but according to
> that table it's determined as 13x. According to current implementation
> of mode
> divisor selection, after requesting 1000000 baudrate from driver,
> later one will configure chip to use MODE13 divisor. Assuming 48Mhz as
> common UART clock speed, MODE13 divisor will effectively give 1230769
> baudrate, what is quite far from desired 1000000 baudrate. While with
> MODE16 divisor, chip will produce exact 1000000 baudrate.
> 
> In old driver that served UART devices (8250.c and serial_core.c) this
> divisor could have been configured by user-space program, but in
> omap_serial.c driver implementation this ability was not implemented
> (afaik, by design) thus disallowing proper usage of MODE16-compatible
> baudrates.
> 
> Best regards,
> Alexey Pelykh
> 
> The following changes since commit 77b67063bb6bce6d475e910d3b886a606d0d91f7:
> 
>   Linux 3.7-rc5 (2012-11-11 13:44:33 +0100)
> 
> are available in the git repository at:
> 
>   git://github.com/alexey-pelykh/linux.git omap_serial_mode_fix
> 
> for you to fetch changes up to cf827bb4057fdcdaeac20b95b01c29c068109185:
> 
>   Tweak to support 1Mbaud and similar baudrates that require Mode16
> instead of Mode13 (2012-11-12 19:29:27 +0200)

Sorry, I can't take a git pull request for a single patch, please just
send it in an email (the patch that is), with the correct signed-off-by:
information, as described in Documentation/SubmittingPatches, and I will
be glad to queue it up.

thanks,

greg k-h

  parent reply	other threads:[~2012-11-28  0:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOmKuSpRJhBibSDxTFCH157-XokhaFhvQ-gYxKZe+PfzokaBoA@mail.gmail.com>
2012-11-27 21:35 ` Fwd: [PULL REQUEST] Tweak to support 1Mbaud and similar baudrates that require Mode16 instead of Mode13 Alexey Pelykh
2012-11-27 21:46   ` Alan Cox
2012-11-27 21:56   ` Fwd: " Alexey Pelykh
2012-11-27 23:00     ` Alan Cox
2012-11-28  0:42     ` Greg KH [this message]
2012-11-28  9:05       ` Fwd: " Alexey Pelykh
2012-11-28 17:25         ` Greg KH
     [not found]           ` <CAOmKuSq52wWgetb53S1HiMNghT_A3UukPaUO0E9dXtWor+GVvw@mail.gmail.com>
2012-11-28 17:32             ` Greg KH

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=20121128004204.GB3857@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexey.pelykh@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox