All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.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: Tue, 11 Jun 2013 09:47:36 +0200	[thread overview]
Message-ID: <51B6D618.30809@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306100716560.4604@utopia.booyaka.com>

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, 3517EVM, CM-T3517: {dmic,mcpdm} lookup failure
>   - Cause unknown
>   - These IP blocks don't exist on OMAP3xxx/AM35xx chips

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'll have the fix.

-- 
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: peter.ujfalusi@ti.com (Peter Ujfalusi)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP v3.10-rc regressions that no one's fixed
Date: Tue, 11 Jun 2013 09:47:36 +0200	[thread overview]
Message-ID: <51B6D618.30809@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306100716560.4604@utopia.booyaka.com>

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, 3517EVM, CM-T3517: {dmic,mcpdm} lookup failure
>   - Cause unknown
>   - These IP blocks don't exist on OMAP3xxx/AM35xx chips

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'll have the fix.

-- 
P?ter

  parent reply	other threads:[~2013-06-11  7: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 [this message]
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
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=51B6D618.30809@ti.com \
    --to=peter.ujfalusi@ti.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.