From: Arnd Bergmann <arnd@arndb.de>
To: devicetree-discuss@lists.ozlabs.org
Cc: Benoit Cousson <b-cousson@ti.com>,
grant.likely@secretlab.ca, tony@atomide.com, manjugk@ti.com,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/13] OMAP4: Add DT support for i2c and twl6030
Date: Thu, 01 Sep 2011 21:14:07 +0200 [thread overview]
Message-ID: <2756178.9Ir4cpMAU8@wuerfel> (raw)
In-Reply-To: <1314897689-17791-1-git-send-email-b-cousson@ti.com>
On Thursday 01 September 2011 19:21:16 Benoit Cousson wrote:
> This is a rework of the original series done by Manju:
> http://www.spinics.net/lists/linux-omap/msg55827.html
>
> It fixes the main issue of the previous series that was not booting at all
> due to the lack of twl support. That fix is mandatory to allow further
> work on the regulators DT bindings.
> In order to have a minimal i2c support, both i2c and twl must be added
> at the same time.
> Please note than some patches can be reshuffle with the previous OMAP4
> series to avoid the intermediate step with static i2c initialization.
>
> That series is as well using the hwmods binding introduced in my previous
> series.
> The OMAP3/beagle support will be added in an other series.
>
> A couple of basic i2c devices are added for panda and sdp board.
>
> Patches are based on for_3.2/4_omap4_dt_early_devices + devicetree/test
> and are available here:
> git://gitorious.org/omap-pm/linux.git for_3.2/5_omap_dt_i2c_twl
>
> Tested on PandaBoard and sdp4430.
I think this is great stuff. I missed the original series, but
it's definitely good to see progress on this!
Arnd
prev parent reply other threads:[~2011-09-01 19:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 17:21 [PATCH 00/13] OMAP4: Add DT support for i2c and twl6030 Benoit Cousson
2011-09-01 17:21 ` [PATCH 01/13] irq: Add stub for none DT build in irqdomain.h Benoit Cousson
2011-09-01 17:21 ` [PATCH 02/13] i2c: OMAP: Add DT support for i2c controller Benoit Cousson
2011-09-01 17:21 ` [PATCH 03/13] documentation/dt: Add OMAP i2c bindings documentation Benoit Cousson
2011-09-01 17:21 ` [PATCH 04/13] mfd: twl-core: Add initial DT support for twl4030/twl6030 Benoit Cousson
2011-09-01 18:27 ` Arnd Bergmann
2011-09-05 16:05 ` Cousson, Benoit
2011-09-01 17:21 ` [PATCH 05/13] documentation/dt: Add TWL4030 and TWL6030 bindings Benoit Cousson
2011-09-01 17:21 ` [PATCH 06/13] arm/dts: OMAP4: Add i2c controller nodes Benoit Cousson
2011-09-01 17:21 ` [PATCH 07/13] arm/dts: omap4-sdp: Set clock freq for i2c controllers Benoit Cousson
2011-09-01 17:21 ` [PATCH 08/13] arm/dts: omap4-panda: " Benoit Cousson
2011-09-01 17:21 ` [PATCH 09/13] arm/dts: omap4-sdp: Add twl6030 node Benoit Cousson
2011-09-01 17:21 ` [PATCH 10/13] arm/dts: omap4-panda: " Benoit Cousson
2011-09-01 17:21 ` [PATCH 11/13] OMAP4: board-dt: Remove static i2c init Benoit Cousson
2011-09-01 17:21 ` [PATCH 12/13] arm/dts: omap4-sdp: Add i2c3 & i2c4 devices Benoit Cousson
2011-09-01 17:21 ` [PATCH 13/13] arm/dts: omap4-panda: Add EEPROM entry in i2c3 Benoit Cousson
2011-09-01 19:14 ` Arnd Bergmann [this message]
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=2756178.9Ir4cpMAU8@wuerfel \
--to=arnd@arndb.de \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=manjugk@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).