[RFC][PATCH] MPC832x_RDB: update dts to use spi, register mmc_spi stub

[Anton Vorontsov]

On Fri, Jul 27, 2007 at 03:14:06AM -0500, Kumar Gala wrote:
>
> On Jul 26, 2007, at 8:57 AM, Anton Vorontsov wrote:
[...]
>>
>> @@ -207,20 +222,36 @@
>>
>>  		spi at 4c0 {
>>  			device_type = "spi";
>> +			device-id = <1>;
>
> Can we just use the reg value for bus_num in the kernel.

Sure, technically nothing prevents this. But, QE specs names
SPIs by these ids. Plus, from the kernel side spi name will be
not pretty, it will be spi1216.1. Reg value making little sense
to the userspace (or kernel-side SPI layer). Still want get
rid of device-id?

>>  			compatible = "fsl_spi";
>>  			reg = <4c0 40>;
>>  			interrupts = <2>;
>>  			interrupt-parent = <&qeic>;
>> -			mode = "cpu";
>> +			mode = "qe";
>> +			sysclk = <5f5e100>; /* 100000000 Hz */
>
> we don't need this in the spi node, its just the system clock frequency 
> which we can get other ways.

Will try, I guess "bus-frequency" property of soc8323 is what I need.

>> +			max-chipselect = <1>;
>
> I'm not sure how I feel about this in here, I'm thinking it should go.

It's board-specific, i.e. how much chips connected to this SPI bus.
SPI layer needs this. Otherwise I have to pass it from board file,
but isn't it fits nicely in the DT?

>> +			pio-handle = <&spi1pio>;
>> +
>> +			mmc at 01 {
>> +				device_type = "mmc";
>> +				compatible = "mmc-spi";
>> +				device-id = <1>;
>> +				max-speed-hz = <bebc20>; /* 12500000 Hz */
>> +				chip-select = <0>;
>> +				pio-handle = <&mmc1pio>;
>> +			};
>
> we should do this in board code and not the device tree.

Well, I've done this initially. But Vitaly hinted that this could
be done in the DT instead, which made sense to me - mmc is the child
device of SPI bus. Why do you think it shouldn't be in the DT? I'm
not arguing, just want understand this.

Thanks!

-- 
Anton Vorontsov
email: cbou at mail.ru
backup email: ya-cbou at yandex.ru
irc://irc.freenode.net/bd2