All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-spi@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] spi: sh-msiof: Enforce fixed DTDL for R-Car H3
Date: Thu, 26 Jan 2023 14:26:53 +0100	[thread overview]
Message-ID: <CAMuHMdXRBYhR+_+r+akZ5nKYPgpVKMNEHB5KCP_pnPJYtHvU=A@mail.gmail.com> (raw)
In-Reply-To: <Y9J6+uoXxUIs4Bkk@ninjato>

Hi Wolfram,

On Thu, Jan 26, 2023 at 2:07 PM Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> > > Documentation says only DTDL of 200 is allowed for this SoC.
> >
> > Do you have a pointer to that?
>
> Yes: Gen3 docs Rev.2.30 from Aug 2021, Section 59.2.1, Bits 22-20:
>
> "[R-Car H3, R-Car H3-N]
> 010: 2-clock-cycle delay
> Other than above: Setting prohibited"

Oops, I looked at the 59.2.4, which describes the receive equivalent,
and which does not have this limitations.

> > We already have "renesas,dtdl" to configure this from DT.
> > Iff this is really needed, perhaps it should be added to r8a77951.dtsi?
>
> I have to disagree here. The docs say that other values are prohibited.
> IMO the driver should take care of valid values then. We should not rely
> on user provided input.

Then we should make sure the user cannot override to an invalid value
through "renesas,dtdl" either?

> > I suspect this is a leftover in the BSP from attempts to get MSIOF
> > working on R-Car H3 ES1.0 (which it never did for me, as CLK starts
> > and stops too soon, compared to MOSI/MISO).
> > On R-Car H3 ES2.0, everything works fine, without touching DTDL.
>
> The BSP originally has this patch for ES3 only. I extended to ES2 as
> well because that is what the docs say.

This limitation appeared in Hardware User's Manual rev. 1.50, which
is also the first version to document R-Car H3-N.
So I wouldn't be surprised if this applies to R-Car H3(-N) ES3.0 only.
Remember that rev.0.53 was the switching point from R-Car H3
ES1.0 to ES2.0.
To be clarified with Renesas?

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

  reply	other threads:[~2023-01-26 13:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24  7:47 [PATCH] spi: sh-msiof: Enforce fixed DTDL for R-Car H3 Wolfram Sang
2023-01-26  9:57 ` Geert Uytterhoeven
2023-01-26 13:07   ` Wolfram Sang
2023-01-26 13:26     ` Geert Uytterhoeven [this message]
2023-01-26 13:40       ` Wolfram Sang
2023-01-26 13:43         ` Geert Uytterhoeven
2023-02-15  8:02         ` Geert Uytterhoeven
2023-02-16  2:59 ` Yoshihiro Shimoda

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='CAMuHMdXRBYhR+_+r+akZ5nKYPgpVKMNEHB5KCP_pnPJYtHvU=A@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.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 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.