From: Ralph Siemsen <ralph.siemsen@linaro.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-mtd@lists.infradead.org, Marek Vasut <marex@denx.de>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mtd: rawnand: denali: add more delays before latching incoming data
Date: Wed, 30 Jun 2021 14:47:41 -0400 [thread overview]
Message-ID: <20210630184741.GA1037365@maple.netwinder.org> (raw)
In-Reply-To: <20200317071821.9916-1-yamada.masahiro@socionext.com>
On Tue, Mar 17, 2020 at 04:18:21PM +0900, Masahiro Yamada wrote:
>
>Marek Vasut reported this driver in the latest kernel does not work
>on his SOCFPGA board. (The on-board NAND chip is mode 5)
In a bit of an ironic twist, this change seems to cause a regression for
me. I'm also using a Cyclone V SoC system, similar but not the same as
the SOCFPGA eval board. The NAND device in my case is S34ML04G2.
It worked fine in 4.9, 4.19 and 5.4 kernels. However after upgrading to
5.10 the NAND driver fails with "timeout while waiting for irq 0x4",
just as was reported back in 2018:
https://lore.kernel.org/linux-mtd/737ejrj81y.fsf@pengutronix.de/
Reverting commit 5756f2e8dad46eba6e2d3e530243b8eff4dd5a42 restores the
behaviour in my case, but that would presumably break the SOCFPGA board.
Any thoughts on how we could make it work for everybody?
Ralph
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2021-06-30 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 7:18 [PATCH v2] mtd: rawnand: denali: add more delays before latching incoming data Masahiro Yamada
2020-04-22 15:29 ` Marek Vasut
2020-04-22 15:36 ` Miquel Raynal
2020-04-22 15:37 ` Marek Vasut
2020-05-10 20:06 ` Miquel Raynal
2021-06-30 18:47 ` Ralph Siemsen [this message]
2021-07-04 16:00 ` Masahiro Yamada
2021-07-05 14:48 ` Ralph Siemsen
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=20210630184741.GA1037365@maple.netwinder.org \
--to=ralph.siemsen@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).