From: Timur Tabi <timur@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] qe: add function qe_clock_source
Date: Tue, 09 Oct 2007 11:43:20 -0500 [thread overview]
Message-ID: <470BAFA8.1060408@freescale.com> (raw)
In-Reply-To: <8D4AA8EB-812F-4E58-A13C-CE3BA72037F3@kernel.crashing.org>
Kumar Gala wrote:
> Ok, I went and looked at how rx-clock & tx-clock are spec'd in
> booting-without-of.txt
>
> Why dont we fix this so we have a property that says "BRG" or "CLK" and
> another that has ID = [1.16] for BRG and [1..24] for CLK.
Because sometimes you can use both BRGs and CLKs. Some operations can be done
only on one or the other, and some can be done on both. The enum itself is
fine, I think. I'd rather not split up the two, just report an error if you
specify a clock source that's not support for that particular purpose.
UART, for instance, can use a CLK signal, but I wrote the driver to only
support BRGs because there are plenty of them and it's a lot simpler. But
someone, for instance, could wire up his board to want to use external clocks
for some UARTs, and so he'd need to modify the driver.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-10-09 16:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 15:53 [PATCH] qe: add function qe_clock_source Timur Tabi
2007-10-09 15:56 ` Kumar Gala
2007-10-09 16:01 ` Timur Tabi
2007-10-09 16:18 ` Kumar Gala
2007-10-09 16:21 ` Timur Tabi
2007-10-09 16:38 ` Kumar Gala
2007-10-09 16:43 ` Timur Tabi [this message]
2007-10-09 16:47 ` Scott Wood
2007-10-09 16:48 ` Timur Tabi
2007-10-09 18:10 ` Kumar Gala
2007-10-09 18:12 ` Timur Tabi
2007-10-09 18:15 ` Kumar Gala
2007-10-09 18:17 ` Timur Tabi
2007-10-09 19:15 ` Kumar Gala
2007-10-09 19:18 ` Timur Tabi
2007-10-09 19:50 ` Kumar Gala
2007-10-09 16:46 ` Scott Wood
2007-10-09 16:47 ` Timur Tabi
2007-10-09 16:48 ` Scott Wood
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=470BAFA8.1060408@freescale.com \
--to=timur@freescale.com \
--cc=galak@kernel.crashing.org \
--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).