From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Oskar Schirmer <oskar@scara.com>
Cc: sameo@linux.intel.com, dmitry.torokhov@gmail.com,
kernel@pengutronix.de, u.kleine-koenig@pengutronix.de,
philippe.retornaz@epfl.ch, michael.thalmeier@hale.at,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/7] mfd: add I2C handling to mc13xxx driver
Date: Thu, 16 Feb 2012 16:40:31 +0000 [thread overview]
Message-ID: <20120216164029.GA27239@sirena.org.uk> (raw)
In-Reply-To: <1329215672-15706-4-git-send-email-oskar@scara.com>
On Tue, Feb 14, 2012 at 10:34:28AM +0000, Oskar Schirmer wrote:
> mc13xxx chips may be wired to SPI or I2C, alternatively.
> Up to now, mc13xxx did support SPI wiring solely.
> Add support for I2C wiring, make the two alternatives
> separate menu option in configuration.
As with the last time you posted this it really would be better to
convert this to regmap rather than add new open coded register map I/O
support.
next prev parent reply other threads:[~2012-02-16 16:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 10:34 [PATCH 0/7] add support for mc13892 I2C based touch panel for mx35_3ds Oskar Schirmer
2012-02-14 10:34 ` [PATCH 1/7] mfd: move mc13xxx global declarations to header file Oskar Schirmer
2012-02-14 10:34 ` [PATCH 2/7] mfd: split off mc13xxx SPI specifica from core Oskar Schirmer
2012-02-14 10:34 ` [PATCH 3/7] mfd: add I2C handling to mc13xxx driver Oskar Schirmer
2012-02-16 16:40 ` Mark Brown [this message]
2012-02-14 10:34 ` [PATCH 4/7] input/touchscreen: rename mc13783_ts.c Oskar Schirmer
2012-02-14 10:34 ` [PATCH 5/7] input/touchscreen: add support for mc13892 Oskar Schirmer
2012-02-14 10:34 ` [PATCH 6/7] input/touchscreen: add calibration functionality with Oskar Schirmer
2012-02-14 10:34 ` [PATCH 7/7] arm/imx: add mc13892 I2C based touch panel support for Oskar Schirmer
2012-02-14 11:49 ` [PATCH 0/7] add support for mc13892 I2C based touch panel for mx35_3ds Uwe Kleine-König
2012-02-14 14:27 ` Oskar Schirmer
2012-02-23 15:37 ` 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=20120216164029.GA27239@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=dmitry.torokhov@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.thalmeier@hale.at \
--cc=oskar@scara.com \
--cc=philippe.retornaz@epfl.ch \
--cc=sameo@linux.intel.com \
--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®