lkml.org 
[lkml]   [2022]   [Mar]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: [RFC PATCH] memory: renesas-rpc-if: Correct QSPI data transfer in Manual mode
    Hi Wolfram,

    On Tue, Mar 8, 2022 at 9:21 AM Wolfram Sang
    <wsa+renesas@sang-engineering.com> wrote:
    > > 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.

    OK, thanks!

    > > 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?

    This is not QSPI, but HF.

    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.

    Note that HF also fails to probe on R-Car M3-W and M3-N ES1.0.
    Haven't tried it on R-Car E3 yet. All those have a (not so new) TF-A,
    but built with RCAR_RPC_HYPERFLASH_LOCKED=0.

    Gr{oetje,eeting}s,

    Geert

    --
    Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

    In personal conversations with technical people, I call myself a hacker. But
    when I'm talking to journalists I just say "programmer" or something like that.
    -- Linus Torvalds

    \
     
     \ /
      Last update: 2022-03-08 09:31    [W:3.354 / U:0.056 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site