From: jhnikula@gmail.com (Jarkko Nikula)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: omap-mcbsp: Remove restrictive checks for cpu type
Date: Wed, 11 May 2011 18:38:58 +0300 [thread overview]
Message-ID: <20110511183858.4ada5071.jhnikula@gmail.com> (raw)
In-Reply-To: <1305122135-27938-1-git-send-email-premi@ti.com>
On Wed, 11 May 2011 19:25:35 +0530
Sanjeev Premi <premi@ti.com> 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.
>
> Signed-off-by: Sanjeev Premi <premi@ti.com>
> cc: Mark Brown <broonie@opensource.wolfsonmicro.com>
> cc: Liam Girdwood <lrg@ti.com>
> cc: Jarkko Nikula <jhnikula@gmail.com>
> ---
Acked-by: Jarkko Nikula <jhnikula@gmail.com>
next prev parent reply other threads:[~2011-05-11 15:38 UTC|newest]
Thread overview: 5+ 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
2011-05-11 14:44 ` [alsa-devel] " Peter Ujfalusi
2011-05-11 15:38 ` Jarkko Nikula [this message]
2011-05-13 12:13 ` 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=20110511183858.4ada5071.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).