public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Sameer <x0081444@ti.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] - NAND - Samsung LP nand feature support - nand_base.c upated
Date: Tue, 22 Apr 2008 16:09:32 +0100	[thread overview]
Message-ID: <1208876972.9212.611.camel@pmac.infradead.org> (raw)
In-Reply-To: <00ed01c84ee5$b4928e40$ec8818ac@ent.ti.com>

On Fri, 2008-01-04 at 20:53 +0530, Sameer wrote:
> Hi,
> This patch add the Large page NAND feature support for Samsung nand flash.
> 
> Regards,
> -Sameer
> 
> 
> Signed-off-by: Sameer U <sameersu@ti.com>
> ---
>  drivers/mtd/nand/nand_base.c |    4 ++++
>  1 files changed, 4 insertions(+)
> 
> Index: linux-omap-git/drivers/mtd/nand/nand_base.c
> ===================================================================
> --- linux-omap-git.orig/drivers/mtd/nand/nand_base.c
> +++ linux-omap-git/drivers/mtd/nand/nand_base.c
> @@ -2322,6 +2322,10 @@ static struct nand_flash_dev *nand_get_f
> 	chip->options &= ~NAND_CHIPOPTIONS_MSK;
> 	chip->options |= type->options & NAND_CHIPOPTIONS_MSK;
> 
> +	/* adding feature support for large page samsung nand */
> +	if ((*maf_id == NAND_MFR_SAMSUNG) && (mtd->writesize > 512))
> +		chip->options |= NAND_SAMSUNG_LP_OPTIONS;
> +

This doesn't seem to make sense. These chips have the options bit set in
the ID table by default, and we mask them _out_ for non-Samsung chips.

Which chip are you using, and why isn't it working as intended?

-- 
dwmw2

      reply	other threads:[~2008-04-22 15:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-04 15:23 [PATCH] - NAND - Samsung LP nand feature support - nand_base.c upated Sameer
2008-04-22 15:09 ` David Woodhouse [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=1208876972.9212.611.camel@pmac.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=x0081444@ti.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