Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Pascal Huerst <pascal.huerst@gmail.com>
Cc: alsa-devel@alsa-project.org, lars@metafoo.de, tiwai@suse.de,
	lgirdwood@gmail.com, zonque@gmail.com,
	ckeepax@opensource.wolfsonmicro.com
Subject: Re: [PATCH] ASoC: snd_soc_tas5086: Reinit register values on probe
Date: Wed, 25 Mar 2015 09:20:29 -0700	[thread overview]
Message-ID: <20150325162029.GF3572@sirena.org.uk> (raw)
In-Reply-To: <1427297379-17736-1-git-send-email-pascal.huerst@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1038 bytes --]

On Wed, Mar 25, 2015 at 04:29:39PM +0100, Pascal Huerst wrote:

> If the machine driver has been un/reloaded, the register values of
> the codec driver have to be reinitialized in order to run properly.

Hrm.  This isn't something that I'd expect to be required - I'd expect
that as part of the machine driver teardown to put the hardware into a
reasonable default state so that things come back as normal.  Can you be
a bit more specific about the problem that you are seeing?  We probably
shouldn't need the existing reset that's in the ASoC level probe either.

I do think a version of this is useful regardless of the above...

>  	tas5086_reset(priv);
> +	regcache_mark_dirty(priv->regmap);

Since the device has hardware reset support we really ought to be able
to do the register cache resync only if the reset GPIO is missing.  How
about putting your code into the reset function and doing it in the
case where the reset GPIO is missing?  That way anything that thinks
it's resetting the device will get the benefit of your code.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2015-03-25 16:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25 15:29 [PATCH] ASoC: snd_soc_tas5086: Reinit register values on probe Pascal Huerst
2015-03-25 16:20 ` Mark Brown [this message]
2015-03-25 17:29   ` Pascal Huerst
2015-03-25 17:48     ` Mark Brown
2015-03-26 12:17       ` Pascal Huerst

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=20150325162029.GF3572@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=pascal.huerst@gmail.com \
    --cc=tiwai@suse.de \
    --cc=zonque@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