[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YicX67PsQO0+bMTZ@shikoro>
Date: Tue, 8 Mar 2022 09:46:35 +0100
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
Duc Nguyen <duc.nguyen.ub@...esas.com>,
Sergey Shtylyov <s.shtylyov@....ru>,
"Lad, Prabhakar" <prabhakar.mahadev-lad.rj@...renesas.com>,
Andrew Gabbasov <andrew_gabbasov@...tor.com>
Subject: Re: [RFC PATCH] memory: renesas-rpc-if: Correct QSPI data transfer
in Manual mode
> This is not QSPI, but HF.
Ah, okay.
> Building a new firmware for R-Car H3 ES1.0 with HF unlocked will be
> complicated, as it is not supported by upstream TF-A.
You mean QSPI here?
> Note that HF also fails to probe on R-Car M3-W and M3-N ES1.0.
Do you have this patch form Andrew in your tree:
[PATCH] memory: renesas-rpc-if: Avoid unaligned bus access for HyperFlash
Even if so, I don't think that reverting patches is the solution. As you
could see from Andrew's patch, HyperFlash was also broken before and it
just may need more fixes for Gen3 perhaps? IIRC my patches didn't break
Andrew's tests but maybe we should ask him again. Maybe Andrew has also
some more ideas, I only did QSPI.
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists