From: Daniel Schultz <d.schultz@phytec.de>
To: <w.egorov@phytec.de>, <trini@konsulko.com>, <u-boot@lists.denx.de>
Cc: <d-gole@ti.com>, <upstream@lists.phytec.de>,
Daniel Schultz <d.schultz@phytec.de>
Subject: [PATCH 2/2] board: phytec: common: k3: Expose product infos to Linux
Date: Fri, 8 Nov 2024 10:19:14 -0800 [thread overview]
Message-ID: <20241108181914.3358114-2-d.schultz@phytec.de> (raw)
In-Reply-To: <20241108181914.3358114-1-d.schultz@phytec.de>
Call 'phytec_ft_board_fixup' in the common K3 board code
to expose the product name and part number to Linux.
Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
---
board/phytec/common/k3/board.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/board/phytec/common/k3/board.c b/board/phytec/common/k3/board.c
index 3d7e090ccaa..14a10f34e53 100644
--- a/board/phytec/common/k3/board.c
+++ b/board/phytec/common/k3/board.c
@@ -99,8 +99,22 @@ int board_late_init(void)
#if IS_ENABLED(CONFIG_OF_LIBFDT) && IS_ENABLED(CONFIG_OF_BOARD_SETUP)
int ft_board_setup(void *blob, struct bd_info *bd)
{
+ struct phytec_eeprom_data data;
+ int ret;
+
fdt_copy_fixed_partitions(blob);
+ ret = phytec_eeprom_data_setup(&data, 0, EEPROM_ADDR);
+ if (ret || !data.valid)
+ return 0;
+
+ ret = phytec_ft_board_fixup(&data, blob, bd);
+ if (ret) {
+ pr_err("%s: Failed to add PHYTEC information to fdt.\n",
+ __func__);
+ return 0;
+ }
+
return 0;
}
#endif
--
2.25.1
next prev parent reply other threads:[~2024-11-08 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 18:19 [PATCH 1/2] board: phytec: common: Add product information to FTD Daniel Schultz
2024-11-08 18:19 ` Daniel Schultz [this message]
2024-11-11 8:20 ` [PATCH 2/2] board: phytec: common: k3: Expose product infos to Linux Wadim Egorov
2024-11-11 8:35 ` [PATCH 1/2] board: phytec: common: Add product information to FTD Wadim Egorov
2025-01-15 10:36 ` Daniel Schultz
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=20241108181914.3358114-2-d.schultz@phytec.de \
--to=d.schultz@phytec.de \
--cc=d-gole@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=upstream@lists.phytec.de \
--cc=w.egorov@phytec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox