From: Anatolij Gustschin <agust@denx.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@list.ozlabs.org, linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH 1/2] powerpc/5200: Add Lite5200 on-board LEDs as devices
Date: Mon, 11 Feb 2013 22:53:45 +0100 [thread overview]
Message-ID: <20130211225345.08dd112b@crub> (raw)
In-Reply-To: <1360310571-31494-1-git-send-email-grant.likely@secretlab.ca>
On Fri, 8 Feb 2013 08:02:50 +0000
Grant Likely <grant.likely@secretlab.ca> wrote:
> The Lite5200 evaluation board has a number of debug LEDs that Linux
> doesn't know about yet. This change adds a gpio-leds stanza to the
> lite5200 device tree so that the correct driver can get hooked up.
>
> Also, make use of the dtc labels feature to reduce the number of source
> lines required to add the gpio-controller property to the general
> purpose timer nodes. In addition, the required #gpio-cells properties
> are added to the common mpc5200b dtsi include file so that each board
> doesn't need to add them explicitly. This still doesn't enable gpio
> mode, 'gpio-controller' is required for that, but it means less work
> needs to be done by board ports.
>
> Cc: Anatolij Gustschin <agust@denx.de>
> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> ---
> arch/powerpc/boot/dts/lite5200b.dts | 23 +++++++++++++++++++----
> arch/powerpc/boot/dts/mpc5200b.dtsi | 25 +++++++++++++++++--------
> 2 files changed, 36 insertions(+), 12 deletions(-)
Applied, thanks!
Anatolij
prev parent reply other threads:[~2013-02-11 21:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 8:02 [PATCH 1/2] powerpc/5200: Add Lite5200 on-board LEDs as devices Grant Likely
2013-02-08 8:02 ` [PATCH 2/2] powerpc/5200: Use the gpt* labels to simplify mpc5200 dts files Grant Likely
2013-02-11 21:55 ` Anatolij Gustschin
2013-02-11 21:53 ` Anatolij Gustschin [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=20130211225345.08dd112b@crub \
--to=agust@denx.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@list.ozlabs.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).