From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: Marc Reilly <marc@cpdesign.com.au>
Cc: sameo@linux.intel.com, mkl@pengutronix.de,
linux-i2c@vger.kernel.org, u.kleine-koenig@pengutronix.de,
spi-devel-general@lists.sourceforge.net,
linux-arm-kernel@lists.infradead.org
Subject: Re: mc13xxx: add I2C support
Date: Thu, 19 Jan 2012 12:12:31 +0100 [thread overview]
Message-ID: <87lip4kktc.fsf@lebrac.rtp-net.org> (raw)
In-Reply-To: <1326934894-29516-1-git-send-email-marc@cpdesign.com.au> (Marc Reilly's message of "Thu, 19 Jan 2012 12:01:31 +1100")
Marc Reilly <marc@cpdesign.com.au> writes:
> Hi,
Hi,
>
> This series (based on 3.2) adds I2C support for the mc13xxx family PMICs.
> The patches are similar, but not identical to my previous patches for this [1], the
> main difference being the way the config items are done in patch 2.
>
> I don't have the hardware to retest on SPI hardware, I'd appreciate if someone could
> double check it still works.
>
> I've also got a stack of patches for the mc13xxx to follow, but should get this in
> first.
I've never looked at regmap deeply but can't it be done with regmap or is it
just a bad idea ?
Arnaud
WARNING: multiple messages have this Message-ID (diff)
From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: mc13xxx: add I2C support
Date: Thu, 19 Jan 2012 12:12:31 +0100 [thread overview]
Message-ID: <87lip4kktc.fsf@lebrac.rtp-net.org> (raw)
In-Reply-To: <1326934894-29516-1-git-send-email-marc@cpdesign.com.au> (Marc Reilly's message of "Thu, 19 Jan 2012 12:01:31 +1100")
Marc Reilly <marc@cpdesign.com.au> writes:
> Hi,
Hi,
>
> This series (based on 3.2) adds I2C support for the mc13xxx family PMICs.
> The patches are similar, but not identical to my previous patches for this [1], the
> main difference being the way the config items are done in patch 2.
>
> I don't have the hardware to retest on SPI hardware, I'd appreciate if someone could
> double check it still works.
>
> I've also got a stack of patches for the mc13xxx to follow, but should get this in
> first.
I've never looked at regmap deeply but can't it be done with regmap or is it
just a bad idea ?
Arnaud
next prev parent reply other threads:[~2012-01-19 11:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 1:01 mc13xxx: add I2C support Marc Reilly
2012-01-19 1:01 ` Marc Reilly
[not found] ` <1326934894-29516-1-git-send-email-marc-DtE7ei5U7Kg0n/F98K4Iww@public.gmane.org>
2012-01-19 1:01 ` [PATCH 1/3] mc13xxx-core: Prepare for separate spi and i2c backends Marc Reilly
2012-01-19 1:01 ` Marc Reilly
[not found] ` <1326934894-29516-2-git-send-email-marc-DtE7ei5U7Kg0n/F98K4Iww@public.gmane.org>
2012-01-19 7:35 ` Shawn Guo
2012-01-19 7:35 ` Shawn Guo
2012-01-19 7:51 ` Uwe Kleine-König
2012-01-19 7:51 ` Uwe Kleine-König
2012-01-19 1:01 ` [PATCH 2/3] mfd: mc13xxx-core: Move spi specific code into separate module Marc Reilly
2012-01-19 1:01 ` Marc Reilly
[not found] ` <1326934894-29516-3-git-send-email-marc-DtE7ei5U7Kg0n/F98K4Iww@public.gmane.org>
2012-01-19 8:08 ` Uwe Kleine-König
2012-01-19 8:08 ` Uwe Kleine-König
[not found] ` <20120119080843.GC4066-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-01-19 12:54 ` Grant Likely
2012-01-19 12:54 ` Grant Likely
2012-01-19 1:01 ` [PATCH 3/3] mfd: mc13xxx-core: Add i2c driver Marc Reilly
2012-01-19 1:01 ` Marc Reilly
2012-01-19 7:22 ` mc13xxx: add I2C support Shawn Guo
2012-01-19 7:22 ` Shawn Guo
2012-01-19 11:12 ` Arnaud Patard [this message]
2012-01-19 11:12 ` Arnaud Patard (Rtp)
[not found] ` <87lip4kktc.fsf-0gaJ4kiyQU6khWr4QmshqB2eb7JE58TQ@public.gmane.org>
2012-01-19 11:29 ` Mark Brown
2012-01-19 11:29 ` Mark Brown
[not found] ` <20120119112941.GC29494-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2012-01-20 7:55 ` Marc Reilly
[not found] ` <201201201855.35971.marc-DtE7ei5U7Kg0n/F98K4Iww@public.gmane.org>
2012-01-20 10:36 ` Arnaud Patard
2012-01-20 10:36 ` Arnaud Patard (Rtp)
2012-01-20 12:08 ` Mark Brown
2012-01-20 12:08 ` Mark Brown
2012-02-20 16:50 ` Samuel Ortiz
2012-02-20 16:50 ` 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=87lip4kktc.fsf@lebrac.rtp-net.org \
--to=arnaud.patard@rtp-net.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=marc@cpdesign.com.au \
--cc=mkl@pengutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.