From: Tom Rini <trini@konsulko.com>
To: "Kumar, Udit" <u-kumar1@ti.com>
Cc: Keerthy <j-keerthy@ti.com>,
u-boot@lists.denx.de, n-francis@ti.com, vigneshr@ti.com
Subject: Re: [PATCH RFC 10/10] board: ti: j721e: Enable ESM initialization for J7200
Date: Tue, 3 Oct 2023 11:10:33 -0400 [thread overview]
Message-ID: <20231003151033.GD8465@bill-the-cat> (raw)
In-Reply-To: <838b07a0-8490-c05b-b08f-3ab6d3e1737a@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
On Tue, Oct 03, 2023 at 07:57:04PM +0530, Kumar, Udit wrote:
>
> On 10/3/2023 1:40 PM, Keerthy wrote:
> > Enable ESM initialization for J7200
> >
> > Signed-off-by: Keerthy <j-keerthy@ti.com>
> > ---
> > board/ti/j721e/evm.c | 6 ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/board/ti/j721e/evm.c b/board/ti/j721e/evm.c
> > index 42fa94b7a5..070b28326f 100644
> > --- a/board/ti/j721e/evm.c
> > +++ b/board/ti/j721e/evm.c
> > @@ -543,7 +543,8 @@ void spl_board_init(void)
> > }
> > #ifdef CONFIG_ESM_K3
> > - if (board_ti_k3_is("J721EX-PM2-SOM")) {
> > + if ((board_ti_k3_is("J721EX-PM2-SOM")) ||
> > + IS_ENABLED(CONFIG_TARGET_J7200_R5_EVM)) {
>
>
> Could we align on one kind of check, For J721E check is done against
> board-id, whereas for J7200 checking
We should look at figuring out how to split this file in two. One for
"generic J721E systems" and one for "TI EVMs", as I've mentioned in
other threads, so that it's easier for custom platforms to drop code
they don' require.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-10-03 15:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 8:10 [PATCH RFC 00/10] arm: dts: j7200/j721s2: Enable the ESM and PMIC ESM Keerthy
2023-10-03 8:10 ` [PATCH RFC 01/10] arm64: dts: ti: k3-j721s2: Add ESM instances Keerthy
2023-10-03 8:10 ` [PATCH RFC 02/10] arm64: dts: ti: k3-j7200: Add MCU domain ESM instance Keerthy
2023-10-03 8:10 ` [PATCH RFC 03/10] arm: dts: k3-j721s2-r5-common-proc-board: Add ESM PMIC and dependent nodes Keerthy
2023-10-03 8:10 ` [PATCH RFC 04/10] arm64: dts: ti: k3-j721e: Add MCU domain ESM instance Keerthy
2023-10-03 8:10 ` [PATCH RFC 05/10] board: ti: j721e: Initialize MCU ESM Keerthy
2023-10-03 8:10 ` [PATCH RFC 06/10] board: ti: j721s2: Initialize the ESM & PMIC ESM Keerthy
2023-10-03 8:10 ` [PATCH RFC 07/10] configs: j721s2_evm_r5_defconfig: Enable ESM & PMIC ESM configs Keerthy
2023-10-03 8:10 ` [PATCH RFC 08/10] arm: dts: k3-j7200-r5-common-proc-board: Add PMIC ESM node Keerthy
2023-10-03 8:10 ` [PATCH RFC 09/10] configs: j7200_evm_r5_defconfig: Enable the ESM configs Keerthy
2023-10-03 8:10 ` [PATCH RFC 10/10] board: ti: j721e: Enable ESM initialization for J7200 Keerthy
2023-10-03 14:27 ` Kumar, Udit
2023-10-03 15:10 ` Tom Rini [this message]
2023-11-16 6:13 ` Neha Malcom Francis
2023-11-16 18:40 ` Tom Rini
2023-11-17 8:30 ` Neha Malcom Francis
2023-11-17 14:07 ` Tom Rini
2023-11-20 4:41 ` Neha Malcom Francis
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=20231003151033.GD8465@bill-the-cat \
--to=trini@konsulko.com \
--cc=j-keerthy@ti.com \
--cc=n-francis@ti.com \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@ti.com \
--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