From: Xiaolei Li <xiaolei.li@mediatek.com>
To: <boris.brezillon@free-electrons.com>, <computersforpeace@gmail.com>
Cc: <dwmw2@infradead.org>, <linux-mtd@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>, <rogercc.lin@mediatek.com>,
<srv_heupstream@mediatek.com>, <xiaolei.li@mediatek.com>
Subject: [PATCH v2] Improve MTK ECC Engine driver
Date: Mon, 30 Oct 2017 10:39:55 +0800 [thread overview]
Message-ID: <1509331196-29412-1-git-send-email-xiaolei.li@mediatek.com> (raw)
This patch-set is mainly to improve MTK ECC Engine driver, include
- remove dummy ECC IRQ disable setting
- fix infinite ECC decode IRQ issue
Changes on v2 relative to:
--------------------
tree : https://github.com/bbrezillon/linux-0day
branch : nand/next
commit :
'commit 1f3df4dc088d927683b292118cd8b4eaaf1af573
Author: Sascha Hauer <s.hauer@pengutronix.de>
Date: Mon Oct 16 11:51:55 2017 +0200'
Patch v2:
---------
- keep writel(0, ecc->regs + ECC_IRQ_REG(op)) in mtk_ecc_disable(), and
remove writel(0, ecc->regs + ECC_IRQ_REG(op)) from irq handler. It's
usually the caller who decides when the IRQ should be enabled/disable.
- add readw(ecc->regs + ECC_DECIRQ_STA) in mtk_ecc_disable() in case there
is a timeout to wait decode IRQ.
Tests:
------
* ubifs and jffs2 are validated on NAND device MT29F16G08ADBCA
by 'dd' command.
* all drivers/mtd/tests/* pass.
Xiaolei Li (1):
mtd: nand: mtk: fix infinite ECC decode IRQ issue
drivers/mtd/nand/mtk_ecc.c | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
--
1.9.1
next reply other threads:[~2017-10-30 2:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 2:39 Xiaolei Li [this message]
2017-10-30 2:39 ` [PATCH v2] mtd: nand: mtk: fix infinite ECC decode IRQ issue Xiaolei Li
2017-10-30 9:27 ` Boris Brezillon
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=1509331196-29412-1-git-send-email-xiaolei.li@mediatek.com \
--to=xiaolei.li@mediatek.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rogercc.lin@mediatek.com \
--cc=srv_heupstream@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