From: Deepak Saxena <dsaxena@plexity.net>
To: "Ruslan V. Sushko" <rsushko@ru.mvista.com>
Cc: tglx@linutronix.de, linux-mtd@lists.infradead.org
Subject: Re: [PATH] NAND Flash support for Intel IXP4xx platform
Date: Wed, 2 May 2007 09:03:59 -0700 [thread overview]
Message-ID: <20070502160359.GA21292@plexity.net> (raw)
In-Reply-To: <46359C8A.4040306@ru.mvista.com>
On Apr 30 2007, at 11:36, Ruslan V. Sushko was caught saying:
> Thomas,
>
> I have tried to fit driver's functionality into common platform
> structures. Unfortunately the device hasn't NAND controller and some
> signals (ALE/CLE(pins on data bus) and CS(gpio)) are driven in custom
> way. Current platform structures have not enough fields to carry
> platform dependent data for this driver without hack (I guess use fields
> not used in driver but designed for other things is not good idea).
> Additionally due to device haven't NAND controller future version of
> board may change the way which is used to drive CS signal, So I move
> this functionality completely to hardware dependent part of driver (sent
> to LAKML)
Can't that extra functionality be stuffed into a structure that you
point to via the priv member of platform_nand_chip?
~Deepak
--
Deepak Saxena - dsaxena@plexity.net - http://www.plexity.net
In the end, they will not say, "those were dark times," they will ask
"why were their poets silent?" - Bertolt Brecht
next prev parent reply other threads:[~2007-05-02 17:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 11:41 [PATH] NAND Flash support for Intel IXP4xx platform Ruslan V. Sushko
2007-04-28 12:33 ` David Woodhouse
2007-04-28 13:32 ` Ruslan V. Sushko
2007-04-28 12:35 ` Thomas Gleixner
2007-04-28 13:42 ` Ruslan V. Sushko
2007-04-28 21:02 ` Thomas Gleixner
2007-04-30 7:36 ` Ruslan V. Sushko
2007-04-30 8:17 ` Thomas Gleixner
2007-04-30 8:24 ` Vitaly Wool
2007-05-02 16:03 ` Deepak Saxena [this message]
2007-05-02 18:09 ` Vitaly Wool
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=20070502160359.GA21292@plexity.net \
--to=dsaxena@plexity.net \
--cc=linux-mtd@lists.infradead.org \
--cc=rsushko@ru.mvista.com \
--cc=tglx@linutronix.de \
/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.