All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert ARIBAUD (3ADEV) <albert.aribaud@3adev.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mtd: nand: vf610_nfc: resync with upstream Linux version
Date: Wed, 14 Oct 2015 13:21:41 +0200	[thread overview]
Message-ID: <20151014132141.088492da@lilith> (raw)
In-Reply-To: <1444799502-20472-1-git-send-email-stefan@agner.ch>

Hello Stefan,

On Tue, 13 Oct 2015 22:11:42 -0700, Stefan Agner <stefan@agner.ch>
wrote:
> This resyncs the driver changes with the Linux version of the
> driver. The driver received some feedback in the LKML and got
> recently acceppted, the latest version can be found here:
> https://lkml.org/lkml/2015/9/2/678
> 
> Notable changes are:
> - On ECC error, reread OOB and count bit flips in OOB too.
>   If flipped bits are below threshold, also return an empty
>   OOB buffer.
> - Return the amount of bit flips in vf610_nfc_read_page.
> - Use endianness aware vf610_nfc_read to read ECC status.
> - Do not enable IDLE IRQ (since we do not operate with an
>   interrupt service routine).
> - Use type safe struct for buffer variants (vf610_nfc_alt_buf).
> - Renamed variables in struct vf610_nfc (column and page_sz)
>   to reflect better what they really representing.
> 
> The U-Boot version currently does not support RAW NAND write
> when using the HW ECC engine.
> 
> Signed-off-by: Bhuvanchandra DV <bhuvanchandra.dv@toradex.com>
> Signed-off-by: Stefan Agner <stefan@agner.ch>

Tested-by: Albert ARIBAUD (3ADEV) <albert.aribaud@3adev.fr>

Works on pcm052.

Amicalement,
-- 
Albert.

  parent reply	other threads:[~2015-10-14 11:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14  5:11 [U-Boot] [PATCH] mtd: nand: vf610_nfc: resync with upstream Linux version Stefan Agner
2015-10-14  8:43 ` Albert ARIBAUD
2015-10-14  8:51   ` Albert ARIBAUD
2015-10-14 11:21 ` Albert ARIBAUD [this message]
2015-10-14 11:27   ` Albert ARIBAUD
2015-10-15  4:00     ` Scott Wood
2015-10-15  8:13       ` Stefano Babic
2015-10-14 16:19   ` Stefan Agner

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=20151014132141.088492da@lilith \
    --to=albert.aribaud@3adev.fr \
    --cc=u-boot@lists.denx.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.