Hi,
Sorry for the delay in responding, mostly in read-only mode this
week :)
* Felipe Balbi [101227 09:17]:
> >
> >What was the problem you saw with N810 which caused the need for
> >commit fc8c2f1dba400e9a0d1d82756e0e2f52dfe2f4b6, quoted below ?
Heh found it after some debugging, we need to ca
On Wed, Dec 01, 2010 at 07:32:11PM +0530, Govindraj.R wrote:
> McSPI runtime conversion.
> Changes involves:
> 1) remove clock framework apis to use runtime framework apis.
> 2) context restore from runtime resume which is a callback for get_sync.
> 3) Remove SYSCONFIG(sysc) register handling
>
On Wed, Dec 01, 2010 at 07:32:00PM +0530, Govindraj.R wrote:
> From: Charulatha V
>
> Cleans up all base address definitions for omap_mcspi
> and adapts the device registration and driver to hwmod framework.
> Changes involves:
> 1) Removing all base address macro defines.
> 2) Using omap-device
On Wed, Dec 01, 2010 at 07:31:38PM +0530, Govindraj.R wrote:
> From: Benoit Cousson
>
> Update omap4 hwmod file with McSPI info.
Ditto here. A lot of this data is identical to the OMAP2 data from
patches 1 & 2. It looks like this should be shared.
g.
>
> Signed-off-by: Benoit Cousson
> Sig
On Wed, Dec 01, 2010 at 07:31:22PM +0530, Govindraj.R wrote:
> From: Charulatha V
>
> Update the 2430 hwmod data file with McSPI info.
>
> Signed-off-by: Charulatha V
> Signed-off-by: Govindraj.R
Hmmm; this patch is virtually identical to the first patch in this
series which adds 2420 hwmod s
On Fri, 3 Dec 2010 23:42:45 +0530, 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.
>
I could have sworn I tried applying this befo
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, th
On Thu, Dec 30, 2010 at 10:00:46AM -0500, Ben Gamari wrote:
On Thu, 30 Dec 2010 14:27:38 +0200, 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 al
On Thu, Dec 30, 2010 at 05:24:05PM +0200, Anca Emanuel wrote:
On Thu, Dec 30, 2010 at 5:00 PM, Ben Gamari wrote:
On Thu, 30 Dec 2010 14:27:38 +0200, 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
On Thu, Dec 30, 2010 at 5:00 PM, Ben Gamari wrote:
> On Thu, 30 Dec 2010 14:27:38 +0200, 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?
You can ask Greg to make an pull r
On Thu, 30 Dec 2010 14:27:38 +0200, 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?
- Ben
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body o
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 pa
On Thu, Dec 30, 2010 at 02:44:40AM -0500, Ben Gamari wrote:
On Mon, 27 Dec 2010 11:20:38 +0200, Felipe Balbi 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 mu
On Thu, Dec 30, 2010 at 12:18:04PM +, Mark Brown wrote:
On Wed, Dec 29, 2010 at 02:28:08PM +0200, Felipe Balbi wrote:
I believe you meant something like below, I'll get back to this in a
little while. Have lots to test:
Yes, that looks like what I'd expect.
Good, I'll clean the patches
On Wed, Dec 29, 2010 at 02:28:08PM +0200, Felipe Balbi wrote:
> I believe you meant something like below, I'll get back to this in a
> little while. Have lots to test:
Yes, that looks like what I'd expect.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a m
From: Anand Sawant
This patch will expose the following voltage controller registers
as part of voltage layer debugfs.
1. PRM_VC_BYPASS_VAL
2. PRM_VC_CMD_VAL - for all VDDs
This patch will help in debugging voltage scaling issues.
Tested on Zoom3 & OMAP4430 SDP.
Patch rebased to latest Kevin's
16 matches
Mail list logo
