From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Pantelis Antoniou <panto@antoniou-consulting.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] Don't clobber access methods when !regmap
Date: Thu, 06 Sep 2012 17:01:14 +0300 [thread overview]
Message-ID: <5048ACAA.3000505@ti.com> (raw)
In-Reply-To: <D96C7824-5EBC-4418-B016-DCE395A720D7@antoniou-consulting.com>
Hi,
On 09/05/2012 07:43 PM, Pantelis Antoniou wrote:
> The driver in question (twl4030.c) does not call snd_soc_codec_set_cache_io().
> However the snd-soc core does call it in sound/soc/soc-core.c in soc_probe_codec.
>
> I do see that there's a commit 98d3088e534a2a61f6690b5426909b0c3b57a785 that is
> fixing it in a different manner.
I also noticed this (with 3.6-rc1 I think).
The commit you mention does fix it so we do not have issue anymore.
I sent two patches related to this:
http://mailman.alsa-project.org/pipermail/alsa-devel/2012-August/053864.html
http://mailman.alsa-project.org/pipermail/alsa-devel/2012-August/053876.html
Mark took a different route which gives us the commit you mentioned:
http://mailman.alsa-project.org/pipermail/alsa-devel/2012-August/053889.html
Regards,
Péter
next prev parent reply other threads:[~2012-09-06 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 13:45 [PATCH] Don't clobber access methods when !regmap Pantelis Antoniou
2012-09-05 16:36 ` Lars-Peter Clausen
2012-09-05 16:43 ` Pantelis Antoniou
2012-09-06 14:01 ` Peter Ujfalusi [this message]
2012-09-06 14:02 ` Pantelis Antoniou
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=5048ACAA.3000505@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=panto@antoniou-consulting.com \
--cc=patches@opensource.wolfsonmicro.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