All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Ben Dooks <ben-linux-arm@fluff.org>
Cc: Linux Arm Mailing List <linux-arm-kernel@lists.arm.linux.org.uk>,
	linux-serial@vger.kernel.org
Subject: Re: [PATCH] s3c2412 serial : more accurate baudrate generation
Date: Fri, 04 Jan 2008 09:34:48 +0100	[thread overview]
Message-ID: <477DEFA8.2020703@parrot.com> (raw)
In-Reply-To: <20080103224911.GC29922@trinity.fluff.org>

Hi,

Ben Dooks wrote:
> On Thu, Jan 03, 2008 at 04:39:16PM +0100, Matthieu CASTET wrote:
> 
>> use UDIVSLOT register on 2412, to get better accuracy when computing the
>> baudrate.
> 
> Personally, I think the following would have been better:
> 
> Improve the accuracy of baud rate generation on the S3C2412 by using the
> UDIVSLOT register to acheive better division if the clock does not directly
> divide down to the required baud rate.
>  
That's sound better.
Thanks for the re-writing.
>> The clock generation is divised on 16 slots.
>> UDIVSLOT : if the bit n is set to 1, then for the slot n the clock generator 
>> divide clock source by (UBRDIV + 2) instead of (UBRDIV + 1).
>>
>> So if m is the number of bit set to one, the baudrate is
>> CLOCK / (m*(UBRDIV + 2) + (16-m)*(UBRDIV + 1))
>> CLOCK / (16*(UBRDIV + 1) + m)
>>
>> See 2412 datasheet for more info.
> 
> I think this could do with re-writing too, but I'll leave that till tommorow.
> 
> My only other question is has this been tested on an non S3C2412 CPUs?
>  
No, I only test it on 2412.

Thanks,

Matthieu

      reply	other threads:[~2008-01-04  8:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-03 15:39 [PATCH] s3c2412 serial : more accurate baudrate generation Matthieu CASTET
2008-01-03 22:49 ` Ben Dooks
2008-01-04  8:34   ` Matthieu CASTET [this message]

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=477DEFA8.2020703@parrot.com \
    --to=matthieu.castet@parrot.com \
    --cc=ben-linux-arm@fluff.org \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.