linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: mvebu: kirkwood: add PogoPlug series 4 device tree
Date: Fri, 27 Nov 2015 21:27:38 +0100	[thread overview]
Message-ID: <20151127202738.GC32356@lunn.ch> (raw)
In-Reply-To: <1448578868-6323-1-git-send-email-linus.walleij@linaro.org>

> +	chosen {
> +		bootargs = "console=ttyS0,115200n8";
> +		stdout-path = &uart0;

Hi Linus

You can append the baud rate etc to uart0, and then don't need
bootargs.

> +	};
> +
> +	gpio_keys {
> +		compatible = "gpio-keys";
> +		#address-cells = <1>;
> +		#size-cells = <0>;
> +		pinctrl-0 = <&pmx_button_eject>;
> +		pinctrl-names = "default";
> +
> +		button at 1 {
> +			debounce_interval = <50>;
> +			wakeup-source;
> +			/* KEY_EJECTCD */
> +			linux,code = <161>;

include/dt-bindings/input/linux-event-codes.h and then

	                linux,code = <KEY_EJECTCD>

> +			label = "Eject Button";
> +			gpios = <&gpio0 29 GPIO_ACTIVE_LOW>;
> +		};
> +	};
> +
> +	gpio-leds {
> +		compatible = "gpio-leds";
> +		pinctrl-0 = <&pmx_led_green &pmx_led_red>;
> +		pinctrl-names = "default";
> +
> +		health {
> +			label = "status:green:health";

The convention is that the first part of the label is the machine
name. OpenWRT and others often does something else... So

s/status/pogoplugv4/g
 
> +			gpios = <&gpio0 22 GPIO_ACTIVE_LOW>;
> +			default-state = "on";
> +		};
> +		fault {
> +			label = "status:red:fault";
> +			gpios = <&gpio0 24 GPIO_ACTIVE_LOW>;
> +		};
> +	};
> +};


> +&i2c0 {
> +	status = "okay";
> +};

Is there something on this i2c bus?

Thanks
	Andrew

  reply	other threads:[~2015-11-27 20:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26 23:01 [PATCH 2/2] ARM: mvebu: kirkwood: add PogoPlug series 4 device tree Linus Walleij
2015-11-27 20:27 ` Andrew Lunn [this message]
2015-12-11  8:28   ` Linus Walleij
2015-12-11 14:21     ` Andrew Lunn

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=20151127202738.GC32356@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=linux-arm-kernel@lists.infradead.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).