From: Mark Brown <broonie@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Greg KH <gregkh@linuxfoundation.org>,
David Brown <davidb@codeaurora.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Nicolas Pitre <nico@fluxnic.net>
Subject: Re: [GIT PATCH] char/misc patches for 3.10-rc1
Date: Wed, 1 May 2013 17:12:26 +0100 [thread overview]
Message-ID: <20130501161226.GR26160@sirena.org.uk> (raw)
In-Reply-To: <201304292250.47699.arnd@arndb.de>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
On Mon, Apr 29, 2013 at 10:50:47PM +0200, Arnd Bergmann wrote:
> On Monday 29 April 2013, Linus Torvalds wrote:
> > - I'm not seeing what commonalities this thing can have with anything
> > else. Did anybody look at the code? There's nothing generic there.
> It's a simple bus that has addressable registers. We have a generic
> infrastructure for these things in drivers/base/regmap, currently
> handling I2C, SPI and MMIO based buses, which are often used as
> different methods to address the same device endpoints. I think it
> would be sensible to add another one-off type here and convert the
> user(s) to be based on the regmap interface rather than its own
> set of exported symbols.
No need for a special bus type, the regmap core now has support for
supplying read and write callbacks so drivers for devices that look
nothing like a bytestream can use the cache and other infrastructure.
This is a good idea anyway for a PMIC since the regulator API has a
large set of regmap based helpers for the standard operations so we'd
probably save a bunch of code in the regulator driver too.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-05-01 16:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 16:21 [GIT PATCH] char/misc patches for 3.10-rc1 Greg KH
2013-04-29 18:28 ` Linus Torvalds
2013-04-29 18:38 ` Greg KH
2013-04-29 18:55 ` Linus Torvalds
2013-04-29 19:02 ` Linus Torvalds
2013-04-29 19:15 ` Linus Torvalds
2013-04-29 19:54 ` Arnd Bergmann
2013-04-29 20:12 ` Linus Torvalds
2013-04-29 20:50 ` Arnd Bergmann
2013-04-29 21:13 ` Linus Torvalds
2013-04-29 21:22 ` Arnd Bergmann
2013-05-01 16:12 ` Mark Brown [this message]
2013-04-29 21:08 ` David Brown
2013-04-29 21:16 ` Arnd Bergmann
2013-05-01 16:13 ` Mark Brown
2013-05-02 20:53 ` David Brown
2013-05-03 8:06 ` Mark Brown
2013-04-29 21:18 ` Linus Torvalds
2013-04-29 21:29 ` Arnd Bergmann
2013-04-29 22:00 ` MFD: move ssbi driver into drivers/mfd Arnd Bergmann
2013-04-29 22:10 ` Greg KH
2013-04-29 22:48 ` Nicolas Pitre
2013-04-30 0:00 ` David Brown
2013-04-30 10:18 ` Samuel Ortiz
2013-04-30 10:26 ` Arnd Bergmann
2013-05-16 9:49 ` Samuel Ortiz
2013-04-29 20:45 ` [GIT PATCH] char/misc patches for 3.10-rc1 Nicolas Pitre
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=20130501161226.GR26160@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=davidb@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=torvalds@linux-foundation.org \
/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).