From: Dan Murphy <dmurphy@ti.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: b-cousson@ti.com, tony@atomide.com, linux@arm.linux.org.uk,
linux-omap@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: omap4-panda: Add LED support into the panda DTS files
Date: Wed, 17 Apr 2013 14:46:58 -0500 [thread overview]
Message-ID: <516EFC32.6030005@ti.com> (raw)
In-Reply-To: <516EF59E.3090907@ti.com>
On 04/17/2013 02:18 PM, Jon Hunter wrote:
> On 04/17/2013 02:09 PM, Dan Murphy wrote:
>> The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
>> are different.
>>
>> Abstract away the pinmux and the LED definitions for the two boards.
> Just a heads-up but you should base this upon Benoit's for_3.10 branch
> [1] as there is now a omap4-panda-common.dtsi where the led stuff
> currently resides.
>
> Cheers
> Jon
>
> [1]
> http://git.kernel.org/cgit/linux/kernel/git/bcousson/linux-omap-dt.git/log/?h=for_3.10/dts
Thanks Jon. Will resend against Benoit's tree.
Dan
--
----------------------------------------------
Dan Murphy
WARNING: multiple messages have this Message-ID (diff)
From: dmurphy@ti.com (Dan Murphy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: omap4-panda: Add LED support into the panda DTS files
Date: Wed, 17 Apr 2013 14:46:58 -0500 [thread overview]
Message-ID: <516EFC32.6030005@ti.com> (raw)
In-Reply-To: <516EF59E.3090907@ti.com>
On 04/17/2013 02:18 PM, Jon Hunter wrote:
> On 04/17/2013 02:09 PM, Dan Murphy wrote:
>> The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
>> are different.
>>
>> Abstract away the pinmux and the LED definitions for the two boards.
> Just a heads-up but you should base this upon Benoit's for_3.10 branch
> [1] as there is now a omap4-panda-common.dtsi where the led stuff
> currently resides.
>
> Cheers
> Jon
>
> [1]
> http://git.kernel.org/cgit/linux/kernel/git/bcousson/linux-omap-dt.git/log/?h=for_3.10/dts
Thanks Jon. Will resend against Benoit's tree.
Dan
--
----------------------------------------------
Dan Murphy
WARNING: multiple messages have this Message-ID (diff)
From: Dan Murphy <dmurphy@ti.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: <b-cousson@ti.com>, <tony@atomide.com>, <linux@arm.linux.org.uk>,
<linux-omap@vger.kernel.org>,
<devicetree-discuss@lists.ozlabs.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: omap4-panda: Add LED support into the panda DTS files
Date: Wed, 17 Apr 2013 14:46:58 -0500 [thread overview]
Message-ID: <516EFC32.6030005@ti.com> (raw)
In-Reply-To: <516EF59E.3090907@ti.com>
On 04/17/2013 02:18 PM, Jon Hunter wrote:
> On 04/17/2013 02:09 PM, Dan Murphy wrote:
>> The GPIO for LED D1 on the omap4-panda a1-a3 rev and the omap4-panda-es
>> are different.
>>
>> Abstract away the pinmux and the LED definitions for the two boards.
> Just a heads-up but you should base this upon Benoit's for_3.10 branch
> [1] as there is now a omap4-panda-common.dtsi where the led stuff
> currently resides.
>
> Cheers
> Jon
>
> [1]
> http://git.kernel.org/cgit/linux/kernel/git/bcousson/linux-omap-dt.git/log/?h=for_3.10/dts
Thanks Jon. Will resend against Benoit's tree.
Dan
--
----------------------------------------------
Dan Murphy
next prev parent reply other threads:[~2013-04-17 19:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 19:09 [PATCH] Fix omap4 panda LED definitions Dan Murphy
2013-04-17 19:09 ` Dan Murphy
2013-04-17 19:09 ` Dan Murphy
2013-04-17 19:09 ` [PATCH] ARM: dts: omap4-panda: Add LED support into the panda DTS files Dan Murphy
2013-04-17 19:09 ` Dan Murphy
2013-04-17 19:09 ` Dan Murphy
2013-04-17 19:18 ` Jon Hunter
2013-04-17 19:18 ` Jon Hunter
2013-04-17 19:18 ` Jon Hunter
2013-04-17 19:46 ` Dan Murphy [this message]
2013-04-17 19:46 ` Dan Murphy
2013-04-17 19:46 ` Dan Murphy
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=516EFC32.6030005@ti.com \
--to=dmurphy@ti.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jon-hunter@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--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 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.