RE: [PATCH 1/3 v5] usb: musb: Add support for ti81xx platform

Hi, > > On Wed, Feb 08, 2012 at 11:46:00AM +0530, Shubhrajyoti wrote: > > > On Wednesday 08 February 2012 09:56 AM, Ajay Kumar Gupta wrote: > > > > +static int dsps_musb_init(struct musb *musb) { > > > > + struct device *dev = musb->controller; > > > > + struct musb_hdrc_platform_data *

Re: [PATCH 2/3 v5] arm: omap: am335x: enable phy controls

Hi, On Mon, Feb 13, 2012 at 04:26:19AM +, Gupta, Ajay Kumar wrote: > Hi, > > * Ajay Kumar Gupta [120207 19:55]: > > > Switch on the phy for am335x. > > > > > > Signed-off-by: Ajay Kumar Gupta > > > --- > > > arch/arm/mach-omap2/omap_phy_internal.c | 21 ++--- > > > 1 files

[PATCH v2 2/2] ARM: OMAP: sram: Add am33xx SRAM support (minimal)

From: Vaibhav Bedia Update SRAM start & size for am33xx SoC's. Note: cpu_is_34xx() is true for am33xx also. Doing cpu_is_am33xx() check after cpu_is_34xx() will not achieve what we want due to the above reason. Hence cpu_is_am33xx() is done before cpu_is_34xx() Signed-off-by: Vaibhav Bedia Sig

[PATCH v2 1/2] ARM: OMAP2+: id: Add am33xx SoC type detection

Determine SoC type, i.e. whether GP or HS Note: cpu_is_34xx() is true for am33xx also. Doing cpu_is_am33xx() check after cpu_is_34xx() will not achieve what we want due to the above reason. Hence cpu_is_am33xx() is done before cpu_is_34xx() Signed-off-by: Afzal Mohammed Signed-off-by: Vaibhav Hi

[PATCH v2 0/2] AM335X: SoC type detection & SRAM support

Hi, These changes does, 1. detect SoC type (i.e. GP or not) 2. add minimal SRAM support for AM335X devices These are required to get AM335X boot to prompt (but not sufficient) v2: Use OMAP naming conventions for subject Regards Afzal Afzal Mohammed (1): ARM: OMAP2+: id: Add am33xx SoC type

Re: OMAP34xx

On Monday 13 February 2012 12:42 AM, Paul Walmsley wrote: > Hi > > On Sun, 12 Feb 2012, Russell King - ARM Linux wrote: > >> The other allnoconfig issue is: >> >> arch/arm/mach-omap2/built-in.o:(.data+0xa3d0): undefined reference to >> `omap_i2c_reset' >> >> which looks like hwmod can't cope with

Re: [PATCH v9 00/25] gpio/omap: driver cleanup and fixes

On Sat, Feb 11, 2012 at 1:25 AM, Kevin Hilman wrote: > Tony Lindgren writes: > > [...] > >> ..but are there also some patches in your series that should also be >> applied separately as fixes for the -rc cycle? > > IMO, there aren't any things in this series that fall into the > regression catego

RE: [PATCH 2/3 v5] arm: omap: am335x: enable phy controls

Hi, > * Ajay Kumar Gupta [120207 19:55]: > > Switch on the phy for am335x. > > > > Signed-off-by: Ajay Kumar Gupta > > --- > > arch/arm/mach-omap2/omap_phy_internal.c | 21 ++--- > > 1 files changed, 14 insertions(+), 7 deletions(-) > > > > diff --git a/arch/arm/mach-omap2/omap

Re: OMAP34xx

Hi On Sun, 12 Feb 2012, Russell King - ARM Linux wrote: > The other allnoconfig issue is: > > arch/arm/mach-omap2/built-in.o:(.data+0xa3d0): undefined reference to > `omap_i2c_reset' > > which looks like hwmod can't cope with the I2C_OMAP being disabled. > > I don't propose these are fixed fo

Re: Possible circular locking dependency (3.3-rc2)

On środa, 8 lutego 2012 o 13:41:48 Felipe Balbi wrote: > Hi guys, > > I have just triggered the folllowing: > > [ 84.860321] == > [ 84.860321] [ INFO: possible circular locking dependency detected ] > [ 84.860321] 3.3.0-rc2-00026-ge4e8a39

Re: OMAP34xx

Here's another issue which kautobuildv2 just found, as I've now added randconfig to the suite of OMAP4430 SDP builds. Obviously, as it's using a different configuration each time, it's going to find different issues on each run. For this, the seed config has the following extra lines compared wit

Re: OMAP34xx

Another issue (through lower priority) is this: twl-common.c:(.init.text+0x2e48): undefined reference to `omap34xx_vddmpu_volt_data' twl-common.c:(.init.text+0x2e4c): undefined reference to `omap34xx_vddcore_volt_data' twl-common.c:(.init.text+0x2e5c): undefined reference to `omap36xx_vddmpu_vo