From: Jarkko Nikula <jarkko.nikula@bitmer.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: stable@linux.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>,
alsa-devel@alsa-project.org, "3.4+" <stable@kernel.org>
Subject: Re: [PATCH] ASoC: omap-mcbsp: Fix 6pin mux configuration
Date: Tue, 07 Aug 2012 15:43:56 +0300 [thread overview]
Message-ID: <50210D8C.8090303@bitmer.com> (raw)
In-Reply-To: <1344343067-27435-1-git-send-email-peter.ujfalusi@ti.com>
On 08/07/2012 03:37 PM, Peter Ujfalusi wrote:
> The check for the mux_signal callback was wrong which prevents us to
> configure the 6pin port's FSR/CLKR signal mux.
>
> Reported-by: CF Adad <cfadad@rocketmail.com>
> Cc: stable@kernel.org (3.4+)
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> ---
>
> Hi Mark,
>
> The omap-mcbsp FSR/CLKR mux configuration code seams to be broken since 3.4.
> Would it be possible to apply this patch for the 3.6 release?
>
> CC-ing stable@kernel.org since this part is broken in 3.4 and 3.5 kernels as
> well.
>
> Regards,
> Peter
>
> sound/soc/omap/mcbsp.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/sound/soc/omap/mcbsp.c b/sound/soc/omap/mcbsp.c
> index 1b08d98..5bda7c9 100644
> --- a/sound/soc/omap/mcbsp.c
> +++ b/sound/soc/omap/mcbsp.c
> @@ -766,7 +766,7 @@ int omap_mcbsp_6pin_src_mux(struct omap_mcbsp *mcbsp, u8 mux)
> {
> const char *signal, *src;
>
> - if (mcbsp->pdata->mux_signal)
> + if (!mcbsp->pdata->mux_signal)
> return -EINVAL;
>
Acked-by: Jarkko Nikula <jarkko.nikula@bitmer.com>
next prev parent reply other threads:[~2012-08-07 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 12:37 [PATCH] ASoC: omap-mcbsp: Fix 6pin mux configuration Peter Ujfalusi
2012-08-07 12:43 ` Jarkko Nikula [this message]
2012-08-07 14:04 ` Mark Brown
2012-08-07 14:24 ` Peter Ujfalusi
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=50210D8C.8090303@bitmer.com \
--to=jarkko.nikula@bitmer.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=stable@kernel.org \
--cc=stable@linux.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 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.