All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Dunn <mikedunn@newsguy.com>
To: linux-mtd@lists.infradead.org
Subject: Re: nand_base.c:nand_get_flash_type() test results
Date: Sun, 16 Oct 2011 07:33:26 -0700	[thread overview]
Message-ID: <4E9AEB36.7000806@newsguy.com> (raw)
In-Reply-To: <4E95B1B4.7040603@st.com>

On 10/12/2011 08:26 AM, Angus CLARK wrote:
> Hi All,
>
> While attempting to add support for some of the more recent NAND devices, I
> ended up refactoring nand_get_flash_type() code.  The refactoring was primarily
> aimed at simplifying the way in which the growing number 'READID' decoding
> exceptions could be accommodated.
>

I am currently grappling with this issue with my driver for the diskonchip G4,
which is an MLC nand under the hood, but has a proprietary controller around it
which doesn't interact as a "typical" NAND device.  Specific to this topic, it
doesn't respond to NAND_READID commands.  My solution was to skip the call to
nand_scan_ident(), which calls nand_get_flash_type().  Instead, I do all the
initializations done by nand_get_flash_type() within my driver. 

Any thoughts or suggestions appreciated.

Thanks,
Mike

  parent reply	other threads:[~2011-10-16 14:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12 15:26 nand_base.c:nand_get_flash_type() test results Angus CLARK
2011-10-14 13:57 ` Artem Bityutskiy
2011-10-14 15:14   ` Angus CLARK
2011-10-16 12:03     ` Artem Bityutskiy
2011-10-16 14:33 ` Mike Dunn [this message]
2011-10-18  7:58   ` Angus CLARK
2011-10-18 14:05     ` Mike Dunn

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=4E9AEB36.7000806@newsguy.com \
    --to=mikedunn@newsguy.com \
    --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 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.