All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yixun Lan <dlan@kernel.org>
To: Bruno Banelli <bbanelli@gmail.com>
Cc: Huan Zhou <pericycle.cc@gmail.com>,
	Guodong Xu <guodong.xu@oss.qualcomm.com>,
	Tom Rini <trini@konsulko.com>,
	u-boot-spacemit@groups.io, u-boot@lists.u-boot-project.org
Subject: Re: [PATCH] board: spacemit: k1: accept the "m1-x_" TLV product name prefix
Date: Tue, 25 Aug 2026 22:44:18 +0000	[thread overview]
Message-ID: <20260825224418-GKC631715@kernel.org> (raw)
In-Reply-To: <20260825065257.69536-1-bbanelli@gmail.com>

Hi Bruno,
 Cc Guodong's new mail address

On 08:52 Tue 25 Aug     , Bruno Banelli wrote:
> board_fit_config_name_match() derives the device tree name from the TLV
> product name held in the board EEPROM, and only recognises boards whose
> product name starts with "k1-x_".
> 
> Boards fitted with the higher-binned M1 part report an "m1-x_" prefix
> instead.  On those, fdt_name is left empty and the function silently
> falls back to "k1-musepi-pro", so an M1 board selects the wrong device
> tree with no error or warning.
> 
> A Milk-V Jupiter fitted with an M1 reads, from the 24c04 at i2c2 0x50:
> 
>   00: 54 6c 76 49 6e 66 6f 00 01 00 1a 21 12 6d 31 2d  TlvInfo....!.m1-
>   10: 78 5f 6d 69 6c 6b 76 2d 6a 75 70 69 74 65 72 fe  x_milkv-jupiter.
> 
> i.e. TLV code 0x21 (product name), length 0x12, "m1-x_milkv-jupiter".
> 
> The device trees are named for the K1 in both cases, so accept either
> prefix and keep deriving a "k1-" name.
> 
> Signed-off-by: Bruno Banelli <bbanelli@gmail.com>

Looks good
Reviewd-by: Yixun Lan <dlan@kernel.org>


-- 
Yixun Lan (dlan)

  reply	other threads:[~2026-08-25 22:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25  6:52 [PATCH] board: spacemit: k1: accept the "m1-x_" TLV product name prefix Bruno Banelli
2026-08-25 22:44 ` Yixun Lan [this message]
2026-08-25 22:50   ` Yixun Lan

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=20260825224418-GKC631715@kernel.org \
    --to=dlan@kernel.org \
    --cc=bbanelli@gmail.com \
    --cc=guodong.xu@oss.qualcomm.com \
    --cc=pericycle.cc@gmail.com \
    --cc=trini@konsulko.com \
    --cc=u-boot-spacemit@groups.io \
    --cc=u-boot@lists.u-boot-project.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 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.