Thread (23 messages) flat view 23 messages, 4 authors, 2012-10-29

[PATCH v2 1/3] drivers: bus: ocp2scp: add pdata support

From: tony@atomide.com (Tony Lindgren)
Date: 2012-10-26 17:17:10
Also in: linux-omap, lkml

* Felipe Balbi [off-list ref] [121025 23:55]:
On Thu, Oct 25, 2012 at 10:44:47AM -0700, Tony Lindgren wrote:
quoted
* Felipe Balbi [off-list ref] [121024 23:24]:
quoted
Hi,

On Wed, Oct 24, 2012 at 05:48:07PM -0700, Tony Lindgren wrote:
quoted
* Tony Lindgren [off-list ref] [121016 09:53]:
quoted
* Kishon Vijay Abraham I [off-list ref] [121007 23:01]:
quoted
ocp2scp was not having pdata support which makes *musb* fail for non-dt
boot in OMAP platform. The pdata will have information about the devices
that is connected to ocp2scp. ocp2scp driver will now make use of this
information to create the devices that is attached to ocp2scp.

Signed-off-by: Kishon Vijay Abraham I <redacted>
This fixes the regression on my panda es for musb port:

Acked-by: Tony Lindgren <tony@atomide.com>
Looks like nobody has picked this one up and we need it to
fix the musb regression on omap, so I'll queue these up.
I don't seem to have the patches around in any mailbox :-(
Bounced them to you. Do you have any better ideas for the
-rc cycle to fix the MUSB regression on omap4?
Well, there are two regressions that I know of. One is caused by the
mode1 DMA changes, which I'll just revert, and the other is the
missing platform_data support on the new PHY driver which these patches
are supposed to solve, right ?
Yes that's it AFAIK.

Regards,

Tony
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help