From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Sergey Kiselev <skiselev@gmail.com>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
alsa-devel@alsa-project.org
Subject: Re: ASoC: PATCH: wm8731 - reinitialize regmap cache after hardware reset
Date: Tue, 2 Jun 2015 12:55:43 +0100 [thread overview]
Message-ID: <20150602115543.GF3449@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CA+abuVebbr9Cif_SfB+JcNhUOMV70fdWa-Q-nk+gFv9H5MRtgQ@mail.gmail.com>
On Thu, May 28, 2015 at 09:34:09AM -0700, Sergey Kiselev wrote:
> Hi,
>
> I am working on a machine driver that uses wm8731 codec and I've
> noticed that it will not work after rmmod/modprobe of that machine
> driver. The issue is that wm8731_probe() resets the hardware, but it
> doesn't reinitialize the regmap cache to the default values.
>
> The patch below fixes this issue.
>
> I also skimmed through other codecs, and some of them might have
> similar issue (wm8510.c, wm8711.c, wm8750.c, wm8753.c, wm8940.c,
> wm8960.c, wm8971.c, wm8974.c, wm8988.c, wm8990.c)
>
> Another way to avoid this issue might be resetting the codec in the
> *_spi_probe()/*_i2c_probe(), so that it only gets reset once when
> codec is loading.
>
> Thanks in advance for any comments/suggestions on the patch.
>
> Thanks,
> Sergey
>
> Signed-off-by: Sergey Kiselev <skiselev@gmail.com>
>
In addition to the comments from Mark and Liam, if you could CC
patches@opensource.wolfsonmicro.com when submitting patches to
the Wolfson stuff, ensures we will see them going through, it is
easy to miss stuff on the generic lists.
Thanks,
Charles
prev parent reply other threads:[~2015-06-02 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 16:34 ASoC: PATCH: wm8731 - reinitialize regmap cache after hardware reset Sergey Kiselev
2015-05-28 16:52 ` Liam Girdwood
2015-05-28 19:26 ` Mark Brown
[not found] ` <CA+abuVeO4=au_X0Z_MjPsq40b1fHbjezKRy_fTOgQ=SzmaPK5Q@mail.gmail.com>
[not found] ` <20150528145548.fa5a0f2d78c0bb2549088fc2@intel.com>
2015-05-29 9:32 ` Mark Brown
2015-06-02 11:55 ` Charles Keepax [this message]
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=20150602115543.GF3449@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=skiselev@gmail.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;
as well as URLs for NNTP newsgroup(s).