public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: [PATCH 0/3] Add regmap support for WM831x and WM8994
Date: Sat, 6 Aug 2011 12:58:08 +0900	[thread overview]
Message-ID: <20110806035806.GA21557@opensource.wolfsonmicro.com> (raw)

This series converts the WM831x and WM8994 MFD drivers over to using the
regmap API (which was merged by Linus during this merge window).  As
these are my main devices for use when developing regmap it would be
very helpful if I could merge them via the regmap tree - does that seem
sensible to you?

The second patch (adding readback info to wm831x) depends on regmap API
updates that aren't in mainline yet.

Mark Brown (3):
      mfd: Convert WM831x to use regmap API
      mfd: Provide regmap register readback info from wm831x driver
      mfd: Convert WM8994 to use new register map API

 drivers/mfd/Kconfig             |    3 +
 drivers/mfd/wm831x-core.c       |  263 ++++++++++++++++++++++++++++++---------
 drivers/mfd/wm831x-i2c.c        |   68 ++--------
 drivers/mfd/wm831x-spi.c        |   60 ++-------
 drivers/mfd/wm8994-core.c       |  178 +++++---------------------
 include/linux/mfd/wm831x/core.h |    9 +-
 include/linux/mfd/wm8994/core.h |    9 +-
 7 files changed, 272 insertions(+), 318 deletions(-)

             reply	other threads:[~2011-08-06  3:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-06  3:58 Mark Brown [this message]
2011-08-06  3:58 ` [PATCH 1/3] mfd: Convert WM831x to use regmap API Mark Brown
2011-08-06  3:58   ` [PATCH 2/3] mfd: Provide regmap register readback info from wm831x driver Mark Brown
2011-08-06  3:58   ` [PATCH 3/3] mfd: Convert WM8994 to use new register map API Mark Brown
2011-08-22  9:05 ` [PATCH 0/3] Add regmap support for WM831x and WM8994 Samuel Ortiz

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=20110806035806.GA21557@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.com \
    --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