On Thu, Dec 30, 2010 at 02:44:40AM -0500, Ben Gamari wrote:
On Mon, 27 Dec 2010 11:20:38 +0200, Felipe Balbi ba...@ti.com wrote:
On Thu, Dec 23, 2010 at 12:16:22PM -0500, Ben Gamari wrote:
Is this change slated to go into 2.6.37? As it stands it looks like
2.6.37 will be released with
Hello.
On 30-12-2010 15:27, Felipe Balbi wrote:
Is this change slated to go into 2.6.37? As it stands it looks like
2.6.37 will be released with completely broken musb support on many boards
(including the BeagleBoard).
yes, it is.
Are you sure? We are currently at -rc8 and yet this
On Thu, 30 Dec 2010 14:27:38 +0200, Felipe Balbi ba...@ti.com wrote:
Yes. The patch is waiting for the merge window, check linux-next or
Greg's usb-next branch.
So I guess no working USB in 2.6.37 in that case?
- Ben
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
On Thu, Dec 30, 2010 at 5:00 PM, Ben Gamari bgamari.f...@gmail.com wrote:
On Thu, 30 Dec 2010 14:27:38 +0200, Felipe Balbi ba...@ti.com wrote:
Yes. The patch is waiting for the merge window, check linux-next or
Greg's usb-next branch.
So I guess no working USB in 2.6.37 in that case?
You can
On Thu, Dec 30, 2010 at 05:24:05PM +0200, Anca Emanuel wrote:
On Thu, Dec 30, 2010 at 5:00 PM, Ben Gamari bgamari.f...@gmail.com wrote:
On Thu, 30 Dec 2010 14:27:38 +0200, Felipe Balbi ba...@ti.com wrote:
Yes. The patch is waiting for the merge window, check linux-next or
Greg's usb-next
On Thu, Dec 30, 2010 at 10:00:46AM -0500, Ben Gamari wrote:
On Thu, 30 Dec 2010 14:27:38 +0200, Felipe Balbi ba...@ti.com wrote:
Yes. The patch is waiting for the merge window, check linux-next or
Greg's usb-next branch.
So I guess no working USB in 2.6.37 in that case?
For am35x, I guess
Hello.
Felipe Balbi wrote:
Yes. The patch is waiting for the merge window, check linux-next or
Greg's usb-next branch.
So I guess no working USB in 2.6.37 in that case?
For am35x, I guess not. All in all, it was a change to omap's arch code
which broke am35x in the first place. Well, the
On Fri, 3 Dec 2010 23:42:45 +0530, Ajay Kumar Gupta ajay.gu...@ti.com wrote:
As the control.h have been moved to new location and it's
uses are not allowed to drivers directly so moving the phy
control, interrupt clear and reset functionality to board
files.
I could have sworn I tried
On Mon, 27 Dec 2010 11:20:38 +0200, Felipe Balbi ba...@ti.com wrote:
On Thu, Dec 23, 2010 at 12:16:22PM -0500, Ben Gamari wrote:
Is this change slated to go into 2.6.37? As it stands it looks like
2.6.37 will be released with completely broken musb support on many boards
(including the
On Thu, Dec 23, 2010 at 12:16:22PM -0500, Ben Gamari wrote:
On Fri, 3 Dec 2010 23:42:45 +0530, Ajay Kumar Gupta ajay.gu...@ti.com wrote:
As the control.h have been moved to new location and it's
uses are not allowed to drivers directly so moving the phy
control, interrupt clear and reset
On Fri, 3 Dec 2010 23:42:45 +0530, Ajay Kumar Gupta ajay.gu...@ti.com wrote:
As the control.h have been moved to new location and it's
uses are not allowed to drivers directly so moving the phy
control, interrupt clear and reset functionality to board
files.
Is this change slated to go into
As the control.h have been moved to new location and it's
uses are not allowed to drivers directly so moving the phy
control, interrupt clear and reset functionality to board
files.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
---
Patch created against today's linus tree.
I
diff --git a/arch/arm/mach-omap2/usb-musb.c b/arch/arm/mach-omap2/usb-
musb.c
index 7260558..1f32fdb 100644
--- a/arch/arm/mach-omap2/usb-musb.c
+++ b/arch/arm/mach-omap2/usb-musb.c
@@ -33,6 +33,82 @@
#ifdef CONFIG_USB_MUSB_SOC
+static void am35x_musb_phy_power(u8 on)
+{
+
Ajay Kumar Gupta wrote:
As the control.h have been moved to new location and it's
uses are not allowed to drivers directly so moving the phy
control, interrupt clear and reset functionality to board
files.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
---
Patch created against today's
Hello.
Ajay Kumar Gupta wrote:
As the control.h have been moved to new location and it's
uses are not allowed to drivers directly so moving the phy
control, interrupt clear and reset functionality to board
files.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
[...]
diff --git
15 matches
Mail list logo
