devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaud Ebalard <arno@natisbad.org>
To: Jason Cooper <jason@lakedaemon.net>,
	Gregory Clement <gregory.clement@free-electrons.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, Russell King <linux@arm.linux.org.uk>,
	Pawel Moll <pawel.moll@arm.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Rob Herring <rob.herring@calxeda.com>,
	Lior Amsalem <alior@marvell.com>, Andrew Lunn <andrew@lunn.ch>,
	Olof Johansson <olof@lixom.net>,
	linux-mtd@lists.infradead.org,
	Brian Norris <computersforpeace@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCHv0 0/3] ARM: mvebu: Enable NAND controller in NETGEAR ReadyNAS .dts files
Date: Sat, 07 Dec 2013 00:12:53 +0100	[thread overview]
Message-ID: <cover.1386370808.git.arno@natisbad.org> (raw)


Now that NAND controller support is available for Armada 370/XP
(cb28e2537a6f: ARM: mvebu: Add support for NAND controller in
Armada 370/XP), let's enable support for ReadyNAS boards.

The three commits in this series all include the partitions
definitions specific to each ReadyNAS variant as delivered
by NETGEAR with standard images.

As described in similar commits 2be2bc39c6f0 (ARM: mvebu: Enable
NAND controller in Armada XP GP board) and d8c552dddfbf (ARM: 
mvebu: Enable NAND controller in Armada 370 Mirabox),
"marvell,keep-config" parameter is used as current support does
not allow for setting of timing parameters yet.

Each patch has been tested on each specific device using Ezequiel's
tree; last known bug having being fixed today.

Jason, Ezequiel, this is a v0. I do not mind at all waiting for a
heads up to repost it later when every bit of nand support is where
it should be.

Ezequiel, I have left a comment in the .dts file to indicate a lost
reader that the last MB of last partition is in practice not
writable.

Cheers,

a+

Arnaud Ebalard (3):
  ARM: mvebu: Enable NAND controller in NETGEAR ReadyNAS 102 .dts file
  ARM: mvebu: Enable NAND controller in NETGEAR ReadyNAS 104 .dts file
  ARM: mvebu: Enable NAND controller in NETGEAR ReadyNAS 2120 .dts file

 arch/arm/boot/dts/armada-370-netgear-rn102.dts | 36 ++++++++++++++++++++++++++
 arch/arm/boot/dts/armada-370-netgear-rn104.dts | 36 ++++++++++++++++++++++++++
 arch/arm/boot/dts/armada-xp-netgear-rn2120.dts | 36 ++++++++++++++++++++++++++
 3 files changed, 108 insertions(+)

-- 
1.8.4.4

             reply	other threads:[~2013-12-06 23:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-06 23:12 Arnaud Ebalard [this message]
2013-12-06 23:13 ` [PATCHv0 2/3] ARM: mvebu: Enable NAND controller in ReadyNAS 104 .dts file Arnaud Ebalard
2013-12-06 23:13 ` [PATCHv0 1/3] ARM: mvebu: Enable NAND controller in ReadyNAS 102 " Arnaud Ebalard
2013-12-06 23:13 ` [PATCHv0 3/3] ARM: mvebu: Enable NAND controller in ReadyNAS 2120 " Arnaud Ebalard
     [not found] ` <cover.1386370808.git.arno-LkuqDEemtHBg9hUCZPvPmw@public.gmane.org>
2013-12-08  1:18   ` [PATCHv0 0/3] ARM: mvebu: Enable NAND controller in NETGEAR ReadyNAS .dts files Jason Cooper

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=cover.1386370808.git.arno@natisbad.org \
    --to=arno@natisbad.org \
    --cc=alior@marvell.com \
    --cc=andrew@lunn.ch \
    --cc=computersforpeace@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=olof@lixom.net \
    --cc=pawel.moll@arm.com \
    --cc=rob.herring@calxeda.com \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=swarren@wwwdotorg.org \
    --cc=thomas.petazzoni@free-electrons.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).