From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Sekhar Nori <nsekhar@ti.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
<linux-mtd@lists.infradead.org>, <linux-omap@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, "Cooper Jr.,
Franklin" <fcooper@ti.com>,
Murali Karicheri <m-karicheri2@ti.com>
Subject: Re: [PATCH] mtd: davinci-nand: disable subpage write for davinci-nand
Date: Tue, 3 Jan 2017 14:13:46 +0100 [thread overview]
Message-ID: <20170103141346.5e652afe@bbrezillon> (raw)
In-Reply-To: <e51292a6-15a5-ce5b-da7b-dbd22ede38b6@ti.com>
Hi Sekhar,
On Tue, 3 Jan 2017 17:07:44 +0530
Sekhar Nori <nsekhar@ti.com> wrote:
> Hi Boris,
>
> On Tuesday 03 January 2017 02:29 PM, Boris Brezillon wrote:
> > Hi Sushaanth,
>
> Sushaanth is not with TI anymore. You might have received a bounce.
Indeed.
>
> >
> > Sorry for the late reply, I'm dequeing old NAND related patches and
> > found this one.
> >
> > Is this patch still needed?
>
> I dont think so. I suspect the real root cause was addressed by Karl in
> commit f6d7c1b5598b ("mtd: nand: davinci: Reinitialize the HW ECC
> engine in 4bit hwctl")
Okay, cool. I'll just mark the patch as 'Superseeded' in patchwork.
>
> I just ran mtd_subpagetest on my da850 lcdk board and it passed[1]. If
> there are more tests to run to determine if subpage write really works,
> let me know too.
No, that should be good.
>
> I suspect even the original workaround for keystone boards may not be
> needed after Karl's patch. I will test and send a patch dropping the
> workaround altogether if the tests succeed.
Sounds good.
Thanks,
Boris
prev parent reply other threads:[~2017-01-03 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 9:08 [PATCH] mtd: davinci-nand: disable subpage write for davinci-nand Sushaanth Srirangapathi
2017-01-03 8:59 ` Boris Brezillon
2017-01-03 11:37 ` Sekhar Nori
2017-01-03 13:13 ` Boris Brezillon [this message]
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=20170103141346.5e652afe@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=fcooper@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=nsekhar@ti.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