From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Sean MacLennan" <smaclennan@pikatech.com>
Cc: linuxppc-dev@ozlabs.org, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [RESEND][PATCH 2/2][POWERPC] PIKA Warp: Update platform code to supportRev B boards
Date: Mon, 28 Apr 2008 19:58:26 -0600 [thread overview]
Message-ID: <fa686aa40804281858r6b2a1f9eva16983d0a3680fc0@mail.gmail.com> (raw)
In-Reply-To: <20080428215029.0e38a0d2@lappy.seanm.ca>
On Mon, Apr 28, 2008 at 7:50 PM, Sean MacLennan <smaclennan@pikatech.com> wrote:
> diff --git a/arch/powerpc/boot/dts/warp.dts b/arch/powerpc/boot/dts/warp.dts
> index b04a52e..3e95e99 100644
You still need to have *some* kind of change log and a signed-off-by
line in this patch. :-)
There is one minor change that needs to be added below; otherwise:
Acked-by: Grant Likely <grant.likely@secretlab.ca>
(You can add my acked-by line to the next version of this patch if
you're only changing the thing I comment on).
Josh, when he respins it I think the dts changes are ready to be picked up.
> @@ -186,18 +179,45 @@
> GPIO1: gpio@ef600c00 {
> compatible = "ibm,gpio-440ep";
> reg = <ef600c00 48>;
> + #gpio-cells = <2>;
> + gpio-controller;
> +
> + led@31 {
>
> + compatible = "linux,gpio-led";
> + linux,name = ":green:";
> + gpios = <&GPIO1 31>;
Since #gpio-cells is '2'; the gpios property needs to reflect that.
It should be:
gpios = <&GPIO1 31 0>;
The second cell the GPIO controller would use for flags (inverted,
open-drain, etc).
> + };
> +
> + led@30 {
> + compatible = "linux,gpio-led";
> + linux,name = ":red:";
> + gpios = <&GPIO1 30>;
ditto
> + };
>
>
> };
>
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-04-29 1:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 19:22 [RESEND][PATCH][POWERPC] PIKA Warp: Update platform code to support Rev B boards Sean MacLennan
2008-04-27 19:25 ` [RESEND][PATCH][POWERPC] PIKA Warp: Update platform code to supportRev " Sean MacLennan
2008-04-28 0:58 ` Stephen Rothwell
2008-04-28 1:51 ` Grant Likely
2008-04-28 2:25 ` Sean MacLennan
2008-04-28 4:47 ` Grant Likely
2008-04-28 17:10 ` Sean MacLennan
2008-04-28 17:44 ` Grant Likely
2008-04-28 17:59 ` Sean MacLennan
2008-04-28 20:44 ` Richard Purdie
2008-04-28 21:24 ` [RESEND][PATCH][POWERPC] PIKA Warp: Update platform code tosupportRev " Sean MacLennan
2008-04-28 21:36 ` Richard Purdie
2008-04-28 2:31 ` [RESEND][PATCH][POWERPC] PIKA Warp: Update platform code to supportRev " Sean MacLennan
2008-04-28 18:53 ` Sean MacLennan
2008-04-28 19:56 ` Grant Likely
2008-04-28 21:37 ` Sean MacLennan
2008-04-28 21:54 ` Scott Wood
2008-04-28 22:07 ` Sean MacLennan
2008-04-30 0:48 ` Josh Boyer
2008-04-28 22:07 ` Grant Likely
2008-04-29 1:47 ` [RESEND][PATCH 1/2][POWERPC] " Sean MacLennan
2008-04-29 1:50 ` [RESEND][PATCH 2/2][POWERPC] " Sean MacLennan
2008-04-29 1:58 ` Grant Likely [this message]
2008-04-29 3:27 ` Sean MacLennan
2008-04-29 3:28 ` [RESEND][PATCH 1/2][POWERPC] " Sean MacLennan
2008-04-29 5:08 ` Paul Mackerras
2008-04-29 5:42 ` [RESEND][PATCH 1/2][POWERPC] PIKA Warp: Update platform code tosupportRev " Sean MacLennan
2008-05-06 15:27 ` Sean MacLennan
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=fa686aa40804281858r6b2a1f9eva16983d0a3680fc0@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
--cc=smaclennan@pikatech.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).