From: dima@android.com (Dima Zavin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/2] mtd: nand: Allow NAND chip ids to be included standalone.
Date: Wed, 6 Apr 2011 23:28:37 -0700 [thread overview]
Message-ID: <BANLkTimWFiKmvAi+9OeEsdZyP91599ibSw@mail.gmail.com> (raw)
In-Reply-To: <1299542935-20291-1-git-send-email-mnalajal@codeaurora.org>
Acked-by: Dima Zavin <dima@android.com>
On Mon, Mar 7, 2011 at 4:08 PM, Murali Nalajala <mnalajal@codeaurora.org> wrote:
> Lets non-standard NAND drivers take advantage of known NAND
> chip information.
>
> The initial development of msm nand driver, driver uses the supported
> NAND devices information as a hardcoded table. Remove the existing
> hardcoded supported flash device table and read the flash device
> information from the flash id table which are part of the mtd subsystem.
>
> Signed-off-by: Dima Zavin <dima@android.com>
> Signed-off-by: Murali Nalajala <mnalajal@codeaurora.org>
> ---
> Changes in V2
> * Add more description to the commit text.
>
> ?drivers/mtd/nand/Kconfig | ? 10 +++++++---
> ?1 files changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/mtd/nand/Kconfig b/drivers/mtd/nand/Kconfig
> index c895922..782275e 100644
> --- a/drivers/mtd/nand/Kconfig
> +++ b/drivers/mtd/nand/Kconfig
> @@ -1,3 +1,10 @@
> +config MTD_NAND_IDS
> + ? ? ? tristate "Include chip ids for known NAND devices."
> + ? ? ? depends on MTD
> + ? ? ? help
> + ? ? ? ? Useful for NAND drivers that do not use the NAND subsystem but
> + ? ? ? ? still like to take advantage of the known chip information.
> +
> ?config MTD_NAND_ECC
> ? ? ? ?tristate
>
> @@ -123,9 +130,6 @@ config MTD_NAND_OMAP_PREFETCH_DMA
> ? ? ? ? or in DMA interrupt mode.
> ? ? ? ? Say y for DMA mode or MPU mode will be used
>
> -config MTD_NAND_IDS
> - ? ? ? tristate
> -
> ?config MTD_NAND_RICOH
> ? ? ? ?tristate "Ricoh xD card reader"
> ? ? ? ?default n
> --
> 1.7.1.1
>
> --
> Sent by a consultant of the Qualcomm Innovation Center, Inc.
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
>
>
next prev parent reply other threads:[~2011-04-07 6:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 0:08 [PATCH V2 1/2] mtd: nand: Allow NAND chip ids to be included standalone Murali Nalajala
2011-03-08 7:50 ` Artem Bityutskiy
2011-03-08 17:41 ` Murali Nalajala
2011-03-21 6:39 ` Murali Nalajala
2011-03-21 7:12 ` Artem Bityutskiy
2011-03-21 7:58 ` Murali Nalajala
2011-03-22 6:41 ` Murali Nalajala
2011-03-22 8:11 ` Artem Bityutskiy
2011-04-06 4:38 ` Murali Nalajala
2011-04-06 7:21 ` Artem Bityutskiy
2011-04-07 6:28 ` Dima Zavin [this message]
2011-04-14 23:33 ` David Brown
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=BANLkTimWFiKmvAi+9OeEsdZyP91599ibSw@mail.gmail.com \
--to=dima@android.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).