public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: linux-renesas-soc@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org
Subject: Re: [RFC PATCH] ARM: dts: renesas: r9a06g032-rzn1d400-db: add QSPI node including NOR flash
Date: Sun, 18 Jan 2026 09:58:59 +0100	[thread overview]
Message-ID: <aWyg0wP89BCaN1tN@shikoro> (raw)
In-Reply-To: <874ioltu94.fsf@bootlin.com>

[-- Attachment #1: Type: text/plain, Size: 704 bytes --]


> > The tuning values used came from Miquel and work here as well. An
> > interested party may try to tune this further but I will go the safe
> > route here.
> 
> In case you feel adventurous, this paragraph made me remember that I had
> noted down some slightly more aggressive values related to the DB board
> (which I don't have) in some of my notes. A bit of digging resurrected
> the following:
> 
>      tshsl-ns = <30>;
>      tsd2d-ns = <3>;
>      tchsh-ns = <3>;
>      tslch-ns = <3>;

Yes, these values can be found in the BSP and could be deduced from the
SPI-NOR datasheet, too. However, I got -ETIMEDOUT with these. Didn't
investigate further (and no time to do so).


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-01-18  8:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 11:48 [RFC PATCH] ARM: dts: renesas: r9a06g032-rzn1d400-db: add QSPI node including NOR flash Wolfram Sang
2026-01-16 16:08 ` Miquel Raynal
2026-01-18  8:58   ` Wolfram Sang [this message]
2026-01-19 16:40 ` 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=aWyg0wP89BCaN1tN@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=krzk+dt@kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=robh@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox