linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] qe: add function qe_clock_source
Date: Tue, 9 Oct 2007 14:15:45 -0500	[thread overview]
Message-ID: <B2FD32B4-241E-4FCF-A18D-1E619034EC3A@kernel.crashing.org> (raw)
In-Reply-To: <470BC5CA.1010105@freescale.com>


On Oct 9, 2007, at 1:17 PM, Timur Tabi wrote:

> Kumar Gala wrote:
>
>> But that's a function of linux' use.  Remember decouple the device  
>> tree from how linux does things.
>
> Ok, I just understand what your point is.  I'm proposing that we  
> just put the name of the clock source in the device tree, and have  
> a function which converts that into an internal representation.   
> The clock is called "BRG3". It's not called BRG, #3 or something  
> like that.  Same thing with the CLK sources.

Ok.  I guess I'm not in favor of changing the device tree to address  
this issue.  I think it would be solved if "dtc" had #define support.

- k

  reply	other threads:[~2007-10-09 19:15 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
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 [this message]
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=B2FD32B4-241E-4FCF-A18D-1E619034EC3A@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@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).