From: jm@lentin.co.uk (Jamie Lentin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 0/3] ARM: Kirkwood: Convert DNS-325 & DNS-320 to access nand via devicetree (was: Add support for DNS-320 and DNS-325 using devicetree)
Date: Sat, 31 Mar 2012 14:53:02 +0100 [thread overview]
Message-ID: <1333201985-2222-1-git-send-email-jm@lentin.co.uk> (raw)
Right, I've stopped being lazy and researched what the various properties
contain and documented them.
In the process I noticed that all other drivers have bank-width in bytes,
so I changed orion_nand to match. If using orion_nand without devicetree,
the width property is still in bits though. Hopefully this isn't considered too
bad? They have different names at least.
I've left out everything that has been merged into either Grant or Jason's
tree. Hopefully this was a useful thing to do.
Thanks again to everyone reviewing.
Changes since v3: Add support for DNS-320 and DNS-325 using devicetree
* Remove patches that are already merged
* Add documentation on orion_nand devicetree bindings
* Convert bank-width to be in bytes to match other properties
* Make defaults more explicit
Changes since v2: Add support for DNS-320 and DNS-325 using devicetree
* Split patches further, separating orion_nand and kirkwood changes
* dts renames: "bank-width", not "width". "okay", not "ok"
* Separate documentation out into separate patch, add references to
partition.txt to all mtd bindings.
Changes since v1: Add support for DNS-320 and DNS-325 using devicetree
* Rebase against kirkwood_dt_for_3.4, removing premature devicetree ports.
* Move additions into a separate board-dnskw.c. It could be separated further
into a board-dns320.c and board-dns325.c but it probably isn't worth it.
* s/marvell,/mrvl,/g
* Include an example dtb partition in documentation
* Copy structure of serial nodes to allow common options for NAND to be set
in kirkwood.dtsi
* Simplifications in orion-nand.c
Jamie Lentin (3):
mtd: Add orion_nand devicetree bindings
kirkwood: Allow nand to be configured via. devicetree
ARM: kirkwood: Define DNS-320/DNS-325 NAND in fdt
.../devicetree/bindings/mtd/orion-nand.txt | 50 ++++++++++++++++++++
arch/arm/boot/dts/kirkwood-dns320.dts | 35 ++++++++++++++
arch/arm/boot/dts/kirkwood-dns325.dts | 35 ++++++++++++++
arch/arm/boot/dts/kirkwood.dtsi | 15 ++++++-
arch/arm/mach-kirkwood/board-dnskw.c | 31 ------------
arch/arm/mach-kirkwood/common.c | 12 +++++
drivers/mtd/nand/orion_nand.c | 41 +++++++++++++++-
7 files changed, 185 insertions(+), 34 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mtd/orion-nand.txt
--
1.7.9.1
next reply other threads:[~2012-03-31 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 13:53 Jamie Lentin [this message]
2012-03-31 13:53 ` [PATCH V4 1/3] mtd: Add orion_nand devicetree bindings Jamie Lentin
2012-04-05 21:12 ` [PATCH V4.1 " Jamie Lentin
2012-03-31 13:53 ` [PATCH V4 2/3] kirkwood: Allow nand to be configured via. devicetree Jamie Lentin
2012-03-31 13:53 ` [PATCH V4 3/3] ARM: kirkwood: Define DNS-320/DNS-325 NAND in fdt Jamie Lentin
2012-03-31 18:12 ` [PATCH V4 0/3] ARM: Kirkwood: Convert DNS-325 & DNS-320 to access nand via devicetree (was: Add support for DNS-320 and DNS-325 using devicetree) 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=1333201985-2222-1-git-send-email-jm@lentin.co.uk \
--to=jm@lentin.co.uk \
--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).