public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Emilio López" <emilio@elopez.com.ar>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kevin@allwinnertech.com,
	sunny@allwinnertech.com, shuge@allwinnertech.com
Subject: Re: [linux-sunxi] [PATCH 5/6] ARM: sunxi: Add Olimex A10s-Olinuxino-micro device tree
Date: Fri, 14 Jun 2013 15:09:49 -0300	[thread overview]
Message-ID: <51BB5C6D.5070308@elopez.com.ar> (raw)
In-Reply-To: <1370795767-9769-6-git-send-email-maxime.ripard@free-electrons.com>

Hi Maxime,

El 09/06/13 13:36, Maxime Ripard escribió:
> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> ---
>  arch/arm/boot/dts/sun5i-a10s-olinuxino-micro.dts | 75 ++++++++++++++++++++++++
>  1 file changed, 75 insertions(+)
>  create mode 100644 arch/arm/boot/dts/sun5i-a10s-olinuxino-micro.dts

Please add this on the sunxi target in arch/arm/boot/dts/Makefile so it
gets built on make dtbs.

(snip)

> +	leds {
> +		compatible = "gpio-leds";
> +		pinctrl-names = "default";
> +		pinctrl-0 = <&led_pins_olinuxino>;
> +
> +		power {
> +			gpios = <&pio 4 3 0>;
> +			default-state = "on";
> +		};

Also, as discussed on IRC, I think it would be wise to change the name
on the LED node. The schematics have a 'power' led already that is
hard-wired to 3.3v, and this led node that you are declaring is referred
as 'led1' there. I suppose 'green' would be a suitable name to keep
consistency with other sunxi boards (namely cubieboard).

Other than that, my OLinuXino worked just fine after applying this
patchset, so

Tested-by: Emilio López <emilio@elopez.com.ar>

Thanks!

Emilio

  reply	other threads:[~2013-06-14 18:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-09 16:36 [PATCH 0/6] Add support for Allwinner A10s SoCs Maxime Ripard
2013-06-09 16:36 ` [PATCH 1/6] ARM: sunxi: Add Allwinner A10s machine compatible Maxime Ripard
2013-06-09 16:36 ` [PATCH 2/6] pinctrl: sunxi: Move the pins definitions to a separate header Maxime Ripard
2013-06-16 11:03   ` Linus Walleij
2013-06-17  8:41     ` Maxime Ripard
2013-06-17 16:11       ` Linus Walleij
2013-06-09 16:36 ` [PATCH 3/6] pinctrl: sunxi: Add Allwinner A10s pins Maxime Ripard
2013-06-16 11:04   ` Linus Walleij
2013-06-09 16:36 ` [PATCH 4/6] ARM: sunxi: dt: Add Allwinner A10s DTSI Maxime Ripard
2013-06-09 21:36   ` Arnd Bergmann
2013-06-10 10:34     ` Maxime Ripard
2013-06-10 14:58       ` Arnd Bergmann
2013-06-09 16:36 ` [PATCH 5/6] ARM: sunxi: Add Olimex A10s-Olinuxino-micro device tree Maxime Ripard
2013-06-14 18:09   ` Emilio López [this message]
2013-06-17  8:38     ` [linux-sunxi] " Maxime Ripard
2013-06-09 16:36 ` [PATCH 6/6] ARM: multi_v7: Enable Allwinner EMAC in multi_v7_defconfig Maxime Ripard
2013-06-15 13:14 ` [PATCH 0/6] Add support for Allwinner A10s SoCs Maxime Ripard

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=51BB5C6D.5070308@elopez.com.ar \
    --to=emilio@elopez.com.ar \
    --cc=kevin@allwinnertech.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=shuge@allwinnertech.com \
    --cc=sunny@allwinnertech.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