All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Stigge <stigge@antcom.de>
To: dedekind1@gmail.com
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"Gupta, Pekon" <pekon@ti.com>
Subject: Re: [PATCH] mtd: nand: subpage write support for hardware based ECC schemes
Date: Fri, 05 Apr 2013 14:56:12 +0200	[thread overview]
Message-ID: <515EC9EC.5030200@antcom.de> (raw)
In-Reply-To: <1365158617.626.29.camel@sauron.fi.intel.com>

On 04/05/2013 12:43 PM, Artem Bityutskiy wrote:
> On Fri, 2013-04-05 at 09:07 +0000, Gupta, Pekon wrote:
>>  > You need to update cafe_nand.c accordingly. Aiaiai detected this:
>>>
>>> Artem Bityutskiy
>>
>> Thanks Aiaiai, Artem, 
> 
> Roland, heads up, I am going to apply this patch to the MTD tree. It
> touches your driver.

Tested-by: Roland Stigge <stigge@antcom.de>

Thanks for the note! (Sorry, haven't followed this issue.)

Works fine so far. As far as I understand it, there is only an interface
change regarding LPC32xx - subpage writing isn't officially supported by
this controller hardware (with >=2k pages + ecc applied to 512 byte
"subpages" - not the real subpages as reported by the flash chip).

So I guess it's ok to ignore the new "uint32_t offset, int data_len"
arguments in lpc32xx_write_page.

Roland

  reply	other threads:[~2013-04-05 12:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15 12:59 [PATCH] mtd: nand: subpage write support for hardware based ECC schemes Gupta, Pekon
2013-03-15 13:15 ` Matthieu CASTET
2013-03-15 18:11   ` Gupta, Pekon
2013-03-18 15:42     ` Matthieu CASTET
2013-03-25  4:17       ` Gupta, Pekon
2013-03-27  8:44 ` Gupta, Pekon
2013-04-04 15:16 ` Artem Bityutskiy
2013-04-05  9:07   ` Gupta, Pekon
2013-04-05 10:43     ` Artem Bityutskiy
2013-04-05 12:56       ` Roland Stigge [this message]
2013-04-05 10:44     ` Artem Bityutskiy

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=515EC9EC.5030200@antcom.de \
    --to=stigge@antcom.de \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pekon@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 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.