mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Reilly <marc@cpdesign.com.au>
To: sameo@linux.intel.com
Cc: linux-arm-kernel@lists.infradead.org,
	spi-devel-general@lists.sourceforge.net,
	linux-i2c@vger.kernel.org, u.kleine-koenig@pengutronix.de,
	oskar@scara.com, linux-kernel@vger.kernel.org
Subject: mfd: mc13xxx: add I2C support, V2
Date: Sun, 11 Mar 2012 12:29:59 +1100	[thread overview]
Message-ID: <1331429402-9639-1-git-send-email-marc@cpdesign.com.au> (raw)

Hi,                                                                                                                            

This series (based on Samuel's mfd-2.6/for-next) adds I2C support for the
mc13xxx family PMICs. Thanks to Oscar for adding dt support for the I2C driver.                       

V2 lets both I2C and SPI support be enabled at the same time and limits the 
scope of common definitions by using a private include header rather than global
one.
The only issue from V1 [0] not addressed is the use of regmap - mainly, I don't
have the time. I accept that this is a lame excuse but hope that use of regmap 
can come later if it is required.

Cheers,
Marc                        

[0] http://www.spinics.net/lists/linux-i2c/msg06992.html


             reply	other threads:[~2012-03-11  2:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-11  1:29 Marc Reilly [this message]
2012-03-11  1:30 ` [PATCH v2 1/3] mfd: mc13xxx-core: Prepare for separate spi and i2c backends Marc Reilly
2012-03-11  9:33   ` Uwe Kleine-König
2012-03-11  1:30 ` [PATCH v2 2/3] mfd: mc13xxx-core: Move spi specific code into separate module Marc Reilly
2012-03-11  1:30 ` [PATCH v2 3/3] mfd: mc13xxx-core: Add i2c driver Marc Reilly
2012-03-11 11:50 ` mfd: mc13xxx: add I2C support, V2 Wolfram Sang
2012-03-12 14:06   ` 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=1331429402-9639-1-git-send-email-marc@cpdesign.com.au \
    --to=marc@cpdesign.com.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oskar@scara.com \
    --cc=sameo@linux.intel.com \
    --cc=spi-devel-general@lists.sourceforge.net \
    --cc=u.kleine-koenig@pengutronix.de \
    /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
all inboxes | Powered by JetHome®