All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gupta, Pekon" <pekon@ti.com>
To: David Jander <david.jander@protonic.nl>,
	Brian Norris <computersforpeace@gmail.com>
Cc: Ted Juan <ted.juan@gmail.com>,
	"sjhill@realitydiluted.com" <sjhill@realitydiluted.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	David Woodhouse <dwmw2@infradead.org>
Subject: RE: [FRC] [PATCH] MTD: nand_base.c: Enable support for Samsung E-die SLC NAND
Date: Mon, 30 Jun 2014 11:06:39 +0000	[thread overview]
Message-ID: <20980858CB6D3A4BAE95CA194937D5E73EAF856A@DBDE04.ent.ti.com> (raw)
In-Reply-To: <20140625141133.247d62a3@archvile>

Hi David,

>From: David Jander [mailto:david.jander@protonic.nl]
[...]
>
>P.S.: Anyone care to give comment on my patch? Not that you two effectively
>hijacked this thread for only slightly tangentially related issues... ;-)
>
Sorry for diverting from the main patch discussion, somehow I'm unable to
find the original PATCH email from mtd-list.
As per Samsung Device (K9F1G08U0E) datasheet, which is
"1Gb E-die SLC NAND Flash". This device support 'Random Input' (0x85) command.
This means driver can change the column-address during page-program
operation and write to any partial page in between. Isn't that sufficient
to support subpage writes ?

Earlier implementation of nand_write_subpage_hwecc() has some limitations,
I have recently sent a patch-series [1] which uses alternate approach, can you
check if subpage writes work with this.
Also which controller driver are you using for this device ? There may be some
controller limitation too, prohibiting use of subpages.


with regards, pekon

[1] http://lists.infradead.org/pipermail/linux-mtd/2014-June/054446.html

  reply	other threads:[~2014-06-30 11:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20 10:12 [FRC] [PATCH] MTD: nand_base.c: Enable support for Samsung E-die SLC NAND David Jander
2014-06-22 12:06 ` Ted Juan
2014-06-23  4:05   ` Gupta, Pekon
2014-06-23  8:15     ` Ted Juan
2014-06-25  6:17       ` Ted Juan
2014-06-25 10:04         ` Gupta, Pekon
2014-06-25 11:31           ` David Jander
2014-06-25 11:55             ` Gupta, Pekon
2014-06-25 12:11               ` David Jander
2014-06-30 11:06                 ` Gupta, Pekon [this message]
2014-06-26  4:02           ` Ted Juan
2014-06-27  9:13             ` Ted Juan
2014-06-27 10:03               ` Gupta, Pekon

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=20980858CB6D3A4BAE95CA194937D5E73EAF856A@DBDE04.ent.ti.com \
    --to=pekon@ti.com \
    --cc=computersforpeace@gmail.com \
    --cc=david.jander@protonic.nl \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=sjhill@realitydiluted.com \
    --cc=ted.juan@gmail.com \
    --cc=tglx@linutronix.de \
    /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.