From: Andrew Lunn <andrew@lunn.ch>
To: Evgeni Dobrev <evgeni@studio-punkt.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Jason Cooper <jason@lakedaemon.net>,
Gregory Clement <gregory.clement@free-electrons.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@googlemail.com>
Subject: Re: [PATCH 2/2] ARM: dts: kirkwood: add dts support for Seagate BlackArmor NAS220
Date: Tue, 16 Dec 2014 09:56:45 +0100 [thread overview]
Message-ID: <20141216085645.GB1450@lunn.ch> (raw)
In-Reply-To: <20141215203855.GA28940@anne>
On Mon, Dec 15, 2014 at 09:38:55PM +0100, Evgeni Dobrev wrote:
> This patch adds support for Seagate BlackArmor NAS220.
Hi Evgeni
Thanks for the patch. It looks good apart from a few minor comments.
Please could you also Cc: the mvebu maintainers, otherwise you patch
might net be seen by the right people. I added them.
>
> The Seagate BlackArmor NAS 220 is a NAS system based on Marvell 88f6192. It has 32MB NAND and 128MB DRAM. It has two SATA slots, one Gigabit Ethernet port, two USB 2.0 ports, two buttons and three LEDs. There is a serial port available on the CN5 connector on the board (1 - TX, 4 - RX, 6 - GND).
>
> The only functionality still not implemented is the bi-color led on
> the front panel (status). Pins mpp22 and mpp23 control this
> led. Setting mpp22 to high and mpp23 to low results in orange
> color. Setting mpp22 to low and mpp23 to high results in blue color.
Any thoughts how you are going to handle this? Can you have both blue
and orange at the same time be setting both high? Or are both then
off?
> The third led is wired to show the SATA activity on the two drives.
>
> Signed-off-by: Evgeni Dobrev <evgeni@studio-punkt.com>
> ---
> arch/arm/boot/dts/Makefile | 1 +
> arch/arm/boot/dts/kirkwood-nas220.dts | 182 +++++++++++++++++++++++++++++++++
> 2 files changed, 183 insertions(+)
> create mode 100644 arch/arm/boot/dts/kirkwood-nas220.dts
>
> diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
> index 38c89ca..8b9ad1d 100644
> --- a/arch/arm/boot/dts/Makefile
> +++ b/arch/arm/boot/dts/Makefile
> @@ -132,6 +132,7 @@ dtb-$(CONFIG_MACH_KIRKWOOD) += kirkwood-b3.dtb \
> kirkwood-lsxhl.dtb \
> kirkwood-mplcec4.dtb \
> kirkwood-mv88f6281gtw-ge.dtb \
> + kirkwood-nas220.dtb \
> kirkwood-net2big.dtb \
> kirkwood-net5big.dtb \
> kirkwood-netgear_readynas_duo_v2.dtb \
> diff --git a/arch/arm/boot/dts/kirkwood-nas220.dts b/arch/arm/boot/dts/kirkwood-nas220.dts
> new file mode 100644
> index 0000000..1de2ac3
> --- /dev/null
> +++ b/arch/arm/boot/dts/kirkwood-nas220.dts
> @@ -0,0 +1,182 @@
> +/*
> + * Device Tree file for Seagate BlackArmor NAS220
> + *
> + * Copyright (C) 2014 Evgeni Dobrev <evgeni@studio-punkt.com>
> + *
> + * Licensed under GPLv2 or later.
> + */
Gregory is in the process of changing the license for the Marvell
Armada SoCs. He is adding X11 license as well, so making it easier for
other systems to reuse the DT blob. I want to see how easy it goes
with Armada, but we may also do the same for Kirkwood sometime in the
future. So maybe you can think about this and follow the discussion.
> +
> +/dts-v1/;
> +
> +#include <dt-bindings/gpio/gpio.h>
> +#include <dt-bindings/input/input.h>
> +#include "kirkwood.dtsi"
> +#include "kirkwood-6192.dtsi"
> +
> +/ {
> + model = "Seagate NAS 220";
> + compatible = "seagate,nas220", "marvell,kirkwood-88f6192", "marvell,kirkwood";
> +
> + memory { /* 128 MB */
> + device_type = "memory";
> + reg = <0x00000000 0x8000000>;
> + };
> +
> + chosen {
> + bootargs = "console=ttyS0,115200n8";
> + stdout-path = &uart0;
> + };
It looks like there is a mix of spaces and tabs. Please only use tabs
in this file.
> +
> + ocp@f1000000 {
> + pinctrl: pin-controller@10000 {
> + pinctrl-0 = < &pmx_uart0
> + &pmx_button_reset
> + &pmx_button_power
> + >;
> + pinctrl-names = "default";
> +
> + pmx_act_sata0: pmx-act-sata0 {
> + marvell,pins = "mpp15";
> + marvell,function = "sata0";
> + };
> + pmx_act_sata1: pmx-act-sata1 {
> + marvell,pins = "mpp16";
> + marvell,function = "sata1";
> + };
> + pmx_power_sata0: pmx-power-sata0 {
> + marvell,pins = "mpp24";
> + marvell,function = "gpio";
> + };
> + pmx_power_sata1: pmx-power-sata1 {
> + marvell,pins = "mpp28";
> + marvell,function = "gpio";
> + };
> + pmx_button_reset: pmx-button-reset {
> + marvell,pins = "mpp29";
> + marvell,function = "gpio";
> + };
> + pmx_button_power: pmx-button-power {
> + marvell,pins = "mpp26";
> + marvell,function = "gpio";
> + };
> + };
> +
> + serial@12000 {
> + status = "okay";
> + };
> +
> + sata@80000 {
> + nr-ports = <2>;
> + status = "okay";
> + };
> +
> + i2c@11000 {
> + status = "okay";
> + adt7476: adt7476a@2e {
> + compatible = "adi,adt7476";
> + reg = <0x2e>;
> + };
> + };
> + };
> +
> + gpio_poweroff {
> + compatible = "gpio-poweroff";
> + gpios = <&gpio0 14 GPIO_ACTIVE_LOW>;
> + };
> +
> + gpio_keys {
> + compatible = "gpio-keys";
> +
> + button@1{
> + label = "Reset push button";
> + linux,code = <KEY_POWER>;
> + gpios = <&gpio0 29 GPIO_ACTIVE_HIGH>;
> + };
> + button@2{
> + label = "Power push button";
> + linux,code = <KEY_SLEEP>;
> + gpios = <&gpio0 26 GPIO_ACTIVE_LOW>;
> + };
> + };
> +
> + gpio-leds {
> + compatible = "gpio-leds";
> +
> + blue-power {
> + label = "nas220:blue:power";
> + gpios = <&gpio0 12 GPIO_ACTIVE_HIGH>;
> + linux,default-trigger = "default-on";
> + };
> + };
> +
> + regulators {
> + compatible = "simple-bus";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + pinctrl-0 = <&pmx_power_sata0 &pmx_power_sata1>;
> + pinctrl-names = "default";
> +
> + sata0_power: regulator@1 {
> + compatible = "regulator-fixed";
> + reg = <1>;
> + regulator-name = "SATA0 Power";
> + regulator-min-microvolt = <5000000>;
> + regulator-max-microvolt = <5000000>;
> + enable-active-high;
> + regulator-always-on;
> + regulator-boot-on;
> + gpio = <&gpio0 24 0>;
> + };
> +
> + sata1_power: regulator@2 {
> + compatible = "regulator-fixed";
> + reg = <2>;
> + regulator-name = "SATA1 Power";
> + regulator-min-microvolt = <5000000>;
> + regulator-max-microvolt = <5000000>;
> + enable-active-high;
> + regulator-always-on;
> + regulator-boot-on;
> + gpio = <&gpio0 28 0>;
> + };
> + };
> +};
> +
> +&nand {
> + status = "okay";
> + partition@0 {
> + label = "uboot";
> + reg = <0x0 0xa0000>;
> + read-only;
> + };
> +
> + partition@a0000 {
> + label = "env";
> + reg = <0xa0000 0x010000>;
> + };
Is there supposed to be a gap here?
> +
> + partition@c0000 {
> + label = "uimage";
> + reg = <0xc0000 0x500000>;
> + };
> +
> + partition@5c0000 {
> + label = "rootfs";
> + reg = <0x5c0000 0x1a40000>;
> + };
> +};
> +
> +&mdio {
> + status = "okay";
> + ethphy0: ethernet-phy@8 {
> + reg = <8>;
> + };
> +};
> +
> +ð0 {
> + status = "okay";
> + ethernet0-port@0 {
> + phy-handle = <ðphy0>;
> + };
> +};
> +
> --
Andrew
next prev parent reply other threads:[~2014-12-16 8:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 20:38 Evgeni Dobrev
2014-12-16 8:56 ` Andrew Lunn [this message]
2014-12-16 16:37 ` Evgeni Dobrev
2014-12-16 19:20 ` Andrew Lunn
2014-12-22 8:04 ` [PATCH v2 0/1] add " Evgeni Dobrev
2014-12-22 8:04 ` [PATCH v2 1/1] " Evgeni Dobrev
2014-12-22 10:02 ` Andrew Lunn
2014-12-22 12:57 ` [PATCH v3 0/1] " Evgeni Dobrev
2014-12-22 12:57 ` [PATCH v3 1/1] " Evgeni Dobrev
2014-12-23 11:31 ` Andrew Lunn
2014-12-25 13:08 ` Sebastian Hesselbarth
2014-12-25 13:31 ` Andrew Lunn
2014-12-25 13:43 ` Sebastian Hesselbarth
2014-12-25 14:12 ` Andrew Lunn
2014-12-25 15:19 ` Sebastian Hesselbarth
2014-12-26 11:06 ` Evgeni Dobrev
2014-12-28 10:46 ` [PATCH v4 0/1] " Evgeni Dobrev
2014-12-28 10:46 ` [PATCH v4 1/1] " Evgeni Dobrev
2015-01-05 18:05 ` 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=20141216085645.GB1450@lunn.ch \
--to=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=evgeni@studio-punkt.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.hesselbarth@googlemail.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
all inboxes | Powered by JetHome®