From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Sanjeev Premi <premi@ti.com>
Cc: alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
Liam Girdwood <lrg@ti.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: omap-mcbsp: Remove restrictive checks for cpu type
Date: Wed, 11 May 2011 15:57:08 +0200 [thread overview]
Message-ID: <20110511135708.GE12469@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1305122135-27938-1-git-send-email-premi@ti.com>
On Wed, May 11, 2011 at 07:25:35PM +0530, Sanjeev Premi wrote:
> Current checks for cpu type were too restrictive leading
> to failures for other silicons in same family.
>
> The problem was found while testing audio playback on
> AM37x and AM35x processors. But should exist on OMAP36xx
> as well.
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
next prev parent reply other threads:[~2011-05-11 13:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 13:55 [PATCH] ASoC: omap-mcbsp: Remove restrictive checks for cpu type Sanjeev Premi
2011-05-11 13:57 ` Mark Brown [this message]
2011-05-11 14:44 ` Peter Ujfalusi
2011-05-11 15:38 ` Jarkko Nikula
2011-05-11 18:16 ` [alsa-devel] " Steve Calfee
2011-05-11 19:19 ` Premi, Sanjeev
2011-05-11 21:31 ` beagleboardxm 2.6.39rc4 mcbsp problems Steve Calfee
2011-05-12 6:25 ` Jarkko Nikula
2011-05-12 11:01 ` Peter Ujfalusi
2011-05-12 18:43 ` Steve Calfee
2011-05-13 5:59 ` Peter Ujfalusi
2011-05-14 2:47 ` Steve Calfee
2011-05-16 8:54 ` Peter Ujfalusi
2011-05-16 18:07 ` Steve Calfee
2011-05-17 6:37 ` Jarkko Nikula
2011-05-19 1:06 ` Steve Calfee
2011-05-20 0:58 ` Steve Calfee
2011-05-20 6:29 ` Jarkko Nikula
2011-05-20 7:03 ` Peter Ujfalusi
2011-05-21 0:55 ` Steve Calfee
2011-05-17 10:42 ` Peter Ujfalusi
2011-05-19 0:30 ` Steve Calfee
2011-05-19 11:28 ` Peter Ujfalusi
2011-05-19 23:58 ` Steve Calfee
2011-05-20 6:56 ` Peter Ujfalusi
2011-05-13 12:13 ` [PATCH] ASoC: omap-mcbsp: Remove restrictive checks for cpu type Liam Girdwood
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=20110511135708.GE12469@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=premi@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).