Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: javier Martin <javier.martin@vista-silicon.com>
Cc: Mike Looijmans <mike.looijmans@topic.nl>,
	alsa-devel@alsa-project.org, lars@metafoo.de, lrg@ti.com,
	w.sang@pengutronix.de
Subject: Re: [PATCH v2 2/2] ASoC: tlv320aic32x4: Add rstn gpio to platform data.
Date: Mon, 5 Nov 2012 09:15:51 +0100	[thread overview]
Message-ID: <20121105081551.GD28886@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CACKLOr0a+oUiP6gh_FNZ+cx7KkTiBef7mRWf3FO7xmRRUYUf0A@mail.gmail.com>


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

On Mon, Nov 05, 2012 at 09:14:41AM +0100, javier Martin wrote:
> On 1 November 2012 15:35, Mark Brown

> > Probably easiest to just convert over to regmap, it handles paging fine.

> this is something I'd like to do when I have some spare time. Do you
> know any example of a codec driver that uses a similar approach for
> accessing registers?

The WM2200 uses paging, and grepping for regmap will turn up a bunch of
other drivers which use it.

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

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



  reply	other threads:[~2012-11-05  8:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31 10:53 [PATCH v2 1/2] ASoC: tlv320aic32x4: Fix problem with first capture Javier Martin
2012-10-31 10:53 ` [PATCH v2 2/2] ASoC: tlv320aic32x4: Add rstn gpio to platform data Javier Martin
2012-10-31 14:40   ` Mike Looijmans
2012-11-01 14:35     ` Mark Brown
2012-11-01 15:28       ` Mike Looijmans
2012-11-02 14:40         ` Mark Brown
2012-11-05  8:14       ` javier Martin
2012-11-05  8:15         ` Mark Brown [this message]
2012-11-01 14:36 ` [PATCH v2 1/2] ASoC: tlv320aic32x4: Fix problem with first capture 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=20121105081551.GD28886@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=javier.martin@vista-silicon.com \
    --cc=lars@metafoo.de \
    --cc=lrg@ti.com \
    --cc=mike.looijmans@topic.nl \
    --cc=w.sang@pengutronix.de \
    /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