From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dong Aisheng <b29396@freescale.com>
Cc: alsa-devel@alsa-project.org, lrg@ti.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/1] ASoC: sgtl5000: enable VAG_POWER for LINE_IN
Date: Tue, 31 Jul 2012 16:40:26 +0100 [thread overview]
Message-ID: <20120731154026.GG4468@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1343387922-25227-1-git-send-email-b29396@freescale.com>
On Fri, Jul 27, 2012 at 07:18:42PM +0800, Dong Aisheng wrote:
> From: Dong Aisheng <dong.aisheng@linaro.org>
>
> LINE_IN also needs VAG_POWER on or we may hear noise when directly
> route LINE_IN to Headphone Mux.
> Tested on imx28evk.
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ASoC: sgtl5000: enable VAG_POWER for LINE_IN
Date: Tue, 31 Jul 2012 16:40:26 +0100 [thread overview]
Message-ID: <20120731154026.GG4468@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1343387922-25227-1-git-send-email-b29396@freescale.com>
On Fri, Jul 27, 2012 at 07:18:42PM +0800, Dong Aisheng wrote:
> From: Dong Aisheng <dong.aisheng@linaro.org>
>
> LINE_IN also needs VAG_POWER on or we may hear noise when directly
> route LINE_IN to Headphone Mux.
> Tested on imx28evk.
Applied, thanks.
next prev parent reply other threads:[~2012-07-31 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 11:18 [PATCH 1/1] ASoC: sgtl5000: enable VAG_POWER for LINE_IN Dong Aisheng
2012-07-27 11:18 ` Dong Aisheng
2012-07-28 14:39 ` Shawn Guo
2012-07-28 14:39 ` [alsa-devel] " Shawn Guo
2012-07-31 15:46 ` Mark Brown
2012-07-31 15:46 ` [alsa-devel] " Mark Brown
2012-08-01 2:46 ` Dong Aisheng
2012-08-01 2:46 ` Dong Aisheng
2012-07-31 15:40 ` Mark Brown [this message]
2012-07-31 15:40 ` Mark Brown
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=20120731154026.GG4468@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=b29396@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lrg@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 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.