From: Quentin Schulz <quentin.schulz@cherry.de>
To: Marek Vasut <marek.vasut+renesas@mailbox.org>, u-boot@lists.denx.de
Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH v2 1/2] arm64: dts: renesas: r8a779g3: Describe generic SPI NOR support on Retronix R-Car V4H Sparrow Hawk board
Date: Mon, 11 Aug 2025 15:24:23 +0200 [thread overview]
Message-ID: <fe9042a1-20db-4011-8af7-e0eee51fab5f@cherry.de> (raw)
In-Reply-To: <20250806144727.7006-1-marek.vasut+renesas@mailbox.org>
Hi Marek,
On 8/6/25 4:47 PM, Marek Vasut wrote:
> Retronix R-Car V4H Sparrow Hawk EVTA1 is populated with Spansion S25FS512S,
> EVTB1 is populated with Winbond W77Q51NW. Describe the SPI NOR using generic
> "jedec,spi-nor" compatible, because both flashes can be auto-detected based
> on their built-in IDs.
>
> Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
> ---
> Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
> Cc: Tom Rini <trini@konsulko.com>
> Cc: u-boot@lists.denx.de
> ---
> V2: Update commit message, s@spi-flash@jedec,spi-nor@
> ---
> dts/upstream/src/arm64/renesas/r8a779g3-sparrow-hawk.dts | 6 +++++-
NACK, only cherry-picks allowed in dts/upstream. Please use
tools/update-subtree.sh after it's been merged into devicetree-rebasing
git repo (which is essentially a few things extracted from upstream Linux).
If you cannot wait, I believe you can have a companion -u-boot.dtsi
where you do the necessary changes since it'll be included after (and
thus properties take precedence if specified multiple times). Does that
work for you?
Cheers,
Quentin
prev parent reply other threads:[~2025-08-11 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 14:47 [PATCH v2 1/2] arm64: dts: renesas: r8a779g3: Describe generic SPI NOR support on Retronix R-Car V4H Sparrow Hawk board Marek Vasut
2025-08-06 14:47 ` [PATCH v2 2/2] arm64: renesas: r8a779g3: Enable Winbond " Marek Vasut
2025-08-11 13:24 ` Quentin Schulz [this message]
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=fe9042a1-20db-4011-8af7-e0eee51fab5f@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=iwamatsu@nigauri.org \
--cc=marek.vasut+renesas@mailbox.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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.