Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Robert Jarzmik <rjarzmik@free.fr>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] Change of cold reset and ac97 register	cache
Date: Thu, 17 Jan 2008 13:28:27 +0000	[thread overview]
Message-ID: <20080117132827.GA1248@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <87k5m91k93.fsf@polgara.paysbobval>

On Wed, Jan 16, 2008 at 11:24:56PM +0100, Robert Jarzmik wrote:

> The actual implementation of the wm9713 codec provides a cache of AC97
> registers. After cold reset, the cache and hardware are not in sync. When
> using wm9713 logic, oring a GPIO triggers many other GPIOS.

> The solution of this patch reads from hardware to cache upon cold reset.
> Another one would be to write the cache to hardware upon init. If decided so,
> I would gladly change my patch.

Neither option is entirely safe - something more involved like the code
in wm9713_soc_resume() would be required to bring the chip back safely.
Writing the current cache values is unsafe due to ordering requirements
and in any case the information required to configure the PLL can't be
recovered from the cache alone.  Reading the values currently set in the
chip for the cache is safer will leave the chip without basic
initialisation and the driver out of sync with the state of the chip.

Could you outline why you need to reset the codec?  I'd like to
understand the use case here.

  reply	other threads:[~2008-01-17 13:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 22:24 [PATCH] Change of cold reset and ac97 register cache Robert Jarzmik
2008-01-17 13:28 ` Mark Brown [this message]
     [not found]   ` <87d4s0kurn.fsf@polgara.paysbobval>
     [not found]     ` <20080118115122.GA22933@rakim.wolfsonmicro.main>
2008-01-18 19:50       ` Robert Jarzmik
2008-01-19 11:49         ` 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=20080117132827.GA1248@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=rjarzmik@free.fr \
    /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