From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Jon Loeliger <jdl@jdl.com>
Subject: Re: [PATCH] Add StorCenter DTS first draft.
Date: Thu, 19 Jul 2007 07:54:38 +1000 [thread overview]
Message-ID: <1184795678.25235.269.camel@localhost.localdomain> (raw)
In-Reply-To: <5F6EB5F7-C5AE-437F-9DF1-22FE38D7A841@kernel.crashing.org>
On Wed, 2007-07-18 at 18:13 +0200, Segher Boessenkool wrote:
> >> + PowerPC,603e { /* Really 8241 */
> >> + device_type = "cpu";
> >> + reg = <0>;
> >> + clock-frequency = <d# 200000000>; /* Hz */
> >> + timebase-frequency = <d# 33333333>; /* Hz */
> >> + bus-frequency = <0>;
> >> + /* Following required by dtc but not used */
> >> + i-cache-line-size = <0>;
> >> + d-cache-line-size = <0>;
> >> + i-cache-size = <4000>;
> >> + d-cache-size = <4000>;
> >> + };
> >
> > The 32 bits kernel may not be using those yet, but it will. 64 bits
> > does
> > already and I plan to merge those bits at one point.
>
> Hrm, what does it use it for? Are you going to require
> all other defined CPU properties as well (like the PowerPC
> binding does)?
Cache line size is used by the kernel on ppc64 for things like clearing
memory (to get the stride between subsequent dcbz) or flushing the
cache :-) It's also passed on to userland.
If it's absent from the device-tree, we default to the values in the
cputable, but if you're going to put the properties in the tree, don't
put a 0 in there. As it is, the day I make the 64 bits code common, your
DT will break unless I special case "0".
Ben.
next prev parent reply other threads:[~2007-07-18 21:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 14:22 [PATCH] Add StorCenter DTS first draft Jon Loeliger
2007-07-17 14:57 ` Segher Boessenkool
2007-07-17 16:26 ` Josh Boyer
2007-07-17 16:38 ` Segher Boessenkool
2007-07-17 22:27 ` Jon Loeliger
2007-07-17 22:34 ` Scott Wood
2007-07-17 22:56 ` Jon Loeliger
2007-07-18 16:19 ` Segher Boessenkool
2007-07-18 18:27 ` Kumar Gala
2007-07-19 17:03 ` Segher Boessenkool
2007-07-18 1:39 ` Benjamin Herrenschmidt
2007-07-18 16:13 ` Segher Boessenkool
2007-07-18 21:54 ` Benjamin Herrenschmidt [this message]
2007-07-19 16:05 ` Jon Loeliger
2007-07-19 17:07 ` Segher Boessenkool
2007-07-19 21:39 ` Benjamin Herrenschmidt
2007-07-20 7:14 ` 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=1184795678.25235.269.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.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).