From: Anand Gadiyar <gadiyar@ti.com>
To: Govindraj <govindraj.ti@gmail.com>,
Tarun Kanti DebBarma <tarun.kanti@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>
Subject: RE: Linux-next as of 20110222 broken on OMAP4
Date: Tue, 22 Feb 2011 15:58:05 +0530 [thread overview]
Message-ID: <f2bd6483c7999508b05c2d00a0e45c3b@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikD6ntKWBXRtgPcpkApKkZrnvG8qK1qYEDrdob5@mail.gmail.com>
Govindraj wrote:
> On Tue, Feb 22, 2011 at 3:19 PM, Anand Gadiyar <gadiyar@ti.com> wrote:
> > Looks like linux-next as of today is broken on at least OMAP4.
> >
> > Turning on earlyprintk, I get a crash in omap_init_mcspi. Disabling
> > CONFIG_SPI_OMAP24XX gets me as far as the following lines from my
> > bootup log, but I haven't attempted to debug further.
>
>
> SPI fix is available but yet be merged its discussed in this thread:
>
> http://dchs.spinics.net/lists/linux-omap/msg46446.html
And the other hack I needed to fix the failure when I disable SPI
is this one (thanks Tarun).
It's just a hack - I hope a better fix will be along shortly.
- Anand
Index: linux-omap-usb/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
===================================================================
--- linux-omap-usb.orig/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
+++ linux-omap-usb/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
@@ -5068,7 +5068,7 @@ static __initdata struct omap_hwmod *oma
&omap44xx_spinlock_hwmod,
/* timer class */
- &omap44xx_timer1_hwmod,
+ /* &omap44xx_timer1_hwmod, */
&omap44xx_timer2_hwmod,
&omap44xx_timer3_hwmod,
&omap44xx_timer4_hwmod,
next prev parent reply other threads:[~2011-02-22 10:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 9:49 Linux-next as of 20110222 broken on OMAP4 Anand Gadiyar
2011-02-22 10:24 ` Govindraj
2011-02-22 10:28 ` Anand Gadiyar [this message]
2011-02-22 12:51 ` Cousson, Benoit
2011-02-22 13:13 ` Santosh Shilimkar
2011-02-22 19:13 ` Tony Lindgren
2011-02-23 4:50 ` DebBarma, Tarun Kanti
2011-02-23 12:07 ` Kishore Kadiyala
2011-02-23 12:20 ` DebBarma, Tarun Kanti
2011-02-23 12:52 ` Kishore Kadiyala
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f2bd6483c7999508b05c2d00a0e45c3b@mail.gmail.com \
--to=gadiyar@ti.com \
--cc=govindraj.ti@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=tarun.kanti@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.