From: Timur Tabi <timur@freescale.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/p5040ds: Add support for P5040DS board
Date: Tue, 24 Jul 2012 15:45:44 -0500 [thread overview]
Message-ID: <500F0978.7010201@freescale.com> (raw)
In-Reply-To: <500EE1BB.6060104@freescale.com>
Scott Wood wrote:
>> > + bus-range = <0x0 0xff>;
> Do we really need this?
I can't find any documentation for this property, but it does appear to be
initialized by U-Boot:
/* We assume a cfg_addr not being set means we didn't setup the controller */
if ((hose == NULL) || (hose->cfg_addr == NULL)) {
fdt_del_node(blob, off);
} else {
bus_range[0] = 0;
bus_range[1] = hose->last_busno - hose->first_busno;
fdt_setprop(blob, off, "bus-range", &bus_range[0], 2*4);
fdt_pci_dma_ranges(blob, off, hose);
}
So I have no idea if it's required in the DTS.
>> > + clock-frequency = <33333333>;
> I doubt this is accurate.
Every other DTS sets this property to 33333333, and I don't see any code
in U-boot that fixes it up.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-07-24 20:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 16:42 [PATCH] powerpc/p5040ds: Add support for P5040DS board Timur Tabi
2012-07-24 17:56 ` Scott Wood
2012-07-24 18:09 ` Timur Tabi
2012-07-24 18:32 ` Scott Wood
2012-07-24 18:55 ` Timur Tabi
2012-07-24 20:42 ` Scott Wood
2012-07-25 2:55 ` Zang Roy-R61911
2012-07-24 19:40 ` Timur Tabi
2012-07-24 20:16 ` Timur Tabi
2012-07-24 20:45 ` Timur Tabi [this message]
2012-07-24 21:19 ` Timur Tabi
2012-07-24 21:31 ` Scott Wood
2012-07-24 21:36 ` Timur Tabi
2012-07-24 21:42 ` Scott Wood
2012-07-24 21:43 ` Timur Tabi
2012-07-24 21:45 ` Scott Wood
2012-07-24 21:47 ` Timur Tabi
2012-07-24 21:54 ` 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=500F0978.7010201@freescale.com \
--to=timur@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@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).