public inbox for linux-mediatek@lists.infradead.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Xiaolei Li <xiaolei.li@mediatek.com>,
	miquel.raynal@bootlin.com, richard@nod.at
Cc: linux-mediatek@lists.infradead.org,
	linux-mtd@lists.infradead.org, stable@vger.kernel.org,
	srv_heupstream@mediatek.com
Subject: Re: [PATCH v3 1/4] mtd: rawnand: mtk: Correct low level time calculation of r/w cycle
Date: Mon,  3 Jun 2019 10:04:51 +0200	[thread overview]
Message-ID: <20190603080451.28923-1-miquel.raynal@bootlin.com> (raw)
In-Reply-To: <20190507102541.34341-2-xiaolei.li@mediatek.com>

On Tue, 2019-05-07 at 10:25:38 UTC, Xiaolei Li wrote:
> At present, the flow of calculating AC timing of read/write cycle in SDR
> mode is that:
> At first, calculate high hold time which is valid for both read and write
> cycle using the max value between tREH_min and tWH_min.
> Secondly, calculate WE# pulse width using tWP_min.
> Thridly, calculate RE# pulse width using the bigger one between tREA_max
> and tRP_min.
> 
> But NAND SPEC shows that Controller should also meet write/read cycle time.
> That is write cycle time should be more than tWC_min and read cycle should
> be more than tRC_min. Obviously, we do not achieve that now.
> 
> This patch corrects the low level time calculation to meet minimum
> read/write cycle time required. After getting the high hold time, WE# low
> level time will be promised to meet tWP_min and tWC_min requirement,
> and RE# low level time will be promised to meet tREA_max, tRP_min and
> tRC_min requirement.
> 
> Fixes: edfee3619c49 ("mtd: nand: mtk: add ->setup_data_interface() hook")
> Cc: stable@vger.kernel.org # v4.17+
> Signed-off-by: Xiaolei Li <xiaolei.li@mediatek.com>
> Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>

Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git nand/next, thanks.

Miquel

  reply	other threads:[~2019-06-03  8:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07 10:25 [PATCH v3 0/4] MTK NAND driver improvements and fixes Xiaolei Li
2019-05-07 10:25 ` [PATCH v3 1/4] mtd: rawnand: mtk: Correct low level time calculation of r/w cycle Xiaolei Li
2019-06-03  8:04   ` Miquel Raynal [this message]
2019-05-07 10:25 ` [PATCH v3 2/4] mtd: rawnand: mtk: Improve data sampling timing for read cycle Xiaolei Li
     [not found]   ` <20190507102541.34341-3-xiaolei.li-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-06-03  8:04     ` Miquel Raynal
2019-05-07 10:25 ` [PATCH v3 3/4] mtd: rawnand: mtk: Add validity check for CE# pin setting Xiaolei Li
     [not found]   ` <20190507102541.34341-4-xiaolei.li-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-06-03  8:04     ` Miquel Raynal
2019-05-07 10:25 ` [PATCH v3 4/4] mtd: rawnand: mtk: Fix wrongly assigned OOB buffer pointer issue Xiaolei Li
2019-06-03  8:04   ` Miquel Raynal
     [not found] ` <20190507102541.34341-1-xiaolei.li-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-05-17  1:32   ` [PATCH v3 0/4] MTK NAND driver improvements and fixes xiaolei li
2019-05-17  8:12     ` Miquel Raynal
2019-05-17  9:21       ` xiaolei li

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=20190603080451.28923-1-miquel.raynal@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=srv_heupstream@mediatek.com \
    --cc=stable@vger.kernel.org \
    --cc=xiaolei.li@mediatek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox