public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Brian Norris" <computersforpeace@gmail.com>
Cc: "David Woodhouse" <dwmw2@infradead.org>,
	linux-mtd@lists.infradead.org,
	"Artem Bityutskiy" <dedekind1@gmail.com>
Subject: Re: [RFC "v2"] mtd: nand: reintroduce NAND_NO_READRDY as NAND_NEED_READRDY
Date: Thu, 14 Mar 2013 11:18:23 +0400	[thread overview]
Message-ID: <1363245503.692625543@f41.mail.ru> (raw)
In-Reply-To: <1363193491-1843-1-git-send-email-computersforpeace@gmail.com>

> This (somewhat) reverts commit 1696e6bc2ae83734e64e206ac99766ea19e9a14e.
> 
> In the patch "mtd: nand: kill NAND_NO_READRDY", I overlooked a few
> things.
> 
> The original documentation for NAND_NO_READRDY included "True for all
> large page devices, as they do not support autoincrement." I was
> conflating "not support autoincrement" with the NAND_NO_AUTOINCR option,
> which was in fact doing nothing. So, when I dropped NAND_NO_AUTOINCR, I
> concluded that I then could harmlessly drop NAND_NO_READRDY. But of
> course the fact the NAND_NO_AUTOINCR was doing nothing didn't mean
> NAND_NO_READRDY was doing nothing...
> 
> So, NAND_NO_READRDY is re-introduced as NAND_NEED_READRDY and applied
> only to those few remaining small-page NAND which needed it in the first
> place.
> 
> This is probably a candidate for stable, but there will certainly be
> conflicts, as drivers/mtd/nand/nand_ids.c has changed significantly.
> 
> Compile-tested only; I don't have a setup that requires this.
> 
> Reported-by: Alexander Shiyan <shc_work@mail.ru>
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
> ---
> 
> This is an attempt at a version 2 of Alexander's RFC patch. I feel like the
> original (per NAND chip type) option makes more sense than per driver (where
> Alexander sets this option only for the diskonchip driver). But it is certainly
> more invasive. And apparently, no one else needs this option (or at least, no
> one complains). Perhaps everyone has just moved beyond small-page NAND?
...

Tested today with 3 DiskOnChip devices which contain following chips:
NAND device: Manufacturer ID: 0x98, Chip ID: 0x75 (Toshiba NAND 32MiB 3,3V 8-bit), 32MiB, page size: 512, OOB size: 16
NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND 32MiB 3,3V 8-bit), 32MiB, page size: 512, OOB size: 16
NAND device: Manufacturer ID: 0x98, Chip ID: 0xe6 (Toshiba NAND 8MiB 3,3V 8-bit), 8MiB, page size: 512, OOB size: 16

All OK. Thanks.

---

  parent reply	other threads:[~2013-03-14  7:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 16:51 [RFC "v2"] mtd: nand: reintroduce NAND_NO_READRDY as NAND_NEED_READRDY Brian Norris
2013-03-13 16:53 ` Brian Norris
2013-03-13 17:17 ` Alexander Shiyan
2013-03-14  7:18 ` Alexander Shiyan [this message]
2013-03-14 10:32   ` David Woodhouse
2013-03-14 10:41 ` Artem Bityutskiy
2013-03-14 10:51   ` David Woodhouse
2013-03-14 12:52     ` David Woodhouse
2013-03-15  7:43       ` Alexander Shiyan
2013-03-15 17:27       ` Brian Norris

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=1363245503.692625543@f41.mail.ru \
    --to=shc_work@mail.ru \
    --cc=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox