From: Lars-Peter Clausen <lars@metafoo.de>
To: Mark Brown <broonie@kernel.org>,
"jonsmirl@gmail.com" <jonsmirl@gmail.com>
Cc: alsa-devel mailing list <alsa-devel@alsa-project.org>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: ASoC: TI codecs and their crazy variable length registers
Date: Thu, 31 Jul 2014 09:01:09 +0200 [thread overview]
Message-ID: <53D9E9B5.4040303@metafoo.de> (raw)
In-Reply-To: <20140730231756.GE17528@sirena.org.uk>
On 07/31/2014 01:17 AM, Mark Brown wrote:
> On Wed, Jul 30, 2014 at 05:56:36PM -0400, jonsmirl@gmail.com wrote:
>
>> I'm working on a TI codec attached via I2C. Just to make things
>> interesting the registers have varying byte lengths of - 1,4,8,12,20
>> bytes. What's the best strategy for using regmap with it?
>
> I'd use the reg_read() and reg_write() callbacks to hide the registers
> that will fit in an integer, the rest of the stack can pretend they've
> got 32 bit values which should improve code reuse.[...]
The adau1701 is a driver that for example does this.
next prev parent reply other threads:[~2014-07-31 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 21:56 ASoC: TI codecs and their crazy variable length registers jonsmirl
2014-07-30 23:17 ` Mark Brown
2014-07-31 7:01 ` Lars-Peter Clausen [this message]
2014-07-31 14:06 ` jonsmirl
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=53D9E9B5.4040303@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jonsmirl@gmail.com \
--cc=lgirdwood@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.