Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Opensource [Adam Thomson]" <Adam.Thomson.Opensource@diasemi.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] ASoC: da732x: Mark DC offset control registers volatile
Date: Mon, 24 Feb 2014 21:42:30 +0900	[thread overview]
Message-ID: <20140224124230.GF25940@sirena.org.uk> (raw)
In-Reply-To: <2E89032DDAA8B9408CB92943514A03376BAD3FC8@SW-EX-MBX01.diasemi.com>

[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]

On Mon, Feb 24, 2014 at 11:31:25AM +0000, Opensource [Adam Thomson] wrote:
> On Mon, 24 Feb 2014 03:01:37 +0000, Mark Brown wrote:

> > but since the registers are marked as volatile and there is a register

> Guessing that should read 'not marked as volatile'.

Yes.

> Having looked over the driver again, can you include the following
> registers as well: 

> DA732X_REG_HPL
> DA732X_REG_HPR

I did notice those.  However they are a bit more fun since they have
some non-volatile fields in them which are also used for control.  I
*suspect* that a lot of the time it'll be possible to get away with just
caching the first read but it needs further study - often with these
things the basic offset is constant in a given system so the sign may
well be right all the time.  That's just a guess, though, and may not
actually hold at which point a bit more attention might be needed.

> Also, if we're doing this then you can move to using snd_soc_read()
> instead of hw_read(), I guess.

Indeed, in fact it was while doing an audit of drivers to kill off
direct users of hw_read() that I noticed what was happening here.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-02-24 12:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24  3:00 [PATCH] ASoC: da732x: Mark DC offset control registers volatile Mark Brown
2014-02-24 11:31 ` Opensource [Adam Thomson]
2014-02-24 12:42   ` Mark Brown [this message]
2014-02-24 13:57     ` Opensource [Adam Thomson]
2014-02-25  1:21       ` Mark Brown
2014-02-25 16:13         ` Opensource [Adam Thomson]
2014-02-25 23:54           ` Mark Brown
2014-02-26  9:39             ` Opensource [Adam Thomson]

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=20140224124230.GF25940@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Adam.Thomson.Opensource@diasemi.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lgirdwood@gmail.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=stable@vger.kernel.org \
    /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