From: b-cousson@ti.com (Cousson, Benoit)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 00/10] OMAP4: Add DT support for i2c and twl6030
Date: Fri, 9 Dec 2011 15:01:32 +0100 [thread overview]
Message-ID: <4EE214BC.7000405@ti.com> (raw)
In-Reply-To: <1323438631-28124-1-git-send-email-b-cousson@ti.com>
Mmm, the send-email was aborted because Manju's email is not valid anymore.
I'll repost after removing the email from the patches.
Sorry for the noise.
Regards,
Benoit
On 12/9/2011 2:50 PM, Benoit Cousson wrote:
> Hi Tony and Rob,
>
> Here is the updated version of the i2c + twl DT adaptation.
>
> This update, compared to v1 [1], is mainly due to the merge into 3.2 of
> Andy's i2c cleanup series that was introducing a lot of pdata accesses
> at runtime.
>
> The pm.c was updated to prevent the SR / VP initialization in the DT
> context since none of them is DT aware for the moment.
>
> A couple of basic i2c devices are added for panda, beagle and sdp board.
>
> Patches are based on for_3.3/2_dt_irq, to get the latest GIC binding,
> and are available here:
> git://gitorious.org/omap-pm/linux.git for_3.3/3_omap_dt_i2c_twl
>
> Tested on Beagle and sdp4430.
>
> Comments are welcome.
>
> Regards,
> Benoit
>
> [1] http://lists.ozlabs.org/pipermail/devicetree-discuss/2011-September/007821.html
>
>
> Benoit Cousson (10):
> ARM: OMAP2+: pm: Do not init statically the SR and voltage layer with DT
> i2c: OMAP: Add DT support for i2c controller
> mfd: twl-core: Add initial DT support for twl4030/twl6030
> rtc: rtc-twl: Add DT support for RTC inside twl4030/twl6030
> arm/dts: OMAP4: Add i2c controller nodes
> arm/dts: OMAP3: Add i2c controller nodes
> arm/dts: omap4-panda: Add twl6030 and i2c EEPROM
> arm/dts: omap4-sdp: Add twl6030, i2c3 and i2c4 devices
> arm/dts: omap3-beagle: Add twl4030 and i2c EEPROM
> ARM: OMAP2+: board-generic: Remove i2c static init
>
> Documentation/devicetree/bindings/i2c/omap-i2c.txt | 42 ++++++++
> .../devicetree/bindings/mfd/twl-familly.txt | 47 +++++++++
> Documentation/devicetree/bindings/rtc/twl-rtc.txt | 12 +++
> arch/arm/boot/dts/omap3-beagle.dts | 38 ++++++++
> arch/arm/boot/dts/omap3.dtsi | 28 ++++++
> arch/arm/boot/dts/omap4-panda.dts | 45 +++++++++
> arch/arm/boot/dts/omap4-sdp.dts | 63 ++++++++++++
> arch/arm/boot/dts/omap4.dtsi | 28 ++++++
> arch/arm/mach-omap2/board-generic.c | 48 +---------
> arch/arm/mach-omap2/pm.c | 8 ++
> drivers/i2c/busses/i2c-omap.c | 100 +++++++++++++-------
> drivers/mfd/twl-core.c | 53 ++++++++++-
> drivers/rtc/rtc-twl.c | 10 ++-
> 13 files changed, 435 insertions(+), 87 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/i2c/omap-i2c.txt
> create mode 100644 Documentation/devicetree/bindings/mfd/twl-familly.txt
> create mode 100644 Documentation/devicetree/bindings/rtc/twl-rtc.txt
>
next prev parent reply other threads:[~2011-12-09 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 13:50 [PATCH v2 00/10] OMAP4: Add DT support for i2c and twl6030 Benoit Cousson
2011-12-09 13:50 ` [PATCH v2 01/10] ARM: OMAP2+: pm: Do not init statically the SR and voltage layer with DT Benoit Cousson
2011-12-10 1:32 ` Kevin Hilman
2011-12-09 14:01 ` Cousson, Benoit [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-09 14:02 [PATCH v2 00/10] OMAP4: Add DT support for i2c and twl6030 Benoit Cousson
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=4EE214BC.7000405@ti.com \
--to=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).