From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "jonsmirl@gmail.com" <jonsmirl@gmail.com>
Cc: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>,
alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: soc-core: Remove display_register() callback
Date: Wed, 2 Feb 2011 14:51:15 +0000 [thread overview]
Message-ID: <20110202145115.GR12743@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTing5zryWWt4HZHGUd15-6mrxpnRwA8EEiE8DGem@mail.gmail.com>
On Wed, Feb 02, 2011 at 09:50:40AM -0500, jonsmirl@gmail.com wrote:
> TI Codec devices have two problems:
> 1) large registers - up to 128 bits
> 2) sparse register maps - big gaps between valid register addresses.
The sparse register maps are already very well handled, they're quite
widespread.
next prev parent reply other threads:[~2011-02-02 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 10:20 [PATCH] ASoC: soc-core: Remove display_register() callback Dimitris Papastamos
2011-02-02 10:23 ` Mark Brown
2011-02-02 14:50 ` jonsmirl
2011-02-02 14:51 ` Mark Brown [this message]
2011-02-02 14:54 ` Dimitris Papastamos
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=20110202145115.GR12743@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dp@opensource.wolfsonmicro.com \
--cc=jonsmirl@gmail.com \
--cc=lrg@slimlogic.co.uk \
--cc=patches@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).