linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Yoder Stuart-B08248" <stuart.yoder@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC] mpc5200 device tree bindings refinement
Date: Mon, 12 Feb 2007 14:55:03 -0700	[thread overview]
Message-ID: <528646bc0702121355k4879737eic63ab285f7213271@mail.gmail.com> (raw)
In-Reply-To: <9696D7A991D0824DBA8DFAC74A9C5FA3029428D5@az33exm25.fsl.freescale.net>

On 2/12/07, Yoder Stuart-B08248 <stuart.yoder@freescale.com> wrote:
> My suggestion would be to _not_ create a brand new property
> called system-frequency.  Could we not use the existing
> clock-frequency property instead (defined to mean the
> Fsystem frequency)?
>
> Currently across many device types (e.g. PCI, serial) the
> clock-frequency property is used to describe the clock
> frequency in a way specific to that device.  Could that work
> here?
>
> If you did need to create a new property unique to this
> particular device it should have the vendor name preprended
> to the property (e.g. linux,phandle).

Now that I think about it some more; Is a vendor name prefix really
warranted here?  I don't see any other examples of vendor prefix being
used for other SoC property values.  (linux,phandle is the notable
exception, but that's not an SoC thing).

I bring up this issue because it seems quite inconsistent.  Most of
the device nodes already uses custom properties w/o any vendor prefix.
 Why make this one the first with a prefix?  :-)

g.

-- 
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

      parent reply	other threads:[~2007-02-12 21:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09  7:30 [RFC] mpc5200 device tree bindings refinement Grant Likely
2007-02-09 17:31 ` Mark A. Greer
2007-02-09 17:50   ` Mark A. Greer
2007-02-09 18:38   ` Grant Likely
     [not found]     ` <9696D7A991D0824DBA8DFAC74A9C5FA3029428E1@az33exm25.fsl.freescale.net>
     [not found]       ` <20070212205731.GC2729@mag.az.mvista.com>
2007-02-13 15:37         ` Grant Likely
2007-02-13 21:41           ` Benjamin Herrenschmidt
2007-02-13 22:25             ` Mark A. Greer
2007-02-12 20:34 ` Yoder Stuart-B08248
2007-02-12 20:44   ` Grant Likely
2007-02-12 21:07     ` Yoder Stuart-B08248
2007-02-12 21:55   ` Grant Likely [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=528646bc0702121355k4879737eic63ab285f7213271@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=stuart.yoder@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).