Re: [PATCH/RESEND 0/2] usb: musb: am335x support part-2

2012-11-08 Thread Felipe Balbi
Hi,

On Tue, Nov 06, 2012 at 08:44:59PM +0530, Afzal Mohammed wrote:
 Hi Balbi,
 
 This is a resend of remaining changes to get am335x usb working. These
 were sent on 31 Oct with subject, usb: musb: dsps: fixes for -rc.

there is no more time for this to reach -rc. Do we need it for v3.8
merge window ?

 First one restores capability to support at least one instance of musb.
 Without it, even a single instance can't be supported as change which
 is reverted by it was made along with multi phy changes and nop
 transciever dt support, both other changes didn't make it to mainline. 
 
 Second one corrects binding document; changes were made in driver as
 per review comments, but documentation was not updated.

second one is clearly not for -rc.

-- 
balbi


signature.asc
Description: Digital signature


[PATCH/RESEND 0/2] usb: musb: am335x support part-2

2012-11-06 Thread Afzal Mohammed
Hi Balbi,

This is a resend of remaining changes to get am335x usb working. These
were sent on 31 Oct with subject, usb: musb: dsps: fixes for -rc.

First one restores capability to support at least one instance of musb.
Without it, even a single instance can't be supported as change which
is reverted by it was made along with multi phy changes and nop
transciever dt support, both other changes didn't make it to mainline. 

Second one corrects binding document; changes were made in driver as
per review comments, but documentation was not updated.

This is made on top of your musb branch. To get USB0 functional on
am335x based boards like beagle bone, first one is required.

Regards
Afzal

Afzal Mohammed (2):
  Revert usb: musb: dsps: remove explicit NOP device creation
  usb: musb: dsps: document dt bindings properly

 Documentation/devicetree/bindings/usb/am33xx-usb.txt | 8 
 drivers/usb/musb/musb_dsps.c | 3 ++-
 2 files changed, 6 insertions(+), 5 deletions(-)

-- 
1.7.12

--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html