From: Dan Malek <dan@embeddededge.com>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] powerpc: Add FSL CPM2 device tree node documentation
Date: Thu, 30 Mar 2006 00:05:38 -0500 [thread overview]
Message-ID: <bed6c40abe7664da7506270a46611d00@embeddededge.com> (raw)
In-Reply-To: <20060328161431.18517.82573.stgit@vitb.ru.mvista.com>
On Mar 28, 2006, at 11:14 AM, Vitaly Bordug wrote:
> Updated the documentation to include the initial description of the
> CPM2
> device that are used on PQII and PQIII families.
I haven't followed the device tree development in detail, but when
looking at this the only question that comes to mind is wondering
what this really does to help me. None of the information provided
here is variable nor configurable .... except I guess for the internal
register base address (IMMR), which for some reason has turned
into a variable which hasn't changed since I did the first kernel port.
About the only thing that is variable, which is the two different bank
addresses of the CPM memory that affects the configuration of
the FCCs in Ethernet mode, isn't reflected here in any way.
> + brg@119f0 {
> + device_type = "brg";
> + model = "BRG1";
> + reg = <119f0>;
> + linux,phandle = <775>;
> + };
Why? We already know it's at this address offset.
> +
> + cpmux@11b04 {
> + device_type = "cpmux";
> + compatible = "fcc";
> + reg = <11b04>;
> + };
> +
> + cpmux@11b08 {
> + device_type = "cpmux";
> + compatible = "scc";
> + reg = <11b08>;
> + };
I don't understand the value of these either.
> +
> + scc@11a20 {
> + device_type = "serial";
> + compatible = "cpm_uart";
> + model = "SCC1";
> + reg = <11a20 100>;
> + reg_pram = <8000 ff>;
> + clock_setup = <0x00ffffff 0>;
> + interrupts = <28 3>;
None of this is variable. If you know you are using scc1,
you must use certain configuration bits in the cmxscr (the
thing you are calling cpmux). Why would you want to make
this variable and prone to error? The driver knows, and
there are no options. Same for the interrupts that are used.
> + fcc@11300 {
> + device_type = "network";
> + compatible = "fs_enet";
> + model = "FCC1";
> + reg = <11300 1f>;
> + reg_pram = <8400 ff>;
> + address = [00 00 00 00 00 00];
I'm assuming this is the MAC address, and is probably
the only thing I see of value here.
> More devices will be defined as this spec matures.
I just don't understand the value of this. Will you explain
it for me?
Thanks.
-- Dan
next prev parent reply other threads:[~2006-03-30 5:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 16:14 [PATCH] powerpc: Add FSL CPM2 device tree node documentation Vitaly Bordug
2006-03-28 16:37 ` Kumar Gala
2006-03-28 16:42 ` Vitaly Bordug
2006-03-28 16:55 ` Paul Nasrat
2006-04-12 23:19 ` Andy Fleming
2006-04-13 5:14 ` Paul Nasrat
2006-04-13 15:15 ` Jon Loeliger
2006-04-21 11:17 ` Paul Mackerras
2006-03-30 5:05 ` Dan Malek [this message]
2006-03-30 6:10 ` Paul Mackerras
2006-03-30 10:37 ` Vitaly Bordug
2006-03-30 10:26 ` Vitaly Bordug
2006-03-30 13:09 ` Dan Malek
2006-03-30 14:37 ` Kumar Gala
2006-03-30 15:14 ` Dan Malek
2006-03-30 15:02 ` Vitaly Bordug
2006-03-30 15:43 ` Kumar Gala
2006-03-30 15:10 ` Vitaly Bordug
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=bed6c40abe7664da7506270a46611d00@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=vbordug@ru.mvista.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).