All of lore.kernel.org
 help / color / mirror / Atom feed
From: Axel Lin <axel.lin@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Liam Girdwood <lrg@ti.com>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	alsa-devel@alsa-project.org
Subject: ASoC: snd_soc_codec_set_cache_io does not set codec->hw_write callback now
Date: Tue, 04 Oct 2011 17:24:32 +0800	[thread overview]
Message-ID: <1317720272.2536.2.camel@phoenix> (raw)

Hi,
I just found that after commit be3ea3b9e
"SoC: Use new register map API for ASoC generic physical I/O",
snd_soc_codec_set_cache_io does not set codec->hw_write any more.

It is still used in some drivers. e.g.
In wm8988_resume, we call codec->hw_write(codec->control_data, data, 2);

For the drivers that is using snd_soc_codec_set_cache_io now,
where is the place to set codec->hw_write callback now? 

Regards,
Axel

WARNING: multiple messages have this Message-ID (diff)
From: Axel Lin <axel.lin@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Liam Girdwood <lrg@ti.com>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	alsa-devel@alsa-project.org
Subject: ASoC: snd_soc_codec_set_cache_io does not set codec->hw_write  callback now
Date: Tue, 04 Oct 2011 17:24:32 +0800	[thread overview]
Message-ID: <1317720272.2536.2.camel@phoenix> (raw)

Hi,
I just found that after commit be3ea3b9e
"SoC: Use new register map API for ASoC generic physical I/O",
snd_soc_codec_set_cache_io does not set codec->hw_write any more.

It is still used in some drivers. e.g.
In wm8988_resume, we call codec->hw_write(codec->control_data, data, 2);

For the drivers that is using snd_soc_codec_set_cache_io now,
where is the place to set codec->hw_write callback now? 

Regards,
Axel


             reply	other threads:[~2011-10-04  9:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04  9:24 Axel Lin [this message]
2011-10-04  9:24 ` ASoC: snd_soc_codec_set_cache_io does not set codec->hw_write callback now Axel Lin
2011-10-04  9:51 ` Mark Brown
2011-10-04  9:51   ` 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=1317720272.2536.2.camel@phoenix \
    --to=axel.lin@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.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.