From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Duc Nguyen <duc.nguyen.ub@renesas.com>,
Sergey Shtylyov <s.shtylyov@omp.ru>,
"Lad, Prabhakar" <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Andrew Gabbasov <andrew_gabbasov@mentor.com>
Subject: Re: [RFC PATCH] memory: renesas-rpc-if: Correct QSPI data transfer in Manual mode
Date: Tue, 8 Mar 2022 09:21:29 +0100 [thread overview]
Message-ID: <YicSCZfl4wLUzvEJ@shikoro> (raw)
In-Reply-To: <CAMuHMdUqQLo7=NFaNEukqniTJbx-mSZv7eQNB9eCT=L28y3u=A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 478 bytes --]
> Wolfram: which platform did you use for QSPI testing, so I don't
> break that again?
I did my refactoring using an Eagle board and once this worked, I
enabled QSPI on Falcon. All remotely. Condor was another candidate but
it was broken in the lab at that time.
> Without that (e.g. old H3 R-Car ES1.0), it crashes with an
Frankly, I wouldn't trust ES1.0 as a reliable source for QSPI. Could you
start with the newest Gen3 board you have and then go to previous ones?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-03-08 8:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 9:10 [RFC PATCH] memory: renesas-rpc-if: Correct QSPI data transfer in Manual mode Wolfram Sang
2021-09-24 11:09 ` Krzysztof Kozlowski
2021-09-24 12:35 ` Wolfram Sang
2021-09-27 8:51 ` Lad, Prabhakar
2021-09-27 9:45 ` Geert Uytterhoeven
2021-09-27 19:50 ` Lad, Prabhakar
2021-09-27 20:10 ` Wolfram Sang
2021-09-28 9:46 ` Krzysztof Kozlowski
2021-09-28 10:31 ` Wolfram Sang
2021-09-28 10:35 ` Krzysztof Kozlowski
2022-03-07 16:44 ` Geert Uytterhoeven
2022-03-07 17:47 ` Krzysztof Kozlowski
2022-03-07 18:11 ` Geert Uytterhoeven
2022-03-08 8:21 ` Wolfram Sang [this message]
2022-03-08 8:29 ` Geert Uytterhoeven
2022-03-08 8:46 ` Wolfram Sang
2022-03-08 9:01 ` Geert Uytterhoeven
2022-03-11 16:55 ` Geert Uytterhoeven
2022-04-27 10:22 ` Geert Uytterhoeven
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=YicSCZfl4wLUzvEJ@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=andrew_gabbasov@mentor.com \
--cc=duc.nguyen.ub@renesas.com \
--cc=geert@linux-m68k.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=s.shtylyov@omp.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.