From: arno@natisbad.org (Arnaud Ebalard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mvebu: Add Netgear ReadyNAS 104 board
Date: Tue, 22 Oct 2013 21:13:54 +0200 [thread overview]
Message-ID: <8738ntqft9.fsf@natisbad.org> (raw)
In-Reply-To: <52668F35.9050203@free-electrons.com> (Gregory CLEMENT's message of "Tue, 22 Oct 2013 15:44:05 +0100")
Hi Gregory,
Gregory CLEMENT <gregory.clement@free-electrons.com> writes:
> On 21/10/2013 22:02, Arnaud Ebalard wrote:
>>
>> Main hardware parts of the (Armada 370 based) NETGEAR ReadyNAS 104 are
>> supported by mainline kernel (USB 3.0 rear ports, USB 2.0 front port,
>> Gigabit controller and PHYs, serial port, LEDs, buttons, SATA ports,
>> G762 fan controller) and referenced in provided .dts file. Some additonal
>> work remains for:
>>
>> - Intersil ISL12057 I2C RTC and Alarm chip: working driver but needs
>> to be splitted for submission of RTC part first;
>> - Front LCD (Winstar 1602G): driver needs to be written
>> - Armada NAND controller (to access onboard 128MB of NAND): support
>> being pushed by @free-electrons people
>> - 4 front SATA LEDs controlled via GPIO brought by NXP PCA9554:
>> driver is available upstream. Not referenced/tested yet.
>>
>> but the device is usable w/o those.
>>
>> Signed-off-by: Arnaud Ebalard <arno@natisbad.org>
>> ---
>> Jason and Andrew,
>>
>> I do not think there is any good way to share much between RN102 and
>> RN104 .dts in a common .dtsi file because MPP are used in a different
>> fashion on the two boards. But if you have ideas ...
>
> It seems to me that you can share at least half of the nodes in a common
> dtsi. But I prefer having two dts files, it remains easier to understand.
> Latter if a 3rd board share the same amount of nodes, then we can
> consider to use a dtsi.
Dully noted. AFAICT, NETGEAR only has 2 Armada 370 based devices at the
moment: the 2-bay RN102 and the 4-bay RN104. FWIW, the only other
ARM-based NAS in their portfolio is the ReadyNAS 2120 (Dual core Armada
XP @1.2GHz).
Cheers,
a+
WARNING: multiple messages have this Message-ID (diff)
From: arno-LkuqDEemtHBg9hUCZPvPmw@public.gmane.org (Arnaud Ebalard)
To: Gregory CLEMENT
<gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Cc: Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>,
Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
Sebastian Hesselbarth
<sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
Ian Campbell
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] ARM: mvebu: Add Netgear ReadyNAS 104 board
Date: Tue, 22 Oct 2013 21:13:54 +0200 [thread overview]
Message-ID: <8738ntqft9.fsf@natisbad.org> (raw)
In-Reply-To: <52668F35.9050203-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org> (Gregory CLEMENT's message of "Tue, 22 Oct 2013 15:44:05 +0100")
Hi Gregory,
Gregory CLEMENT <gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org> writes:
> On 21/10/2013 22:02, Arnaud Ebalard wrote:
>>
>> Main hardware parts of the (Armada 370 based) NETGEAR ReadyNAS 104 are
>> supported by mainline kernel (USB 3.0 rear ports, USB 2.0 front port,
>> Gigabit controller and PHYs, serial port, LEDs, buttons, SATA ports,
>> G762 fan controller) and referenced in provided .dts file. Some additonal
>> work remains for:
>>
>> - Intersil ISL12057 I2C RTC and Alarm chip: working driver but needs
>> to be splitted for submission of RTC part first;
>> - Front LCD (Winstar 1602G): driver needs to be written
>> - Armada NAND controller (to access onboard 128MB of NAND): support
>> being pushed by @free-electrons people
>> - 4 front SATA LEDs controlled via GPIO brought by NXP PCA9554:
>> driver is available upstream. Not referenced/tested yet.
>>
>> but the device is usable w/o those.
>>
>> Signed-off-by: Arnaud Ebalard <arno-LkuqDEemtHBg9hUCZPvPmw@public.gmane.org>
>> ---
>> Jason and Andrew,
>>
>> I do not think there is any good way to share much between RN102 and
>> RN104 .dts in a common .dtsi file because MPP are used in a different
>> fashion on the two boards. But if you have ideas ...
>
> It seems to me that you can share at least half of the nodes in a common
> dtsi. But I prefer having two dts files, it remains easier to understand.
> Latter if a 3rd board share the same amount of nodes, then we can
> consider to use a dtsi.
Dully noted. AFAICT, NETGEAR only has 2 Armada 370 based devices at the
moment: the 2-bay RN102 and the 4-bay RN104. FWIW, the only other
ARM-based NAS in their portfolio is the ReadyNAS 2120 (Dual core Armada
XP @1.2GHz).
Cheers,
a+
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-10-22 19:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 21:02 [PATCH] ARM: mvebu: Add Netgear ReadyNAS 104 board Arnaud Ebalard
2013-10-21 21:02 ` Arnaud Ebalard
2013-10-21 21:57 ` Andrew Lunn
2013-10-21 21:57 ` Andrew Lunn
2013-10-22 16:02 ` Andrew Lunn
2013-10-22 16:02 ` Andrew Lunn
2013-10-22 14:44 ` Gregory CLEMENT
2013-10-22 14:44 ` Gregory CLEMENT
2013-10-22 19:13 ` Arnaud Ebalard [this message]
2013-10-22 19:13 ` Arnaud Ebalard
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=8738ntqft9.fsf@natisbad.org \
--to=arno@natisbad.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.