From: Scott Wood <scottwood@freescale.com>
To: Tabi Timur-B04825 <B04825@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
Aggrwal Poonam-B10812 <B10812@freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Singh Sandeep-B37400 <B37400@freescale.com>
Subject: Re: [PATCH] Device Tree Bindings for Freescale TDM controller
Date: Mon, 19 Mar 2012 12:27:57 -0500 [thread overview]
Message-ID: <4F676C9D.2070301@freescale.com> (raw)
In-Reply-To: <CAOZdJXVU=1bW8_OTMecJHuWaa6_023UnUsfQTX8MGqd3E4SRAg@mail.gmail.com>
On 03/17/2012 11:07 AM, Tabi Timur-B04825 wrote:
> On Sat, Mar 17, 2012 at 2:33 AM, Aggrwal Poonam-B10812
> <B10812@freescale.com> wrote:
>>
>>>> + compatible = "fsl,p1010-tdm", "fsl,mpc8315-tdm";
>>>> + reg = <0x16000 0x200 0x2c000 0x2000>;
>>>> + clock-frequency = <0>;
>>>
>>> Show a real clock-frequency, perhaps with a comment saying it's typically
>>> filled in by boot software.
>
>> Okay.
>
> Scott, are you suggesting that Poonam put a non-zero number in the DTS
> for clock-frequency? If so, then I don't think that's a good idea, if
> U-Boot will always override it.
This is a device tree binding document, not U-Boot specific. It
describes what Linux (or another OS) can expect to see, not how it gets
there.
-Scott
next prev parent reply other threads:[~2012-03-19 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 1:30 [PATCH] Device Tree Bindings for Freescale TDM controller Poonam Aggrwal
2012-03-16 18:29 ` Scott Wood
2012-03-17 7:33 ` Aggrwal Poonam-B10812
2012-03-17 16:04 ` Tabi Timur-B04825
2012-03-17 16:07 ` Tabi Timur-B04825
2012-03-19 17:27 ` Scott Wood [this message]
2012-03-19 17:32 ` Timur Tabi
2012-03-19 17:55 ` Scott Wood
2012-03-19 17:32 ` 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=4F676C9D.2070301@freescale.com \
--to=scottwood@freescale.com \
--cc=B04825@freescale.com \
--cc=B07421@freescale.com \
--cc=B10812@freescale.com \
--cc=B37400@freescale.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linuxppc-dev@lists.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).