public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Vaishnav Achath <vaishnav.a@ti.com>
To: <u-boot@lists.denx.de>, <a-govindraju@ti.com>, <vigneshr@ti.com>,
	<s-anna@ti.com>, <kishon@ti.com>, <kristo@kernel.org>,
	<j-keerthy@ti.com>, <p.yadav@ti.com>
Cc: <vaishnav.a@ti.com>
Subject: [PATCH 1/9] arm: dts: k3-j721e-mcu-wakeup: Add HyperBus Controller node
Date: Mon, 9 May 2022 11:50:09 +0530	[thread overview]
Message-ID: <20220509062017.27623-2-vaishnav.a@ti.com> (raw)
In-Reply-To: <20220509062017.27623-1-vaishnav.a@ti.com>

Add DT node for HyperBus Memory Controller and hbmc-mux in the
FSS. hbmc-am654 driver uses syscon_get_regmap() call which fails
with current compatible setting.

Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
---
 arch/arm/dts/k3-j721e-mcu-wakeup.dtsi | 20 +++++++++++++++++++-
 1 file changed, 19 insertions(+), 1 deletion(-)

diff --git a/arch/arm/dts/k3-j721e-mcu-wakeup.dtsi b/arch/arm/dts/k3-j721e-mcu-wakeup.dtsi
index d2dceda72f..22166c7942 100644
--- a/arch/arm/dts/k3-j721e-mcu-wakeup.dtsi
+++ b/arch/arm/dts/k3-j721e-mcu-wakeup.dtsi
@@ -170,12 +170,30 @@
 	};
 
 	fss: fss@47000000 {
-		compatible = "simple-bus";
+		compatible = "syscon", "simple-mfd";
 		reg = <0x0 0x47000000 0x0 0x100>;
 		#address-cells = <2>;
 		#size-cells = <2>;
 		ranges;
 
+		hbmc_mux: hbmc-mux {
+			compatible = "mmio-mux";
+			#mux-control-cells = <1>;
+			mux-reg-masks = <0x4 0x2>; /* HBMC select */
+		};
+
+		hbmc: hyperbus@47034000 {
+			compatible = "ti,j721e-hbmc", "ti,am654-hbmc";
+			reg = <0x0 0x47034000 0x0 0x100>,
+				<0x5 0x00000000 0x1 0x0000000>;
+			power-domains = <&k3_pds 102 TI_SCI_PD_EXCLUSIVE>;
+			#address-cells = <2>;
+			#size-cells = <1>;
+			mux-controls = <&hbmc_mux 0>;
+			assigned-clocks = <&k3_clks 102 0>;
+			assigned-clock-rates = <250000000>;
+		};
+
 		ospi0: spi@47040000 {
 			compatible = "ti,am654-ospi", "cdns,qspi-nor";
 			reg = <0x0 0x47040000 0x0 0x100>,
-- 
2.17.1


  reply	other threads:[~2022-05-09 12:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09  6:20 [PATCH 0/9] j721e: Add HyperFlash boot support Vaishnav Achath
2022-05-09  6:20 ` Vaishnav Achath [this message]
2022-06-10 21:39   ` [PATCH 1/9] arm: dts: k3-j721e-mcu-wakeup: Add HyperBus Controller node Tom Rini
2022-05-09  6:20 ` [PATCH 2/9] arm: dts: k3-j721e-som-p0: Add HyperFlash node Vaishnav Achath
2022-05-09  6:20 ` [PATCH 3/9] arm: dts: k3-j721e-r5-common-proc-board: " Vaishnav Achath
2022-05-09  6:20 ` [PATCH 4/9] arm: dts: k3-j721e-common-proc-board-u-boot: enable HyperFlash in SPL Vaishnav Achath
2022-05-09  6:20 ` [PATCH 5/9] arm: dts: k3-j721e-common-proc-board: enable hyperflash mux sel GPIO Vaishnav Achath
2022-05-09  6:20 ` [PATCH 6/9] arm: k3: sysfw-loader: add hyperflash support Vaishnav Achath
2022-05-09  6:20 ` [PATCH 7/9] configs: j721e_evm.h: define CONFIG_SYS_FLASH_BASE Vaishnav Achath
2022-05-09  6:20 ` [PATCH 8/9] ti: j721e: enable hyperflash spl fixup for j721e Vaishnav Achath
2022-05-09  6:20 ` [PATCH 9/9] configs: j721e_evm_defconfig: Add HBMC related configs Vaishnav Achath

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=20220509062017.27623-2-vaishnav.a@ti.com \
    --to=vaishnav.a@ti.com \
    --cc=a-govindraju@ti.com \
    --cc=j-keerthy@ti.com \
    --cc=kishon@ti.com \
    --cc=kristo@kernel.org \
    --cc=p.yadav@ti.com \
    --cc=s-anna@ti.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