linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Marian Balakowicz <m8@semihalf.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2 11/12] [POWERPC] Promess Motion-PRO DTS
Date: Tue, 06 Nov 2007 21:02:10 +0100	[thread overview]
Message-ID: <4730C842.9020601@semihalf.com> (raw)
In-Reply-To: <20071105005626.GI19867@localhost.localdomain>

David Gibson wrote:
> On Sun, Nov 04, 2007 at 12:53:17AM +0100, Marian Balakowicz wrote:
>> Add device tree source file for Motion-PRO board.
> [snip]
>> +		motionpro-statusled@660 {	// Motion-PRO status LED
>> +			compatible = "promess,motionpro-statusled";
>> +			cell-index = <6>;
>> +			reg = <660 10>;
>> +			interrupts = <1 f 0>;
>> +			interrupt-parent = <&mpc5200_pic>;
>> +			blink-delay = <64>; // 100 msec
>> +		};
>> +
>> +		motionpro-readyled@670 {	// Motion-PRO ready LED
>> +			compatible = "promess,motionpro-readyled";
>> +			cell-index = <7>;
> 
> These cell-index values for the LEDs look very strange.  How are they
> used?
[snip]
>> +
>> +		mscan@980 {
>> +			compatible = "mpc5200b-mscan","mpc5200-mscan";
>> +			cell-index = <1>;
> 
> As for serial and gpt, is cell-index really suitable here?

Ok, removed those unused "cell-index" properties.

> [snip]
>> +		spi@f00 {
>> +			device_type = "spi";
>> +			compatible = "mpc5200b-spi","mpc5200-spi";
>> +			reg = <f00 20>;
>> +			interrupts = <2 d 0 2 e 0>;
>> +			interrupt-parent = <&mpc5200_pic>;
>> +		};
> [snip]
>> +		// PSC2 in spi master mode 
>> +		spi@2200 {		// PSC2
>> +			device_type = "spi";
>> +			compatible = "mpc5200b-psc-spi","mpc5200-psc-spi";
>> +			cell-index = <1>;
> 
> cell-index present for one spi, but not the other makes be even more
> suspicious about it's applicability here...

These are two different SPIs, both are part of the SoC but first one
is dedicated SPI interface while the second one is PSC port in a SPI
mode. Driver for the second one (mpc52xx_psc_spi.c) is actually using
cell-index to get the PSC port number it's controlling.

> [snip]
>> +	lpb {
>> +		model = "fsl,lpb";
>> +		compatible = "fsl,lpb";
> 
> Is lpb another one of these chipselect/offset configurable bus bridge
> things?  If so, you should use a 2-cell addressing convention for the
> subnodes like fsl localbus and 4xx EBC.

Yes, it is, so I have switched to 2-cell addressing. Please see the v3
respin of the patches.


>> +		// 8-bit custom Anybus Module on LocalPlus Bus CS3
>> +		anybus50020000 {
> 
> Missing '@'.

Fixed.

Thanks,
m.

  reply	other threads:[~2007-11-06 20:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-03 23:52 [PATCH v2 00/12] [POWERPC] Add TQM5200/CM5200/Motion-PRO board support Marian Balakowicz
2007-11-03 23:52 ` [PATCH v2 01/12] [POWERPC] Add 'model: ...' line to common show_cpuinfo() Marian Balakowicz
2007-11-04 22:17   ` David Gibson
2007-11-05  1:40   ` Olof Johansson
2007-11-03 23:52 ` [PATCH v2 02/12] [POWERPC] Add 'fsl, lpb' bus type for MPC5200 LocalPlus Bus Marian Balakowicz
2007-11-04 22:18   ` David Gibson
2007-11-03 23:52 ` [PATCH v2 03/12] [POWERPC] Add common mpc52xx_setup_pci() routine Marian Balakowicz
2007-11-03 23:52 ` [PATCH v2 04/12] [POWERPC] Add generic support for simple MPC5200 based boards Marian Balakowicz
2007-11-03 23:52 ` [PATCH v2 05/12] [POWERPC] Export mpc52xx_map_node() routine symbol Marian Balakowicz
2007-11-04  4:09   ` Stephen Rothwell
2007-11-06 12:23     ` Marian Balakowicz
2007-11-03 23:52 ` [PATCH v2 06/12] [POWERPC] TQM5200 DTS Marian Balakowicz
2007-11-05  0:47   ` David Gibson
2007-11-06 19:50     ` Marian Balakowicz
2007-11-03 23:52 ` [PATCH v2 07/12] [POWERPC] TQM5200 defconfig Marian Balakowicz
2007-11-03 23:52 ` [PATCH v2 08/12] [POWERPC] CM5200 DTS Marian Balakowicz
2007-11-05  0:50   ` David Gibson
2007-11-06 19:18     ` Marian Balakowicz
2007-11-03 23:53 ` [PATCH v2 09/12] [POWERPC] CM5200 defconfig Marian Balakowicz
2007-11-03 23:53 ` [PATCH v2 10/12] [POWERPC] Motion-PRO: Add LED support Marian Balakowicz
2007-11-04  4:27   ` Stephen Rothwell
2007-11-06 11:58     ` Marian Balakowicz
2007-11-03 23:53 ` [PATCH v2 11/12] [POWERPC] Promess Motion-PRO DTS Marian Balakowicz
2007-11-05  0:56   ` David Gibson
2007-11-06 20:02     ` Marian Balakowicz [this message]
2007-11-03 23:53 ` [PATCH v2 12/12] [POWERPC] Promess Motion-PRO defconfig Marian Balakowicz

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=4730C842.9020601@semihalf.com \
    --to=m8@semihalf.com \
    --cc=david@gibson.dropbear.id.au \
    --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).