On Mon, May 2, 2011 at 3:39 PM, Felipe Balbi <balbi@xxxxxx> wrote:
> On Mon, May 02, 2011 at 12:49:39PM +0300, Felipe Balbi wrote:
>> Hi Greg,
>>
>> Here are 5 small patches to fix last few mistakes
>> from last merge window.
>>
>> The "add regulator support for EHCI" is actually
>> fixing a regression on many boards since during
>> the merge window that ended up being removed.
>>
>> So, although it doesn't sound from the description,
>> it's fixing many boards who depend on those regulators
>> to work.
>>
>> The following changes since commit f0e615c3cb72b42191b558c130409335812621d8:
>>
>> Linux 2.6.39-rc4 (2011-04-18 21:26:00 -0700)
>>
>> are available in the git repository at:
>> git://gitorious.org/usb/usb.git ..BRANCH.NOT.VERIFIED..
>
> sorry about this rubbish mail. Nevermind it.
Hi greg
requesting you to drop the patch with commit id :
3dc18b81e69bc6a61108f40ad3e437e93df56f0a
patch description is as follows:
omap:usb: fixing ehci phy gpio values for omap3
The gpio of EHCI phy should be 0 instead of 1;
This fixes the hub enumeration issue in beagle xm board.
Signed-off-by: Keshava Munegowda <keshava_mgowda@xxxxxx>
Tested-by: Steve Calfee <stevecalfee@xxxxxxxxx>
Signed-off-by: Felipe Balbi <balbi@xxxxxx
I am extremely sorry to trouble you in this.
This patch is was first made by Juergen Kilb ( patch description and link is
given below); But I was not aware of it and reinvented wheel with
beagle-xm board :(
So, balbi will send the another git pull request.
Here is the link :
http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg48215.html
omap:usbhs:Fixed gpio polarity of gpio USB-phy reset
With commit 19403165 a main part of ehci-omap.c moved to
drivers/mfd/omap-usb-host.c created by commit 17cdd29d.
Due to this reorganisation the polarity used to reset the
external USB phy changed and USB host doesn't recognize
any devices.
Signed-off-by: Juergen Kilb <J.Kilb@xxxxxxxxx>
regards
keshava
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
