From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 27518C761A6 for ; Thu, 30 Mar 2023 18:51:06 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 558A685A33; Thu, 30 Mar 2023 20:51:03 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=quarantine dis=none) header.from=ti.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (1024-bit key; unprotected) header.d=ti.com header.i=@ti.com header.b="pZk0fE9N"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id D4FF585A33; Thu, 30 Mar 2023 20:50:59 +0200 (CEST) Received: from lelv0142.ext.ti.com (lelv0142.ext.ti.com [198.47.23.249]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id ADC84856B2 for ; Thu, 30 Mar 2023 20:50:55 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=quarantine dis=none) header.from=ti.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=nm@ti.com Received: from lelv0265.itg.ti.com ([10.180.67.224]) by lelv0142.ext.ti.com (8.15.2/8.15.2) with ESMTP id 32UIorkP082472; Thu, 30 Mar 2023 13:50:53 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1680202253; bh=ABh2IT2nMIzrPGFpwiMmv3a8ehYsdRQIwUEfh7d3dp8=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=pZk0fE9N/Dvi0yX+VFLHW/rs94GS1KjEw9PIz9LmT8VRFZL283ntP+qBX0M9iqrSN r79aMi0jbkb1BC79Lgf0F2JYGPnVMoLAmgBsAPk2xXAjpuhWLjNIS8ezbpo6xoEM+J xymIHdniRFxly5BVpcwzFs//eWannXv1Z8ify6dI= Received: from DLEE108.ent.ti.com (dlee108.ent.ti.com [157.170.170.38]) by lelv0265.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 32UIorlK021288 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 30 Mar 2023 13:50:53 -0500 Received: from DLEE113.ent.ti.com (157.170.170.24) by DLEE108.ent.ti.com (157.170.170.38) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.16; Thu, 30 Mar 2023 13:50:53 -0500 Received: from fllv0039.itg.ti.com (10.64.41.19) by DLEE113.ent.ti.com (157.170.170.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.16 via Frontend Transport; Thu, 30 Mar 2023 13:50:53 -0500 Received: from localhost (ileaxei01-snat.itg.ti.com [10.180.69.5]) by fllv0039.itg.ti.com (8.15.2/8.15.2) with ESMTP id 32UIorYf082532; Thu, 30 Mar 2023 13:50:53 -0500 Date: Thu, 30 Mar 2023 13:50:53 -0500 From: Nishanth Menon To: Vaishnav Achath CC: , , , , Subject: Re: [PATCH 1/2] arm: dts: k3-j721e-mcu-wakeup: Disable hyperbus controller node Message-ID: <20230330185053.3ouehfhxkbf7drer@geometric> References: <20230330174005.24950-1-vaishnav.a@ti.com> <20230330174005.24950-2-vaishnav.a@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20230330174005.24950-2-vaishnav.a@ti.com> X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.8 at phobos.denx.de X-Virus-Status: Clean On 23:10-20230330, Vaishnav Achath wrote: > J721E SoC has a hyperbus controller and OSPI controller muxed and only > one of the controllers can be active at a time. While enabling the > support for hyperbus, both the OSPI and hyperbus nodes were enabled > by default and hyperbus was disabled in board dts. This causes issues > in other J721E based platforms which does not explicitly disable the > hbmc node in board dts, thus disable hyperbus node by default. > > Fixes: 297daac43afb ("arm: dts: k3-j721e-mcu-wakeup: Add HyperBus Controller node") > > Signed-off-by: Vaishnav Achath > --- > > Since this node is not present in corresponding upstream kernel DTS > now, a manual fix is needed. > > arch/arm/dts/k3-j721e-mcu-wakeup.dtsi | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/arch/arm/dts/k3-j721e-mcu-wakeup.dtsi b/arch/arm/dts/k3-j721e-mcu-wakeup.dtsi > index 22166c7942..b7a0dd2326 100644 > --- a/arch/arm/dts/k3-j721e-mcu-wakeup.dtsi > +++ b/arch/arm/dts/k3-j721e-mcu-wakeup.dtsi > @@ -183,6 +183,7 @@ > }; > > hbmc: hyperbus@47034000 { > + status = "disabled"; > compatible = "ti,j721e-hbmc", "ti,am654-hbmc"; > reg = <0x0 0x47034000 0x0 0x100>, > <0x5 0x00000000 0x1 0x0000000>; > -- > 2.17.1 > We should just delete the entire node. this does'nt exist in upstream[1] [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi -- Regards, Nishanth Menon Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D