From: Wolfgang Grandegger <wg@grandegger.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [NAND] driver extension to support NAND on TQM85xx modules
Date: Fri, 30 May 2008 15:57:10 +0200 [thread overview]
Message-ID: <484007B6.2070300@grandegger.com> (raw)
In-Reply-To: <8B8CFD8C-8F18-4548-A07B-5748BAD1ACEA@kernel.crashing.org>
Kumar Gala wrote:
>
> On May 30, 2008, at 1:36 AM, Wolfgang Grandegger wrote:
>
>> This patch extends the FSL UPM NAND driver from Anton Vorontsov to
>> support for the TQM85xx modules. Unfortunately, the hardware does
>> not support the R/B pins of the NAND chip and therefore the specified
>> maximum delay time must used. It therefore re-introduces the chip-delay
>> property.
>>
>> Note: this patch is based on a patch Anton Vorontsov posted to this list:
>> See http://ozlabs.org/pipermail/linuxppc-dev/2008-April/055587.html.
>> It should show up mainstream soon.
>>
>> Signed-off-by: Wolfgang Grandegger <wg@grandegger.com>
>> ---
>> drivers/mtd/nand/Kconfig | 2 +-
>> drivers/mtd/nand/fsl_upm.c | 30 +++++++++++++++++++++---------
>> include/linux/of_gpio.h | 2 +-
>> 3 files changed, 23 insertions(+), 11 deletions(-)
>
> You really need to CC the MTD list as this should go via them. Also
> you're adding a new property and there should be updates to
> booting-w-o-f for it.
OK. There are various patches pending for booting-w-o-f including
"[PATCH 6/7] [POWERPC] booting-without-of: add FHCI USB, FSL MCU,
FSL UPM and GPIO LEDs bindings" from Anton. What tree should the patches
for NAND and 85xx be based on for kernel inclusion?
Wolfgang.
prev parent reply other threads:[~2008-05-30 13:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 6:36 [PATCH] [NAND] driver extension to support NAND on TQM85xx modules Wolfgang Grandegger
2008-05-30 12:50 ` Anton Vorontsov
2008-06-04 9:52 ` Wolfgang Grandegger
2008-06-04 11:58 ` Anton Vorontsov
2008-05-30 13:07 ` Kumar Gala
2008-05-30 13:57 ` Wolfgang Grandegger [this message]
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=484007B6.2070300@grandegger.com \
--to=wg@grandegger.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=galak@kernel.crashing.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.