From: "Gadiyar, Anand" <gadiyar@ti.com>
To: "Achath, Vaishnav" <vaishnav.a@ti.com>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
"trini@konsulko.com" <trini@konsulko.com>
Cc: "Raghavendra, Vignesh" <vigneshr@ti.com>,
"Menon, Nishanth" <nm@ti.com>, "Kumar, Udit" <u-kumar1@ti.com>
Subject: RE: [PATCH 0/2] arm: dts: J721E Hyperbus Fixes
Date: Thu, 30 Mar 2023 17:43:47 +0000 [thread overview]
Message-ID: <9d858d65db784c0cbb3ef76237fc287d@ti.com> (raw)
In-Reply-To: <20230330174005.24950-1-vaishnav.a@ti.com>
> From: Achath, Vaishnav <vaishnav.a@ti.com>
>
> J721E SoC has a hyperbus controller and OSPI controller muxed and only
> one of the controllers should be active at a time
>
> While enabling support for hyperflash in J721E, the hyperbus controller
> was enabled by default in SoC DTS and was kept disabled in board DTS.
> For J721E SK, the board level DTS does not disable the hyperbus node
> which causes OSPI and Hyperbus controllers to be active at the same time
> thus causing boot failure on J721E SK, to avoid situations like this keep
> the hyperbus controller disabled by default in SoC DTS. Also the fixups for
> hyperflash enable according to DIP switch settings on EVM is relevant only
> to J721E EVM and J7200 EVM, thus disable those fixups for other platforms.
>
> Since the hyperbus node is not present in kernel DTS, manual update is
> needed to fix the issue( J721E SK Boot failure). J721E SK boot failure
> needs additional fixes on the board DTS which will be sent separately,
> but hyperbus and OSPI controller being active was also one of the issues
> causing boot failure.
>
> Changes were tested on J721E EVM and J721E SK for basic boot and hyperflash
> functionality(EVM).
>
> Vaishnav Achath (2):
> arm: dts: k3-j721e-mcu-wakeup: Disable hyperbus controller node
> board: ti: j721e: Disable hyperflash fixup for J721E SK
>
> arch/arm/dts/k3-j721e-mcu-wakeup.dtsi | 1 +
> board/ti/j721e/evm.c | 6 ++++++
> 2 files changed, 7 insertions(+)
>
For what it's worth, these were independently tested by me on both J721e EVM
and SK boards off the v2023.04-rc5 tag.
An additional patchset is needed for the SK board to boot - it seems to have
been broken since at least March 2022, if not earlier. I'll send that out shortly.
Tested-by: Anand Gadiyar <gadiyar@ti.com>
prev parent reply other threads:[~2023-03-30 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 17:40 [PATCH 0/2] arm: dts: J721E Hyperbus Fixes Vaishnav Achath
2023-03-30 17:40 ` [PATCH 1/2] arm: dts: k3-j721e-mcu-wakeup: Disable hyperbus controller node Vaishnav Achath
2023-03-30 18:50 ` Nishanth Menon
2023-03-30 17:40 ` [PATCH 2/2] board: ti: j721e: Disable hyperflash fixup for J721E SK Vaishnav Achath
2023-03-30 17:43 ` Gadiyar, Anand [this message]
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=9d858d65db784c0cbb3ef76237fc287d@ti.com \
--to=gadiyar@ti.com \
--cc=nm@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@ti.com \
--cc=vaishnav.a@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 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.