From: Semih Hazar <semih.hazar@indefia.com>
To: "Vladimir A. Barinov" <vbarinov@ru.mvista.com>
Cc: linux-mtd@lists.infradead.org, vitalywool@gmail.com
Subject: Re: Generic Platform NAND Driver
Date: Tue, 22 May 2007 14:53:06 +0300 [thread overview]
Message-ID: <4652D9A2.6020607@indefia.com> (raw)
In-Reply-To: <4652D1C8.4050305@ru.mvista.com>
Vladimir A. Barinov wrote:
>>
>> +ixdp425_flash_nand_cmd_ctrl(struct mtd_info *mtd, int cmd, unsigned
>> int ctrl)
>> +{
>> + struct nand_chip *this = mtd->priv;
>> + int offset = (int)this->priv;
>>
>> Here offset is read from nand_chip->priv, which actually points to
>> struct plat_nand_data of plat_nand.c
>>
>> Am I wrong ?
> I agree with you.
> And you are right that all things work fine because the
> mtd_info->priv->priv that points to plat_nand_data is not used.
>
> I agree that the line 54 in plat_nand.c should be removed:
>
> - data->chip.priv = &data;
>
>
> But does it really usefull to create void * host pointer if it could
> be done in arch code like the above patch does?
I thought board-specific code can make use of this area (just as in your
patch) so it's good to be able pass some _known_ data there.
My code which uses generic nand and is very much like the patch you've
sent. But we may have board specific CLE, ACE, CE pins so they're not
#define'd in the machine code, rather they're passed in a struct from
the board code. And I thought the right thing to so that would be to
pass that data to the priv member rather than accessing it in a static way.
If it's better to access have these board-specific in a static manner,
then I'll just go ahead and change my code that way.
Thanks for your feedback.
Regards,
--
Semih Hazar
prev parent reply other threads:[~2007-05-22 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 12:15 Generic Platform NAND Driver Semih Hazar
2007-05-22 9:08 ` Semih Hazar
2007-05-22 9:48 ` Vladimir A. Barinov
2007-05-22 10:28 ` Semih Hazar
2007-05-22 11:19 ` Vladimir A. Barinov
2007-05-22 11:53 ` Semih Hazar [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=4652D9A2.6020607@indefia.com \
--to=semih.hazar@indefia.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vbarinov@ru.mvista.com \
--cc=vitalywool@gmail.com \
/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).