From: Benoit Cousson <b-cousson@ti.com>
To: "AnilKumar, Chimata" <anilkumar@ti.com>
Cc: "tony@atomide.com" <tony@atomide.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>
Subject: Re: [PATCH 00/10] ARM: dts: AM33XX: Add device tree data
Date: Mon, 5 Nov 2012 17:37:45 +0100 [thread overview]
Message-ID: <5097EB59.8070104@ti.com> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EA647CE@DBDE01.ent.ti.com>
Hi Anil,
On 11/05/2012 02:46 PM, AnilKumar, Chimata wrote:
> On Mon, Nov 05, 2012 at 16:15:40, AnilKumar, Chimata wrote:
>> Add device tree date for GPIO based various drivers matrix keypad,
>> volume keys, push buttons and use leds accross three AM33XX devices
>> viz EVM, BeagleBone and Starter Kit.
>>
>> To make it functional this series also adds pinctrl data for all
>> the GPIOs used by various drivers. In this series only default state
>> pinmux/conf settings are added because of sleep/idle state pinctrl
>> values are not available.
>>
>> These patches are based on linux-omap-dt:for_3.8/dts tree and these
>
> My bad, small correction in this statement, these patches apply cleanly
> on linux-omap-dt:for_3.8/dts tree with the below two patches.
> http://www.spinics.net/lists/arm-kernel/msg204872.html
> http://www.spinics.net/lists/arm-kernel/msg204873.html
Mmm, this 2 patches do have dependency on some driver changes that might
not be accepted for 3.8. And in fact I do have some comment on the RTC
one :-)
Don't you prefer to change the order to allow me to pull these ones first?
Thanks,
Benoit
next prev parent reply other threads:[~2012-11-05 16:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 10:45 [PATCH 00/10] ARM: dts: AM33XX: Add device tree data AnilKumar Ch
2012-11-05 10:45 ` [PATCH 01/10] ARM: dts: AM33XX: Add pinmux configuration for matrix keypad to EVM AnilKumar Ch
2012-11-05 10:45 ` [PATCH 02/10] ARM: dts: AM33XX: Add matrix keypad device tree data to am335x-evm AnilKumar Ch
2012-11-05 10:45 ` [PATCH 03/10] ARM: dts: AM33XX: Add pinmux configuration for volume-keys to EVM AnilKumar Ch
2012-11-05 10:45 ` [PATCH 04/10] ARM: dts: AM33XX: Add volume-keys device tree data to am335x-evm AnilKumar Ch
2012-11-05 10:45 ` [PATCH 05/10] ARM: dts: AM33XX: Add pinmux configuration for user-leds to BONE AnilKumar Ch
2012-11-05 10:45 ` [PATCH 06/10] ARM: dts: AM33XX: Add user-leds device tree data to am335x-bone AnilKumar Ch
2012-11-05 10:45 ` [PATCH 07/10] ARM: dts: AM33XX: Add pinmux configuration for gpio-leds to EVMSK AnilKumar Ch
2012-11-05 10:45 ` [PATCH 08/10] ARM: dts: AM33XX: Add user-leds device tree data to am335x-evmsk AnilKumar Ch
2012-11-05 10:45 ` [PATCH 09/10] ARM: dts: AM33XX: Add pinmux configuration for gpio-keys to EVMSK AnilKumar Ch
2012-11-05 10:45 ` [PATCH 10/10] ARM: dts: AM33XX: Add push-buttons device tree data to am335x-evmsk AnilKumar Ch
2012-11-05 13:46 ` [PATCH 00/10] ARM: dts: AM33XX: Add device tree data AnilKumar, Chimata
2012-11-05 16:37 ` Benoit Cousson [this message]
2012-11-06 4:33 ` AnilKumar, Chimata
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=5097EB59.8070104@ti.com \
--to=b-cousson@ti.com \
--cc=anilkumar@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=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).