From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: OMAP v3.10-rc regressions that no one's fixed Date: Wed, 12 Jun 2013 10:48:42 -0700 Message-ID: <20130612174842.GQ8164@atomide.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:21523 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754906Ab3FLRsp (ORCPT ); Wed, 12 Jun 2013 13:48:45 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Paul Walmsley Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org * Paul Walmsley [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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Wed, 12 Jun 2013 10:48:42 -0700 Subject: OMAP v3.10-rc regressions that no one's fixed In-Reply-To: References: Message-ID: <20130612174842.GQ8164@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Paul Walmsley [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