linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Linuxppc-dev@ozlabs.org
Subject: DTS question
Date: Tue, 02 Sep 2008 15:56:30 -0600	[thread overview]
Message-ID: <48BDB68E.8040806@mlbassoc.com> (raw)

Following on with my RTC problem, I cut&pasted this from
the TQM5200 dts file:
                 i2c@3d40 {
                         #address-cells = <1>;
                         #size-cells = <0>;
                         compatible = "fsl,mpc5200-i2c","fsl-i2c";
                         reg = <0x3d40 0x40>;
                         interrupts = <2 16 0>;
                         interrupt-parent = <&mpc5200_pic>;
                         fsl5200-clocking;

                          rtc@68 {
                                 device_type = "rtc";
                                 compatible = "dallas,ds1307";
                                 reg = <0x68>;
                         };
                 };

However, the dts file I started with had this (*mine*):
		i2c@3d40 {
			#address-cells = <1>;
			#size-cells = <0>;
			compatible = "fsl,mpc5200-i2c","fsl-i2c";
			cell-index = <1>;
			reg = <3d40 40>;
			interrupts = <2 10 0>;
			interrupt-parent = <&mpc5200_pic>;
			fsl5200-clocking;
		};

Notice the different mix of hex (0xNNN) and implied hex values.
This is really confusing to me.  Even more so when I added the
RTC snippet cut directly from the TQM5200 file:

                          rtc@68 {
                                 device_type = "rtc";
                                 compatible = "dallas,ds1307";
                                 reg = <0x68>;
                         };

This yielded a syntax error when merged with my platform dts.
When I changed the 'reg=<0x68>' to 'reg=<68>', the syntax error
went away & it worked perfectly.

What gives?  Why is explicit hex sometimes an error and sometimes not?
Is the format of this file documented anywhere (I've not found it)?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

             reply	other threads:[~2008-09-02 21:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-02 21:56 Gary Thomas [this message]
2008-09-02 23:42 ` DTS question David Gibson
2008-09-03  0:14   ` Gary Thomas
2008-09-03  0:25     ` David Gibson
2008-09-02 23:43 ` Scott Wood
  -- strict thread matches above, loose matches on Subject: below --
2008-03-20 21:33 Sean MacLennan
2008-03-20 21:47 ` Segher Boessenkool
2008-03-20 21:48 ` Scott Wood
2008-03-20 22:19 ` Sean MacLennan
2008-03-20 22:26   ` Scott Wood
2008-03-21  4:12     ` Sean MacLennan
2008-03-21  4:34       ` Grant Likely
2008-03-21  5:09         ` Sean MacLennan
2008-03-21  7:05           ` David Gibson
2008-03-21 11:35             ` Segher Boessenkool
2008-03-25 22:12               ` David Gibson
2008-03-26 15:32                 ` Segher Boessenkool
2008-03-26 23:40                   ` David Gibson
2008-03-27  3:42                     ` Sean MacLennan
2008-03-21 11:31         ` Segher Boessenkool

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=48BDB68E.8040806@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --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).