From: Scott Wood <scottwood@freescale.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Marek Vasut <marek.vasut@gmail.com>,
linux-mtd@lists.infradead.org,
Huang Shijie <b32955@freescale.com>
Subject: Re: GPMI-NAND: Wrong ECC size in driver
Date: Tue, 31 Jan 2012 13:09:13 -0600 [thread overview]
Message-ID: <4F283C59.2050800@freescale.com> (raw)
In-Reply-To: <4F282519.5020802@gmail.com>
On 01/31/2012 11:30 AM, Brian Norris wrote:
> There's another distinct possibility (one that I use on an out-of-tree
> driver): instead of calling "nand_scan()", separate it into its two
> sub-functions "nand_scan_ident()" and "nand_scan_tail()" so you have
> something like this
>
> ret = nand_scan_ident(mtd, pdata->max_chip_count, NULL);
> chip->options |= NAND_NO_SUBPAGE_WRITE;
> if (!ret)
> ret = nand_scan_tail(mtd);
>
> That way your option is set after we mask with NAND_CHIPOPTIONS_MSK. I'm
> not sure if this solution is better than really trying to tackle the
> issue of why we have that mask and whether it is still needed, but it
> solves the problem.
It's a bit hackish, but should work. Why not get just rid of the mask,
though, if it's not actually doing anything constructive and is
requiring such workarounds?
-Scott
next prev parent reply other threads:[~2012-01-31 19:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 0:48 GPMI-NAND: Wrong ECC size in driver Marek Vasut
2012-01-04 5:58 ` Huang Shijie
2012-01-04 17:30 ` Scott Wood
2012-01-04 21:32 ` Marek Vasut
2012-01-04 21:48 ` Scott Wood
2012-01-04 23:38 ` Marek Vasut
2012-01-04 23:48 ` Scott Wood
2012-01-31 11:33 ` Marek Vasut
2012-01-31 17:30 ` Brian Norris
2012-01-31 19:09 ` Scott Wood [this message]
2012-02-03 2:43 ` Brian Norris
2012-02-03 3:16 ` Brian Norris
2012-01-04 21:33 ` Marek Vasut
2012-01-05 2:08 ` Huang Shijie
2012-01-05 9:07 ` Marek Vasut
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=4F283C59.2050800@freescale.com \
--to=scottwood@freescale.com \
--cc=b32955@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@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 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.