From: Scott Wood <scottwood@freescale.com>
To: Laurent Pinchart <laurentp@cse-semaphore.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC] Using two baud rate generators with the cpm_uart driver
Date: Tue, 15 Apr 2008 10:59:39 -0500 [thread overview]
Message-ID: <4804D0EB.5020508@freescale.com> (raw)
In-Reply-To: <200804151754.21664.laurentp@cse-semaphore.com>
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.
-Scott
next prev parent reply other threads:[~2008-04-15 15:59 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 [this message]
2008-04-15 16:03 ` Laurent Pinchart
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=4804D0EB.5020508@freescale.com \
--to=scottwood@freescale.com \
--cc=laurentp@cse-semaphore.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).