All of lore.kernel.org
 help / color / mirror / Atom feed
From: Huang Shijie <shijie8@gmail.com>
To: Caizhiyong <caizhiyong@hisilicon.com>
Cc: "Wanglin \(Albert\)" <albert.wanglin@hisilicon.com>,
	David Woodhouse <David.Woodhouse@intel.com>,
	Quyaxin <quyaxin@hisilicon.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Huang Shijie <b32955@freescale.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
	Brian Norris <computersforpeace@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd: increase max page/OOB size to support 16K pagesize NAND
Date: Fri, 13 Dec 2013 23:11:39 +0800	[thread overview]
Message-ID: <20131213151138.GA1316@gmail.com> (raw)
In-Reply-To: <C3050A4DBA34F345975765E43127F10F25E47537@SZXEMA512-MBX.china.huawei.com>

On Fri, Dec 13, 2013 at 11:10:10AM +0000, Caizhiyong wrote:
> 
> There are a lot of 16K page size NAND, they are used in android system.
> 
> Many NAND need read retry and data randomization, kernel does not support this feature.
Brian is adding the read-retry feature.

I think the data randomization should be done by the hardware.
If we do it by software, it costs lot of the cpu cycles.


> Kernel also does not support synchronous NAND.

The synchronous NAND should be supported by the nand controller driver,
not the kernel.


thanks
Huang Shijie

WARNING: multiple messages have this Message-ID (diff)
From: Huang Shijie <shijie8@gmail.com>
To: Caizhiyong <caizhiyong@hisilicon.com>
Cc: Brian Norris <computersforpeace@gmail.com>,
	David Woodhouse <David.Woodhouse@intel.com>,
	Quyaxin <quyaxin@hisilicon.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Huang Shijie <b32955@freescale.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
	"Wanglin (Albert)" <albert.wanglin@hisilicon.com>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd: increase max page/OOB size to support 16K pagesize NAND
Date: Fri, 13 Dec 2013 23:11:39 +0800	[thread overview]
Message-ID: <20131213151138.GA1316@gmail.com> (raw)
In-Reply-To: <C3050A4DBA34F345975765E43127F10F25E47537@SZXEMA512-MBX.china.huawei.com>

On Fri, Dec 13, 2013 at 11:10:10AM +0000, Caizhiyong wrote:
> 
> There are a lot of 16K page size NAND, they are used in android system.
> 
> Many NAND need read retry and data randomization, kernel does not support this feature.
Brian is adding the read-retry feature.

I think the data randomization should be done by the hardware.
If we do it by software, it costs lot of the cpu cycles.


> Kernel also does not support synchronous NAND.

The synchronous NAND should be supported by the nand controller driver,
not the kernel.


thanks
Huang Shijie

  reply	other threads:[~2013-12-13 15:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-13  5:03 [PATCH] mtd: increase max page/OOB size to support 16K pagesize NAND Caizhiyong
2013-12-13  5:03 ` Caizhiyong
2013-12-13  7:27 ` Huang Shijie
2013-12-13  7:27   ` Huang Shijie
2013-12-13  8:04   ` Brian Norris
2013-12-13  8:04     ` Brian Norris
2013-12-13  8:01 ` Brian Norris
2013-12-13  8:01   ` Brian Norris
2013-12-13 11:10   ` Caizhiyong
2013-12-13 11:10     ` Caizhiyong
2013-12-13 15:11     ` Huang Shijie [this message]
2013-12-13 15:11       ` Huang Shijie
2013-12-16  2:03       ` Caizhiyong
2013-12-16  2:03         ` Caizhiyong
2013-12-16  3:06         ` Huang Shijie
2013-12-16  3:06           ` Huang Shijie
2013-12-16  4:08           ` Caizhiyong
2013-12-16  4:08             ` Caizhiyong
  -- strict thread matches above, loose matches on Subject: below --
2013-12-13  5:01 Caizhiyong
2013-12-13  5:01 ` Caizhiyong
2013-12-13  7:49 ` Brian Norris
2013-12-13  7:49   ` Brian Norris

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=20131213151138.GA1316@gmail.com \
    --to=shijie8@gmail.com \
    --cc=David.Woodhouse@intel.com \
    --cc=albert.wanglin@hisilicon.com \
    --cc=artem.bityutskiy@linux.intel.com \
    --cc=b32955@freescale.com \
    --cc=caizhiyong@hisilicon.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=quyaxin@hisilicon.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.