Subject: OMAP v3.10-rc regressions that no one's fixed

From: [email-masked] (Lokesh Vutla)
Date: Thu, 13 Jun 2013 16:25:16 +0530

Hi Tony,
On Wednesday 12 June 2013 11:18 PM, Tony Lindgren wrote:
> * Paul Walmsley <[email-masked]> [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?
Yes by commenting out omap3_evm_display_init() fixes the booting.
>
> 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.
As per your suggestion I have sent a patch for marking 
omap3_evm_display_init()
with CONFIG_BROKEN.

Thanks,
Lokesh
>
> Regards,
>
> Tony
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>