From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Shawn Guo <shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linaro-dev-cunTk1MwBs8s++Sfvej+rw@public.gmane.org,
patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH 2/3] arm/dt: add very basic dts file for babbage board
Date: Mon, 28 Feb 2011 11:09:17 -0700 [thread overview]
Message-ID: <20110228180917.GG13690@angua.secretlab.ca> (raw)
In-Reply-To: <20110228143159.GA3688-+NayF8gZjK2ctlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
On Mon, Feb 28, 2011 at 10:32:01PM +0800, Shawn Guo wrote:
> Hi Grant,
>
> On Mon, Feb 21, 2011 at 10:10:24AM -0700, Grant Likely wrote:
> > On Mon, Feb 21, 2011 at 2:46 AM, Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> wrote:
> [...]
> > >> + clocks {
>
> Do we already have a clock binding specification, which is followed
> by this example? Or the properties given here still can be discussed
> and open to change?
>
> Also to support dynamically creating and registering 'struct clk' per
> dt clock nodes, I need to add a few properties to map stuff like
> parent 'struct clk', con_id of 'struct clk_lookup'. Is there any
> specification to follow, or I can draft it per the needs of my work?
The clock specifications are still in draft. I'm not willing to lock
down on a binding until we've got some real implementations to back
them up. If you need additional properties, go ahead an propose them.
Keep in mind when defining/extending bindings, that the dt is intended
to represent hardware layout, not Linux kernel internal implementation
details. Try to avoid describing things in a linux-specific way.
>
> > >> + #address-cells = <1>;
> > >> + #size-cells = <0>;
> > >> +
> > >
> > > Can we use hex value here to keep the consistency throughout the file?
> >
> > For #address-cells and #size-cells use decimal integers.
> >
> > >
> > >> + uart_clk0: uart@0 {
> >
> > @0 should only be specified if the node has a 'reg = <0>' property.
> > In this case it doesn't so either 'reg' should be added, or '@0'
> > should be removed.
> >
> > >> + compatible = "clock";
> > >> + clock-outputs = "imx-uart.0";
> > >> + };
> > >> +
> > >> + uart_clk1: uart@1{
> > >
> > > Can we put a space before "{" to keep the consistency throughout the file?
> >
> > Yes, please.
> >
> > >
> > >> + compatible = "clock";
> > >> + clock-outputs = "imx-uart.1";
> > >> + };
> > >> +
> > >> + uart_clk2: uart@2{
> > >
> > > ditto
> > >
> > >> + compatible = "clock";
> > >> + clock-outputs = "imx-uart.2";
> > >> + };
>
> --
> Regards,
> Shawn
>
next prev parent reply other threads:[~2011-02-28 18:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 8:12 [PATCH 0/3] Add MX51 basic DT support Jason Liu
[not found] ` <1298016730-22761-1-git-send-email-r64343-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2011-02-18 8:12 ` [PATCH 1/3] arm/dt: add basic mx51 device tree support Jason Liu
[not found] ` <1298016730-22761-2-git-send-email-r64343-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2011-02-21 8:37 ` Shawn Guo
2011-02-28 6:48 ` Shawn Guo
[not found] ` <AANLkTi=v4X6XU9VUOVyr1MYZVsBeF494MBP3aeoZc4y6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-07 5:05 ` Jason Hui
2011-02-18 8:12 ` [PATCH 2/3] arm/dt: add very basic dts file for babbage board Jason Liu
[not found] ` <1298016730-22761-3-git-send-email-r64343-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2011-02-21 9:46 ` Shawn Guo
[not found] ` <AANLkTikerADxGGRfnumWMN+s2r8gWOb1UAaS3tQ6DTe5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-02-21 17:10 ` Grant Likely
[not found] ` <AANLkTi=kxbzDCJqOnPNjCsNxMsLtcbbcGLfZbY05_Svh-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-02-22 14:13 ` Shawn Guo
[not found] ` <20110222141309.GH19871-+NayF8gZjK2ctlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2011-02-23 18:59 ` Grant Likely
2011-02-28 14:32 ` Shawn Guo
[not found] ` <20110228143159.GA3688-+NayF8gZjK2ctlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2011-02-28 18:09 ` Grant Likely [this message]
[not found] ` <20110228180917.GG13690-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>
2011-03-07 5:06 ` Jason Hui
2011-02-26 14:30 ` Shawn Guo
2011-02-18 8:12 ` [PATCH 3/3] serial/imx: parse from device tree support Jason Liu
[not found] ` <1298016730-22761-4-git-send-email-r64343-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2011-02-18 8:34 ` Arnd Bergmann
2011-02-28 10:35 ` Shawn Guo
[not found] ` <AANLkTind79cPhBoSbGZsVodYRRk4dEQpr4G-Zf19yi7G-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-07 5:08 ` Jason Hui
2011-02-18 15:12 ` [PATCH 0/3] Add MX51 basic DT support Rob Herring
[not found] ` <4D5E8C74.4090004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-02-21 2:10 ` Liu Hui-R64343
2011-02-21 8:17 ` Shawn Guo
[not found] ` <AANLkTinWF54qvgSc4MVjS4ONPb3upnwQ2YJzVxmePiH_-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-07 5:03 ` Jason Hui
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=20110228180917.GG13690@angua.secretlab.ca \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linaro-dev-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.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).