From: Scott Wood <scottwood@freescale.com>
To: Alan Bennett <alan@akb.net>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: device tree question
Date: Tue, 18 Sep 2007 17:36:30 -0500 [thread overview]
Message-ID: <46F052EE.1040004@freescale.com> (raw)
In-Reply-To: <bfa0697f0709181521r62c81b55q65cd49d4e4ba3637@mail.gmail.com>
Alan Bennett wrote:
> I finally saw some light, though not much, and have made several
> changes to a new dts file.
>
> BTW: I've lost my __log_buf
> was 02aec04 now it's not there, nor is it Load Address: 0x00400000 + 02aec04
You can't rely on that sort of thing staying at the same address...
check System.map to see where it is now.
> BRx/ORx=CSx
> 128MB flash: CS0 = F800_0000 f800_0000
> 128MB flash: CS4 = D000_0000 f800_0000
> 128MB SDRAM: CS1 = 0000_0000 f800_0000
Below, you seem to be assuming flash is CS0 and CS3, and that CS1 is BCSR.
> / {
> model = "MPC8248";
> compatible = "fsl,mpc8248";
Model/compatible should be for the board, not the chip.
> board-control@1,0 {
> reg = <1 0 20>;
> compatible = "fsl,mpc8248-bcsr";
> };
BCSR is board-specific, not chip-specific. The compatible should
reference the specific board's name (with the board vendor replacing fsl).
> flash2@3,0 {
The unit address provides uniqueness; just do "flash@3,0".
> compatible = "jedec-flash";
Note that this should be cfi-flash if your flash is CFI-compatible.
> reg = <0 0 8000000>;
> bank-width = <1>;
> device-width = <32>;
These are specified in bytes, not bits or chips.
I'm guessing you should set them both to 4 based on the above.
> };
> dualportram@1,0 {
Should be dualportram@5,0
> reg = <5 0 100000>;
> compatible = "fsl,mpc8248-dualportram";
> };
> dualportcsr@1,0 {
Should be dualportcsr@6,0
> soc@f0000000 {
> #address-cells = <1>;
> #size-cells = <1>;
> device_type = "soc";
> compatible = "fsl,mpc8272", "fsl,pq2-soc";
The 8272 references should be 8248, though it doesn't currently matt
> serial@11a82 {
> device_type = "serial";
> compatible = "fsl,mpc8272-smc-uart",
> "fsl,cpm2-smc-uart";
> reg = <11a82 20 8300 100>;
> interrupts = <2b 8>;
> interrupt-parent = <&PIC>;
> fsl,cpm-brg = <4>;
> fsl,cpm-command = <0ce00000>;
This doesn't look right...
You'll need to update reg, interrupts, and fsl,cpm-command for whichever
SMC port you're using.
This is for SMC1 on the ep8248e:
serial@11a80 {
device_type = "serial";
compatible = "fsl,mpc8248-smc-uart",
"fsl,cpm2-smc-uart";
reg = <11a80 20 1100 40>;
interrupts = <4 8>;
interrupt-parent = <&PIC>;
fsl,cpm-brg = <7>;
fsl,cpm-command = <1d000000>;
};
Note that the 1100 in reg should be set to wherever your firmware
locates the SMC's parameter RAM block, and fsl,cpm-brg should be set to
whichever BRG your firmware and/or platform code set the SMC port to.
> mdio@10d40 {
> device_type = "mdio";
> compatible = "fsl,mpc8272ads-mdio-bitbang",
> "fsl,mpc8272-mdio-bitbang",
> "fsl,cpm2-mdio-bitbang";
> reg = <10d40 14>;
> #address-cells = <1>;
> #size-cells = <0>;
> fsl,mdio-pin = <12>;
> fsl,mdc-pin = <13>;
Does your board do mdio the same way as the mpc8272ads board? if not,
you'll have to change this.
-Scott
next prev parent reply other threads:[~2007-09-18 22:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 20:43 device tree question Alan Bennett
2007-09-18 22:06 ` Scott Wood
2007-09-18 22:21 ` Alan Bennett
2007-09-18 22:36 ` Scott Wood [this message]
[not found] ` <bfa0697f0709181604i5758824foad67a86455f45d8e@mail.gmail.com>
[not found] ` <46F05BF7.6020906@freescale.com>
[not found] ` <bfa0697f0709190638r6894fab6gd31a5672a997e97@mail.gmail.com>
[not found] ` <46F16BD4.2000207@freescale.com>
[not found] ` <bfa0697f0709191420x5a6aed9dx499fe4a8cf6b1b2d@mail.gmail.com>
[not found] ` <46F19326.7050507@freescale.com>
2007-09-20 17:53 ` Alan Bennett
2007-09-20 18:31 ` Scott Wood
2007-09-20 21:38 ` Alan Bennett
2007-09-20 21:43 ` Scott Wood
-- strict thread matches above, loose matches on Subject: below --
2008-08-07 19:56 Device " Steven A. Falco
2008-08-09 7:41 ` Benjamin Herrenschmidt
2008-08-11 14:05 ` Steven A. Falco
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=46F052EE.1040004@freescale.com \
--to=scottwood@freescale.com \
--cc=alan@akb.net \
--cc=linuxppc-embedded@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).