From: "Ruslan V. Sushko" <rsushko@ru.mvista.com>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATH] NAND Flash support for Intel IXP4xx platform
Date: Mon, 30 Apr 2007 11:36:42 +0400 [thread overview]
Message-ID: <46359C8A.4040306@ru.mvista.com> (raw)
In-Reply-To: <1177794151.7646.312.camel@localhost.localdomain>
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)
Thank you,
Ruslan
Thomas Gleixner wrote:
> Ruslan,
>
> On Sat, 2007-04-28 at 17:42 +0400, Ruslan V. Sushko wrote:
>
>>> How excatly is this functionally different from the generic write_buf
>>> function in nand_base.c ?
>>>
>>>
>> This function should be removed. It was different for originally. ALE
>> and CLE signal assertion was herre, but I decide this functionality is
>> not necessary for data writing, so I've remove that, but forget to check
>> remainder with generic code.
>>
>
> I did a review and pointed this out. No need for lengthy explanaitions.
> Just remove it.
>
>
>>> Aside of that I agree with Lennert, that we really need to get around
>>> and make this real platform code.
>>>
>>>
>> Sorry don't understand
>> Do you propose to move all these (especially hw_ctrl function)
>> functionality to platform/arch code?
>>
>
> That's what Lennert said. And I agree. Many of the drivers just differ
> in the hardware control function and the pyhsical address where the
> device is located.
>
> We have already platform support for NAND:
>
> See include/linux/mtd/nand.h:
>
> struct platform_nand_chip / struct platform_nand_ctrl
>
> As far as I can tell, there is everything covered what you need for a
> generic platform driver.
>
> Again. Lennert is right and another post of your driver does not change
> anything unless you listen to his and my advise.
>
> tglx
>
>
>
next prev parent reply other threads:[~2007-04-30 7:36 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 [this message]
2007-04-30 8:17 ` Thomas Gleixner
2007-04-30 8:24 ` Vitaly Wool
2007-05-02 16:03 ` Deepak Saxena
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=46359C8A.4040306@ru.mvista.com \
--to=rsushko@ru.mvista.com \
--cc=linux-mtd@lists.infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox