Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20200317071821.9916-1-yamada.masahiro@socionext.com> <20210630184741.GA1037365@maple.netwinder.org>
In-Reply-To: <20210630184741.GA1037365@maple.netwinder.org>
From:   Masahiro Yamada <masahiroy@kernel.org>
Date:   Mon, 5 Jul 2021 01:00:43 +0900
Message-ID: <CAK7LNASvYVyEQ4M_zEUdw9K9AB-RVErKoqFMQZ5OSKJF0AoBww@mail.gmail.com>
Subject: Re: [PATCH v2] mtd: rawnand: denali: add more delays before latching
 incoming data
To:     Ralph Siemsen <ralph.siemsen@linaro.org>
Cc:     linux-mtd <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 Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, Jul 1, 2021 at 3:47 AM Ralph Siemsen <ralph.siemsen@linaro.org> wrote:
>
> 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


I no longer have any hardware to test this driver.

If you increase data_setup_on_host (the current value is 10000),
will it solve your issue?


-- 
Best Regards
Masahiro Yamada