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

2013-06-16 Thread Paul Walmsley
On Fri, 14 Jun 2013, Lokesh Vutla wrote: > On Monday 10 June 2013 12:52 PM, Paul Walmsley wrote: > > > * 3730 Beagle XM, am335xbone, CM-T3517: uart4_rx.uart4_rx mux failure > >- Cause unknown > I am able to reproduce this issue on 37xx EVM using non-dt boot (dt boot > doesn't throw this error

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

2013-06-16 Thread Paul Walmsley
On Mon, 10 Jun 2013, Lokesh Vutla wrote: > On Monday 10 June 2013 12:52 PM, Paul Walmsley wrote: > > > * 3730 Beagle XM, am335xbone, CM-T3517: uart4_rx.uart4_rx mux failure > Just booted up my BeagleBone. I didn't see any error for uart4_rx in my boot > log. > Since I don't have other boards, I wa

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

2013-06-14 Thread Lokesh Vutla
Hi Paul, On Monday 10 June 2013 12:52 PM, Paul Walmsley wrote: 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 -

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

2013-06-13 Thread Paul Walmsley
On Wed, 12 Jun 2013, Tony Lindgren wrote: > * Paul Walmsley [130610 00:27]: > > > * 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. > > D

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

2013-06-13 Thread Paul Walmsley
Hi Péter, On Tue, 11 Jun 2013, Peter Ujfalusi wrote: > I will send a patch soon to fix these. Need to test the patch(es) first. I > think they surfaced because I have enabled the audio support in > omap2plus_defconfig for OMAP4 and 5 - which require McPDM and DMIC. > Just couple of minutes, and I

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

2013-06-13 Thread Tony Lindgren
* Lokesh Vutla [130613 04:01]: > Hi Tony, > On Wednesday 12 June 2013 11:18 PM, Tony Lindgren wrote: > >* 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

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

2013-06-13 Thread Lokesh Vutla
Hi Tony, On Wednesday 12 June 2013 11:18 PM, Tony Lindgren wrote: * 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:

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

2013-06-12 Thread Tony Lindgren
* 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

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

2013-06-11 Thread Peter Ujfalusi
Hi Paul, On 06/10/2013 09:22 AM, Paul Walmsley wrote: > > 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: > > * 2430SDP, 3730 Beagle XM, 3530 Beagle, 351

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

2013-06-10 Thread Lokesh Vutla
Hi Paul, On Monday 10 June 2013 12:52 PM, Paul Walmsley wrote: 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 -

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

2013-06-10 Thread Paul Walmsley
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 * 2420N800, 2430sdp: failed to get counter_32k res