public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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>
Subject: [PATCH v2 1/2] board: ti: am64x: Recognize AM64-HSEVM
Date: Mon, 31 Jul 2023 15:27:36 +0300	[thread overview]
Message-ID: <20230731122737.36316-2-rogerq@kernel.org> (raw)
In-Reply-To: <20230731122737.36316-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>
---
 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


  reply	other threads:[~2023-07-31 12:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 12:27 [PATCH v2 0/2] arm: dts: k3-am6: Sync DT with Linux Roger Quadros
2023-07-31 12:27 ` Roger Quadros [this message]
2023-07-31 14:20   ` [PATCH v2 1/2] board: ti: am64x: Recognize AM64-HSEVM Andrew Davis
2023-07-31 12:27 ` [PATCH v2 2/2] arm: dts: k3-am64: Sync DT with Linux v6.5-rc1 Roger Quadros
2023-08-01 12:36   ` Nishanth Menon
2023-08-01 13:04   ` Nishanth Menon
2023-07-31 15:16 ` [PATCH v2 0/2] arm: dts: k3-am6: Sync DT with Linux Roger Quadros
2023-08-01 12:37 ` Nishanth Menon
2023-08-01 13:20   ` Roger Quadros
2023-08-02 21:12 ` 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=20230731122737.36316-2-rogerq@kernel.org \
    --to=rogerq@kernel.org \
    --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