On Tue, Feb 23, 2010 at 10:46:44AM +0100, ext Ajay Kumar Gupta wrote:
MUSB can supply upto 500mA such as, AM3517 and OMAP3EVM Rev =E and thus
the 'power' field has to hold values above 255.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
applied, thanks
--
balbi
--
To unsubscribe from
to hold all possible values
Hi,
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Friday, February 26, 2010 3:50 AM
To: Felipe Balbi
Cc: Gupta, Ajay Kumar; linux-omap@vger.kernel.org
Subject: Re: [PATCH] musb: fix power field to hold all possible values
On Tue, Mar 23, 2010 at 12:41:16PM +0100, ext Gupta, Ajay Kumar wrote:
Felipe/Tony,
Any update on this patch ?
It's fine by me but I was expecting Tony to pick it up since it's on the
arch code.
Tony, do you want me to queue it for Greg or you take it forward ?
--
balbi
--
To unsubscribe
* Felipe Balbi m...@felipebalbi.com [100223 12:30]:
Hi,
On Tue, Feb 23, 2010 at 08:01:50PM +0530, Gupta, Ajay Kumar wrote:
Board files are providing the actual mA and it is getting divided in
Arch/arm/mach-omap2/usb-musb.c. See the code snippet below,
musb_plat.clock = ick;
Hi,
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Friday, February 26, 2010 3:50 AM
To: Felipe Balbi
Cc: Gupta, Ajay Kumar; linux-omap@vger.kernel.org
Subject: Re: [PATCH] musb: fix power field to hold all possible values
* Felipe Balbi m
Hi,
On Tue, Feb 23, 2010 at 03:16:44PM +0530, Ajay Kumar Gupta wrote:
MUSB can supply upto 500mA such as, AM3517 and OMAP3EVM Rev =E and thus
the 'power' field has to hold values above 255.
power on the arch code is same as bMaxPower it will be multiplied by two
on musb_core.c. See line 150 of
Felipe Balbi wrote:
Hi,
On Tue, Feb 23, 2010 at 03:16:44PM +0530, Ajay Kumar Gupta wrote:
MUSB can supply upto 500mA such as, AM3517 and OMAP3EVM Rev =E and thus
the 'power' field has to hold values above 255.
power on the arch code is same as bMaxPower it will be multiplied by two
on
Hi,
On Tue, Feb 23, 2010 at 03:27:39PM +0530, Gadiyar, Anand wrote:
power on the arch code is same as bMaxPower it will be multiplied by two
on musb_core.c. See line 150 of that file.
Meaning 500mA is set to 250 on the board-file.
Any reason we have the multiply by 2 there?
no big
Hi,
On Tue, Feb 23, 2010 at 08:01:50PM +0530, Gupta, Ajay Kumar wrote:
Board files are providing the actual mA and it is getting divided in
Arch/arm/mach-omap2/usb-musb.c. See the code snippet below,
musb_plat.clock = ick;
musb_plat.board_data = board_data;
--
