Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bard Liao <bardliao@realtek.com>
To: broonie@kernel.org, lgirdwood@gmail.com
Cc: oder_chiou@realtek.com, alsa-devel@alsa-project.org,
	lars@metafoo.de, zhengxing@rock-chips.com, yang.a.fang@intel.com,
	koro.chen@mediatek.com, john.lin@realtek.com,
	Bard Liao <bardliao@realtek.com>,
	flove@realtek.com
Subject: [PATCH 2/2] ASoC: Intel: rt5645_set_jack_detect is changed
Date: Mon, 20 Apr 2015 10:37:22 +0800	[thread overview]
Message-ID: <1429497442-13021-2-git-send-email-bardliao@realtek.com> (raw)
In-Reply-To: <1429497442-13021-1-git-send-email-bardliao@realtek.com>

rt5645_set_jack_detect is changed, so we need to modify the code
which is using rt5645_set_jack_detect.

Signed-off-by: Bard Liao <bardliao@realtek.com>
---
 sound/soc/intel/cht_bsw_rt5645.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sound/soc/intel/cht_bsw_rt5645.c b/sound/soc/intel/cht_bsw_rt5645.c
index bd29617..3d0b549 100644
--- a/sound/soc/intel/cht_bsw_rt5645.c
+++ b/sound/soc/intel/cht_bsw_rt5645.c
@@ -185,7 +185,7 @@ static int cht_codec_init(struct snd_soc_pcm_runtime *runtime)
 		return ret;
 	}
 
-	rt5645_set_jack_detect(codec, &ctx->hp_jack, &ctx->mic_jack);
+	rt5645_set_jack_detect(codec, &ctx->hp_jack, &ctx->mic_jack, NULL);
 
 	return ret;
 }
-- 
1.8.1.1.439.g50a6b54

  reply	other threads:[~2015-04-20  2:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20  2:37 [PATCH 1/2] ASoC: rt5645: Adds push button support for rt5650 Bard Liao
2015-04-20  2:37 ` Bard Liao [this message]
2015-04-20 20:57   ` [PATCH 2/2] ASoC: Intel: rt5645_set_jack_detect is changed Mark Brown
2015-04-20 20:41 ` [PATCH 1/2] ASoC: rt5645: Adds push button support for rt5650 Mark Brown
2015-04-21  2:08   ` Bard Liao
2015-04-21 10:48     ` Mark Brown
2015-04-21 11:41       ` Bard Liao
2015-04-22 11:04         ` 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=1429497442-13021-2-git-send-email-bardliao@realtek.com \
    --to=bardliao@realtek.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=flove@realtek.com \
    --cc=john.lin@realtek.com \
    --cc=koro.chen@mediatek.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=oder_chiou@realtek.com \
    --cc=yang.a.fang@intel.com \
    --cc=zhengxing@rock-chips.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