From: Wolfgang Grandegger <wg@grandegger.com>
To: linux-mtd@lists.infradead.org, linuxppc-dev@ozlabs.org
Subject: [PATCH v2 0/5] NAND: Multi-chip support for FSL-UPM for TQM8548 modules
Date: Thu, 19 Mar 2009 16:16:03 +0100 [thread overview]
Message-ID: <1237475768-11481-1-git-send-email-wg@grandegger.com> (raw)
This is the 2nd version of the patch series adding generic support for
multi-chip NAND devices to the FSL-UPM driver and support for the
Micron MT29F8G08FAB NAND flash memory on the TQM8548 modules. It
addresses the issues reported on the mailing list, e.g. the new
bindings are now documented:
[PATCH v2 1/5] NAND: FSL-UPM: add multi chip support
[PATCH v2 2/5] NAND: FSL-UPM: add support for selecting chips via MAR
[PATCH v2 3/5] NAND: FSL-UPM: Add wait flags to support board/chip specific delays
[PATCH v2 4/5] powerpc: NAND: FSL UPM: document new bindings
[PATCH v2 5/5] powerpc/85xx: TQM8548: Update DTS file for multi-chip support
Please consider these patches for kernel inclusion.
Thanks.
Wolfgang.
next reply other threads:[~2009-03-19 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 15:16 Wolfgang Grandegger [this message]
2009-03-19 15:16 ` [PATCH v2 1/5] NAND: FSL-UPM: add multi chip support Wolfgang Grandegger
2009-03-19 15:16 ` [PATCH v2 2/5] NAND: FSL-UPM: add support for selecting chips via MAR Wolfgang Grandegger
2009-03-19 15:16 ` [PATCH v2 3/5] NAND: FSL-UPM: Add wait flags to support board/chip specific delays Wolfgang Grandegger
2009-03-19 15:16 ` [PATCH v2 4/5] powerpc: NAND: FSL UPM: document new bindings Wolfgang Grandegger
2009-03-19 15:16 ` [PATCH v2 5/5] powerpc/85xx: TQM8548: Update DTS file for multi-chip support Wolfgang Grandegger
2009-03-19 17:05 ` [PATCH v2 4/5] powerpc: NAND: FSL UPM: document new bindings Scott Wood
2009-03-24 18:59 ` Wolfgang Grandegger
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=1237475768-11481-1-git-send-email-wg@grandegger.com \
--to=wg@grandegger.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.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).