linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC] Using two baud rate generators with the cpm_uart driver
Date: Tue, 15 Apr 2008 18:03:56 +0200	[thread overview]
Message-ID: <200804151803.56383.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <4804D0EB.5020508@freescale.com>

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

On Tuesday 15 April 2008 17:59, Scott Wood wrote:
> Laurent Pinchart wrote:
> >> The clean solution would be to have an abstracted clock API, similar to 
> >> phylib, where the caller doesn't know details about BRGs and such. 
> >> Maybe the linux/clk.h API would be suitable; I haven't looked at it in 
> >> detail.
> > 
> > The clock API would have to be quite advanced to express things like "the SCC4 
> > clock is a combination of BRG2 and BRG5" (and I don't even consider 
> > adding "with BRG2 set to 16x the baud rate and BRG5 to the baud rate").
> 
> What I was picturing was platform code providing a clock object that the 
> cpm_uart driver could be pointed at (possibly by modifying the device 
> tree in platform init); the knowledge of the multiple BRG weirdness 
> would be contained in platform code.

I'll think about it.

Thanks.

-- 
Laurent Pinchart
CSE Semaphore Belgium

Chaussee de Bruxelles, 732A
B-1410 Waterloo
Belgium

T +32 (2) 387 42 59
F +32 (2) 387 42 75

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2008-04-15 16:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-15 13:32 [RFC] Using two baud rate generators with the cpm_uart driver Laurent Pinchart
2008-04-15 15:34 ` Scott Wood
2008-04-15 15:54   ` Laurent Pinchart
2008-04-15 15:59     ` Scott Wood
2008-04-15 16:03       ` Laurent Pinchart [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=200804151803.56383.laurentp@cse-semaphore.com \
    --to=laurentp@cse-semaphore.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).