All of lore.kernel.org
 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>, Andrew Davis <afd@ti.com>
Subject: [PATCH v5 1/4] board: ti: am64x: Recognize AM64-HSEVM
Date: Sat,  5 Aug 2023 11:14:37 +0300	[thread overview]
Message-ID: <20230805081440.7045-2-rogerq@kernel.org> (raw)
In-Reply-To: <20230805081440.7045-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>
Reviewed-by: Nishanth Menon <nm@ti.com>
Tested-by: Nishanth Menon <nm@ti.com> #SK-AM64B
---
 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-08-05  8:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-05  8:14 [PATCH v5 0/4] arm: dts: k3-am64: Sync DT with Linux Roger Quadros
2023-08-05  8:14 ` Roger Quadros [this message]
2023-08-05  8:14 ` [PATCH v5 2/4] Revert "ARM: dts: k3-am642-sk-u-boot: add PMIC node" Roger Quadros
2023-08-05  8:14 ` [PATCH v5 3/4] doc: board: ti: am64: Add boot flow diagram Roger Quadros
2023-08-05  8:14 ` [PATCH v5 4/4] arm: dts: k3-am64: Sync DT with Linux v6.5-rc1 Roger Quadros
2023-08-05 16:29   ` Nishanth Menon
2023-08-17 19:18 ` [PATCH v5 0/4] arm: dts: k3-am64: Sync DT with Linux Tom Rini

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=20230805081440.7045-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 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.