From: Alexander Clouter <alex@digriz.org.uk>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: plat_nand: add further DT bindings and documentation
Date: Sun, 21 Apr 2013 11:49:20 +0100 [thread overview]
Message-ID: <20130421104920.GR2917@edkhil> (raw)
In-Reply-To: <20130329225353.GQ7123@edkhil>
Bueller?
On Fri, Mar 29, 2013 at 10:53:53PM +0000, Alexander Clouter wrote:
>Anyone with any suggestions on what should be done with this patch?
>For my DT platform porting, is it okay for me to continue making use
>of this work? Or is there a plan to kill plat-nand?
>
>I am suspecting folks are aghast with horror at the thought of having
>plat-nand breeding with devicetree?
>
>On Sun, Mar 24, 2013 at 11:27:33AM +0000, Alexander Clouter wrote:
>>The plat_nand driver has some devicetree support but it is currently
>>unusable, especially as there is no documentation on how to use it.
>>
>>This patch adds the much needed documentation as well as adds some common
>>properties (bank-width, chip-delay, bbt-use-flash and nr-chips) removing
>>further use of the platform_nand_data struct.
>>
>>Signed-off-by: Alexander Clouter <alex@digriz.org.uk>
>>---
>>.../devicetree/bindings/mtd/plat-nand.txt | 93 ++++++++++++++++++++
>>drivers/mtd/nand/plat_nand.c | 53 ++++++++---
>>2 files changed, 134 insertions(+), 12 deletions(-)
--
Alexander Clouter
.sigmonster says: Even moderation ought not to be practiced to excess.
next prev parent reply other threads:[~2013-04-21 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 11:27 [PATCH] mtd: plat_nand: add further DT bindings and documentation Alexander Clouter
2013-03-27 9:59 ` Ezequiel Garcia
2013-03-27 12:44 ` Alexander Clouter
2013-03-29 22:53 ` Alexander Clouter
2013-04-21 10:49 ` Alexander Clouter [this message]
2013-05-10 11:34 ` Artem Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2013-03-23 22:06 Alexander Clouter
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=20130421104920.GR2917@edkhil \
--to=alex@digriz.org.uk \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@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