From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dimitris Papastamos <dp@opensource.wolfsonmicro.com>,
Samuel Oritz <sameo@linux.intel.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Graeme Gregory <gg@slimlogic.co.uk>
Subject: Re: [PATCH 0/8] regmap: Generic I2C and SPI register map library
Date: Thu, 30 Jun 2011 18:14:52 +0100 [thread overview]
Message-ID: <4E0CAF0C.7060309@ti.com> (raw)
In-Reply-To: <4E0CAD47.9020709@ti.com>
On 30/06/11 18:07, Liam Girdwood wrote:
> On 30/06/11 06:58, Mark Brown wrote:
>> [This revision of the series has some minor updates to the SPI code.]
>>
>> Many I2C and SPI based devices implement register maps on top of the raw
>> wire interface. This is generally done in a very standard fashion by
>> devices, resulting in a lot of very similar code in drivers. For some
>> time now ASoC has factored this code out into the subsystem but that's
>> only useful for audio devices. The intention with this series is to
>> generalise the concept so that it can be used throughout the kernel.
>>
>> It's not intended that this be suitable for all devices - some devices
>> have things that are hard to generalise like registers with variable
>> size and paging which are hard to support genericly. At the minute the
>> code is focused on the common cases. It is likely that the same code
>> could be used with other buses with similar properties to I2C and SPI.
>>
>> Currently only physical I/O is handled, the intention is that once this
>> support has been reviewed and merged the generic register cache code
>> that ASoC includes will also be factored out too. For devices with read
>> heavy workloads (especially those that need a lot of read/modify/write
>> cycles) or which don't support read at all this can provide a useful
>> performance improvement and for sparse register maps there's a lot of
>> benefit in relatively complex cache code.
>>
>> I'm not entirely happy with the implementation currently but am fairly
>> happy with the external interfaces.
>>
>
> I'm also happy with the interface and imho the code looks fine for initial integration.
>
Forgot this.
Acked-by: Liam Girdwood <lrg@ti.com>
prev parent reply other threads:[~2011-06-30 17:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 5:58 [PATCH 0/8] regmap: Generic I2C and SPI register map library Mark Brown
2011-06-30 6:00 ` [PATCH 1/8] regmap: Add generic non-memory mapped register access API Mark Brown
2011-06-30 6:00 ` [PATCH 2/8] regmap: Add I2C bus support Mark Brown
2011-06-30 6:00 ` [PATCH 3/8] regmap: Add SPI " Mark Brown
2011-06-30 6:00 ` [PATCH 4/8] ASoC: Use new register map API for ASoC generic physical I/O Mark Brown
2011-06-30 6:00 ` [PATCH 5/8] mfd: Convert WM831x to use regmap API Mark Brown
2011-06-30 6:00 ` [PATCH 6/8] mfd: Convert WM8994 to use new register map API Mark Brown
2011-06-30 6:00 ` [PATCH 7/8] mfd: Convert pcf50633 " Mark Brown
2011-06-30 6:00 ` [PATCH 8/8] regulator: Convert tps65023 to use regmap API Mark Brown
2011-06-30 17:07 ` [PATCH 0/8] regmap: Generic I2C and SPI register map library Liam Girdwood
2011-06-30 17:14 ` Liam Girdwood [this message]
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=4E0CAF0C.7060309@ti.com \
--to=lrg@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dp@opensource.wolfsonmicro.com \
--cc=gg@slimlogic.co.uk \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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