From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Cc: Peter Hsiang <Peter.Hsiang@maxim-ic.com>,
alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
patches@opensource.wolfsonmicro.com,
Timur Tabi <timur@freescale.com>
Subject: Re: [PATCH v2 1/3] ASoC: soc-cache: Add support for default readable()/volatile() functions
Date: Thu, 13 Jan 2011 13:31:12 +0000 [thread overview]
Message-ID: <1294925472.3453.3.camel@odin> (raw)
In-Reply-To: <1294921238-11859-1-git-send-email-dp@opensource.wolfsonmicro.com>
On Thu, 2011-01-13 at 12:20 +0000, Dimitris Papastamos wrote:
> For common scenarios, device drivers can provide a table of all the
> registers that are at least either readable/writable/volatile. The idea
> is that if a register lookup fails, all of its read/write/vol members
> will be zero and will be treated as default. This also reduces the
> size of the register access array.
>
> Signed-off-by: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
I think we may be getting to the point where we should probably look
into making this register cache functionality available to other non
ASoC I2C and SPI based drivers.
Thanks
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2011-01-13 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 12:20 [PATCH v2 1/3] ASoC: soc-cache: Add support for default readable()/volatile() functions Dimitris Papastamos
2011-01-13 12:20 ` [PATCH v2 2/3] ASoC: Update users of readable_register()/volatile_register() Dimitris Papastamos
2011-01-13 12:20 ` [PATCH v2 3/3] ASoC: Automatically assign the default readable()/volatile() functions Dimitris Papastamos
2011-01-13 13:31 ` Liam Girdwood [this message]
2011-01-13 14:08 ` [PATCH v2 1/3] ASoC: soc-cache: Add support for " 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=1294925472.3453.3.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=Peter.Hsiang@maxim-ic.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dp@opensource.wolfsonmicro.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=timur@freescale.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).