Re: [PATCH] Revert "spi: omap2-mcspi: convert to module_platform_driver" |
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
On Friday 03 August 2012 03:28 PM, Felipe Balbi wrote:
>> [ 1.496124] spi spi1.0: setup mode 0, 8 bits/w, 6000000 Hz max --> 0
>> > [ 1.503265] omap2_mcspi omap2_mcspi.1: registered child spi1.0
>> >
>> > If I modify the board file so that child spi1.0 is registered before
>> > spi1.2, then it starts to work properly:
> that sounds quite odd... Shubhro, have you seen this before on any of
> our platforms ?
>
I havent seen this behaviour may be I didn't have this configuration.
Will try to see if I have any way of recreating and testing the multi cs
on one of our boards.
BTW I didnt understand why does that matter at all the cs order.
Aaro,
I am missing what is making the order matter.
What is it that I am missing?
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Linux Arm (vger)]
[ARM Kernel]
[ARM MSM]
[Linux Tegra]
[Maemo Users]
[Linux USB Devel]
[Video for Linux]
[Linux Audio Users]
[Photo]
[Yosemite News]
[Yosemite Photos]
[Free Online Dating]
[Linux Kernel]
[Linux SCSI]
[XFree86]