From: Roger Quadros <rogerq@kernel.org>
To: trini@konsulko.com
Cc: nm@ti.com, vigneshr@ti.com, srk@ti.com, r-gunasekaran@ti.com,
s-vadapalli@ti.com, u-boot@lists.denx.de,
Roger Quadros <rogerq@kernel.org>, Andrew Davis <afd@ti.com>
Subject: [PATCH v4 1/4] board: ti: am64x: Recognize AM64-HSEVM
Date: Thu, 3 Aug 2023 19:06:47 +0300 [thread overview]
Message-ID: <20230803160650.167279-2-rogerq@kernel.org> (raw)
In-Reply-To: <20230803160650.167279-1-rogerq@kernel.org>
AM64-HSEVM is AM64-GPEVM with High Security Device.
Gets rid of "Unidentified board claims AM64-HSEVM in eeprom header".
Signed-off-by: Roger Quadros <rogerq@kernel.org>
Acked-by: Andrew Davis <afd@ti.com>
---
board/ti/am64x/evm.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/board/ti/am64x/evm.c b/board/ti/am64x/evm.c
index 96f4e3013a..a080b2b0d2 100644
--- a/board/ti/am64x/evm.c
+++ b/board/ti/am64x/evm.c
@@ -18,7 +18,8 @@
#include "../common/board_detect.h"
-#define board_is_am64x_gpevm() board_ti_k3_is("AM64-GPEVM")
+#define board_is_am64x_gpevm() (board_ti_k3_is("AM64-GPEVM") || \
+ board_ti_k3_is("AM64-HSEVM"))
#define board_is_am64x_skevm() (board_ti_k3_is("AM64-SKEVM") || \
board_ti_k3_is("AM64B-SKEVM"))
--
2.34.1
next prev parent reply other threads:[~2023-08-03 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 16:06 [PATCH v4 0/4] arm: dts: k3-am64: Sync DT with Linux Roger Quadros
2023-08-03 16:06 ` Roger Quadros [this message]
2023-08-04 11:18 ` [PATCH v4 1/4] board: ti: am64x: Recognize AM64-HSEVM Nishanth Menon
2023-08-03 16:06 ` [PATCH v4 2/4] Revert "ARM: dts: k3-am642-sk-u-boot: add PMIC node" Roger Quadros
2023-08-04 11:19 ` Nishanth Menon
2023-08-03 16:06 ` [PATCH v4 3/4] doc: board: ti: am64: Add boot flow diagram Roger Quadros
2023-08-04 11:22 ` Nishanth Menon
2023-08-03 16:06 ` [PATCH v4 4/4] arm: dts: k3-am64: Sync DT with Linux v6.5-rc1 Roger Quadros
2023-08-04 11:23 ` Nishanth Menon
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=20230803160650.167279-2-rogerq@kernel.org \
--to=rogerq@kernel.org \
--cc=afd@ti.com \
--cc=nm@ti.com \
--cc=r-gunasekaran@ti.com \
--cc=s-vadapalli@ti.com \
--cc=srk@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox