From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: OMAP v3.10-rc regressions that no one's fixed
Date: Wed, 12 Jun 2013 10:48:42 -0700 [thread overview]
Message-ID: <20130612174842.GQ8164@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306100716560.4604@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [130610 00:27]:
>
> Hi folks -- particularly TIers working on mainline,
>
> There are several regressions that started with v3.10-rc that no one's
> fixed for over a month. Some of them should be quite easy:
>
> * 37xx EVM: boot fails
> - as of v3.10-rc1
> - Cause unknown
This one is probably because of broken GPIO numbering in
the board file that uses hardcoded GPIOs for what are probably
twl GPIOs.
Does commenting out omap3_evm_display_init() in the board file
fix the booting for you?
If so, we should probably mark omap3_evm_display_init() with
CONFIG_BROKEN for now rather than add more late init callback
functions for the twl code.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP v3.10-rc regressions that no one's fixed
Date: Wed, 12 Jun 2013 10:48:42 -0700 [thread overview]
Message-ID: <20130612174842.GQ8164@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306100716560.4604@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [130610 00:27]:
>
> Hi folks -- particularly TIers working on mainline,
>
> There are several regressions that started with v3.10-rc that no one's
> fixed for over a month. Some of them should be quite easy:
>
> * 37xx EVM: boot fails
> - as of v3.10-rc1
> - Cause unknown
This one is probably because of broken GPIO numbering in
the board file that uses hardcoded GPIOs for what are probably
twl GPIOs.
Does commenting out omap3_evm_display_init() in the board file
fix the booting for you?
If so, we should probably mark omap3_evm_display_init() with
CONFIG_BROKEN for now rather than add more late init callback
functions for the twl code.
Regards,
Tony
next prev parent reply other threads:[~2013-06-12 17:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 7:22 OMAP v3.10-rc regressions that no one's fixed Paul Walmsley
2013-06-10 7:22 ` Paul Walmsley
2013-06-10 13:13 ` Lokesh Vutla
2013-06-10 13:13 ` Lokesh Vutla
2013-06-17 4:38 ` Paul Walmsley
2013-06-17 4:38 ` Paul Walmsley
2013-06-11 7:47 ` Peter Ujfalusi
2013-06-11 7:47 ` Peter Ujfalusi
2013-06-14 2:47 ` Paul Walmsley
2013-06-14 2:47 ` Paul Walmsley
2013-06-12 17:48 ` Tony Lindgren [this message]
2013-06-12 17:48 ` Tony Lindgren
2013-06-13 10:55 ` Lokesh Vutla
2013-06-13 10:55 ` Lokesh Vutla
2013-06-13 11:08 ` Tony Lindgren
2013-06-13 11:08 ` Tony Lindgren
2013-06-14 2:57 ` Paul Walmsley
2013-06-14 2:57 ` Paul Walmsley
2013-06-14 12:38 ` Lokesh Vutla
2013-06-14 12:38 ` Lokesh Vutla
2013-06-17 4:41 ` Paul Walmsley
2013-06-17 4:41 ` Paul Walmsley
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=20130612174842.GQ8164@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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.