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,
alexg@meprolight.com
Subject: mc13xxx: add I2C support, V5
Date: Sun, 1 Apr 2012 16:41:35 +1000 [thread overview]
Message-ID: <1333262499-25871-1-git-send-email-marc@cpdesign.com.au> (raw)
Hi,
This series (against mfd-2.6/for-next) changes the mc13xxx driver to use
regmap and adds I2C support.
It has a compile dependency on regmap/for-next, as the spi driver uses the
recently added pad_bits config field.
Patch 2/4 has:
Reviewed-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Patch 4/4 has:
Signed-off-by: Oskar Schirmer <oskar@scara.com>
Changes since:
V4:
- Fix compile error when CONFIG_OF enabled
- Select REGMAP_I2C and REGMAP_SPI for appropriate drivers.
V3:
- spi driver uses padded register format (reads should actually work now!)
- mc13873 removed from I2C driver
- fix memory leak on probe error
Cheers,
Marc
next reply other threads:[~2012-04-01 7:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 6:41 Marc Reilly [this message]
2012-04-01 6:41 ` [PATCH v5 1/4] mfd: mc13xxx-core: Prepare for separate spi and i2c backends Marc Reilly
2012-04-01 6:41 ` [PATCH v5 2/4] mfd: mc13xxx-core: use regmap for register access Marc Reilly
2012-04-02 16:00 ` Mark Brown
2012-04-01 6:41 ` [PATCH v5 3/4] mfd: mc13xxx-core: Move spi specific code into separate module Marc Reilly
2012-04-01 6:41 ` [PATCH v5 4/4] mfd: mc13xxx: Add i2c driver Marc Reilly
2012-04-01 9:21 ` mc13xxx: add I2C support, V5 Uwe Kleine-König
[not found] ` <201204011939.49665.marc@cpdesign.com.au>
2012-04-02 6:40 ` Uwe Kleine-König
2012-04-01 11:12 ` Alex Gershgorin
2012-04-16 23:21 ` Marc Reilly
2012-05-01 10:39 ` Samuel Ortiz
2012-05-01 22:55 ` Marc Reilly
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=1333262499-25871-1-git-send-email-marc@cpdesign.com.au \
--to=marc@cpdesign.com.au \
--cc=alexg@meprolight.com \
--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®