Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1392491 > unrolled thread

Re: [RFC PATCH 0/2] mtd: nand: add manafacturer specific handling

Started byRichard Weinberger <richard.weinberger@gmail.com>
First post2016-05-02 22:10 +0200
Last post2016-05-02 22:10 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [RFC PATCH 0/2] mtd: nand: add manafacturer specific handling Richard Weinberger <richard.weinberger@gmail.com> - 2016-05-02 22:10 +0200

#1392491 — Re: [RFC PATCH 0/2] mtd: nand: add manafacturer specific handling

FromRichard Weinberger <richard.weinberger@gmail.com>
Date2016-05-02 22:10 +0200
SubjectRe: [RFC PATCH 0/2] mtd: nand: add manafacturer specific handling
Message-ID<ruski-1EO-11@gated-at.bofh.it>
On Mon, Feb 24, 2014 at 6:29 PM, Boris BREZILLON
<b.brezillon.dev@gmail.com> wrote:
> Hello,
>
> This is a proposal to add support for manufacturer specific handling of
> NAND chips.
>
> Currently the only ones allowed to modify how NAND chips are accessed are
> NAND controllers (by modifying the nand_chip callbacks) and NAND core code
> (by setting default callbacks when these are not specified by the NAND
> controller).
>
> This series adds support for manufacturer/vendor specific handling, which is
> particularly useful for read retry implementation that are (at least for
> the moment) manufacturer specific.
>
> I know there was a debate on how we should support all these READ RETRY
> implementations (see http://permalink.gmane.org/gmane.linux.drivers.mtd/50603),
> so please tell if I'm wrong.

Just realized that this got no feedback at all.
Brian?

-- 
Thanks,
//richard

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web