Message ID | 20230412173609.1307837-1-u-kumar1@ti.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:b0ea:0:b0:3b6:4342:cba0 with SMTP id b10csp508786vqo; Wed, 12 Apr 2023 11:00:23 -0700 (PDT) X-Google-Smtp-Source: AKy350a86+Y234p7WyW/EGA/DgiU+uoorpFfzyGfmegCQR32g5o0WGwGc53k5gV8XKJM+UVMvYcR X-Received: by 2002:a05:6a20:6da7:b0:e8:a277:5e16 with SMTP id gl39-20020a056a206da700b000e8a2775e16mr3287879pzb.43.1681322423371; Wed, 12 Apr 2023 11:00:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681322423; cv=none; d=google.com; s=arc-20160816; b=W8ELEy4f2cagdYGaL6TlLyN0Tn3Y0k0e+RLkYrc6Ue6s/BJUaJdDJm7R69deKe1dHL cP3aqgBzQ0igViOoA0S9uofLsJZBATL2Smi4KjJM5UF+fp7pziPQmlsdqYIqcN+qczgl SbDXI09kuiVI0NqKIjZ0OtbdeZNanK8GiMSDF84E0faND9Z/XSW977E9UYhOGVsyhqpC ateSm2LLWtPxD9g5EM9fU11fMj+cqsK2eLuIp2S143pD6rHRgunUcJcXw0NI0wE0LUqp 4oyefg8C75K7YXEUl3P1CgoiqmN0pGd8Oawi5lqjGQSC7WIzzJQMC2sTeGQZ7GeLG7L2 q/Vg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=Gwn22cSL9LrtifAyT+aMZ04trXrV9XYL70h9w0kbhFg=; b=MLBIVJ6wVY9f0B8NywdrAtMcKTsaFtTOvRQjOr+HD0MIRE/7udj+mNPHTO0aooQwug Lx3E2JPECUUzj4hz2Np6uY6VTrdGDLKGY9W/UmpYjPBSWtvtZXjNzdId9RVJJcLtMZU8 3I1j7oQT19qVm1/ywC0kqP4J87XFcBs6vtlozO1kll/3Vi1AtYI/FeecvdLprlvD11Jj PYsl3mx+H6owc6yoV6TRJXeYUgrpNzgtGbzR3mfXvgaEvrgJunsyBqDanBnIhEncop/1 GsVpEyZCiFKfcCBXbqlXGlqfSB1+WAPW8H5XIcFqwMGfd8xx6TspwR2LbiJUmf4smOK1 G2KA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=tOxk2sNb; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id f20-20020a656294000000b0051412a8bc7esi15657605pgv.560.2023.04.12.11.00.10; Wed, 12 Apr 2023 11:00:23 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=tOxk2sNb; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229778AbjDLRgp (ORCPT <rfc822;peter110.wang@gmail.com> + 99 others); Wed, 12 Apr 2023 13:36:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43358 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229498AbjDLRgo (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Wed, 12 Apr 2023 13:36:44 -0400 Received: from lelv0143.ext.ti.com (lelv0143.ext.ti.com [198.47.23.248]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 76D5426BE; Wed, 12 Apr 2023 10:36:43 -0700 (PDT) Received: from fllv0034.itg.ti.com ([10.64.40.246]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id 33CHaSQU040540; Wed, 12 Apr 2023 12:36:28 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1681320988; bh=Gwn22cSL9LrtifAyT+aMZ04trXrV9XYL70h9w0kbhFg=; h=From:To:CC:Subject:Date; b=tOxk2sNbTqlgK5t23qzQcboJKrU0aIcUSjwWv6v+ULKeyYF7NjRgyQjW32TUJ6dOL Ar0TdP6YLwJTItNEhmp8uSlZwdnP9tBAqOq718VFyjGGl7ZQZsAEA0BlvnW1car0oJ Rv3Qh5eFClL8FRhVtVrfwMM2zGFmB7NWewdhSJq0= Received: from DLEE111.ent.ti.com (dlee111.ent.ti.com [157.170.170.22]) by fllv0034.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 33CHaSWQ082774 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 12 Apr 2023 12:36:28 -0500 Received: from DLEE107.ent.ti.com (157.170.170.37) by DLEE111.ent.ti.com (157.170.170.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.16; Wed, 12 Apr 2023 12:36:28 -0500 Received: from fllv0039.itg.ti.com (10.64.41.19) by DLEE107.ent.ti.com (157.170.170.37) 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; Wed, 12 Apr 2023 12:36:27 -0500 Received: from udit-HP-Z2-Tower-G9-Workstation-Desktop-PC.dhcp.ti.com (ileaxei01-snat.itg.ti.com [10.180.69.5]) by fllv0039.itg.ti.com (8.15.2/8.15.2) with ESMTP id 33CHaOna082586; Wed, 12 Apr 2023 12:36:25 -0500 From: Udit Kumar <u-kumar1@ti.com> To: <linux-arm-kernel@lists.infradead.org>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>, <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>, <a-govindraju@ti.com>, <kishon@ti.com> CC: <n-dasan@ti.com>, Udit Kumar <u-kumar1@ti.com> Subject: [PATCH] arm64: dts: ti: k3-j721s2-main: fix msmc node Date: Wed, 12 Apr 2023 23:06:09 +0530 Message-ID: <20230412173609.1307837-1-u-kumar1@ti.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_PASS,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1762994341581554025?= X-GMAIL-MSGID: =?utf-8?q?1762994341581554025?= |
Series |
arm64: dts: ti: k3-j721s2-main: fix msmc node
|
|
Commit Message
Kumar, Udit
April 12, 2023, 5:36 p.m. UTC
On J721S2 SOC, l3cache-sram size is configured as zero by
system firmware.
Also top 64K of msmc_ram (0x703F_0000 to 0x703F_FFFF) is used by system
firmware tifs-sram.
This patch removes l3cache-sram node and update range for tifs-sram.
Fixes: b8545f9d3a54 ("arm64: dts: ti: Add initial support for J721S2 SoC")
Signed-off-by: Udit Kumar <u-kumar1@ti.com>
---
arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
Comments
On 23:06-20230412, Udit Kumar wrote: > On J721S2 SOC, l3cache-sram size is configured as zero by > system firmware. > Also top 64K of msmc_ram (0x703F_0000 to 0x703F_FFFF) is used by system > firmware tifs-sram. > > This patch removes l3cache-sram node and update range for tifs-sram. > > Fixes: b8545f9d3a54 ("arm64: dts: ti: Add initial support for J721S2 SoC") > > Signed-off-by: Udit Kumar <u-kumar1@ti.com> > --- > arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 7 ++----- > 1 file changed, 2 insertions(+), 5 deletions(-) > > diff --git a/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi b/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi > index 2dd7865f7654..cbc784f915a9 100644 > --- a/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi > +++ b/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi > @@ -17,13 +17,10 @@ atf-sram@0 { > reg = <0x0 0x20000>; > }; > > - tifs-sram@1f0000 { > - reg = <0x1f0000 0x10000>; > + tifs-sram@3f0000 { > + reg = <0x3f0000 0x10000>; > }; > > - l3cache-sram@200000 { > - reg = <0x200000 0x200000>; > - }; > }; > > gic500: interrupt-controller@1800000 { > -- > 2.34.1 > Are you saying that j721s2 is incapable of l3 cache? say some level 1 errata? or is it because, the chip is really capable of l3 cache and we are really setting it to 0? https://git.ti.com/cgit/k3-image-gen/k3-image-gen/tree/soc/j721s2/evm/board-cfg.c#n71 unless the chip has an errata, you are supposed to fix it up based on configuration by using the API and this patch is a NAK https://software-dl.ti.com/tisci/esd/latest/2_tisci_msgs/general/core.html#tisci-query-msmc
Hi Nishanth, On 13/04/23 01:26, Nishanth Menon wrote: > On 23:06-20230412, Udit Kumar wrote: >> On J721S2 SOC, l3cache-sram size is configured as zero by >> system firmware. >> Also top 64K of msmc_ram (0x703F_0000 to 0x703F_FFFF) is used by system >> firmware tifs-sram. >> >> This patch removes l3cache-sram node and update range for tifs-sram. >> >> Fixes: b8545f9d3a54 ("arm64: dts: ti: Add initial support for J721S2 SoC") >> >> Signed-off-by: Udit Kumar <u-kumar1@ti.com> >> --- >> arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 7 ++----- >> 1 file changed, 2 insertions(+), 5 deletions(-) >> >> diff --git a/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi b/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi >> index 2dd7865f7654..cbc784f915a9 100644 >> --- a/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi >> +++ b/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi >> @@ -17,13 +17,10 @@ atf-sram@0 { >> reg = <0x0 0x20000>; >> }; >> >> - tifs-sram@1f0000 { >> - reg = <0x1f0000 0x10000>; >> + tifs-sram@3f0000 { >> + reg = <0x3f0000 0x10000>; >> }; >> >> - l3cache-sram@200000 { >> - reg = <0x200000 0x200000>; >> - }; >> }; >> >> gic500: interrupt-controller@1800000 { >> -- >> 2.34.1 >> > Are you saying that j721s2 is incapable of l3 cache? say some level 1 > errata? No > or is it because, the chip is really capable of l3 cache and we are > really setting it to 0? > > https://git.ti.com/cgit/k3-image-gen/k3-image-gen/tree/soc/j721s2/evm/board-cfg.c#n71 This is because, l3 cache size is set to zero. > unless the chip has an errata, you are supposed to fix it up based on > configuration by using the API and this patch is a NAK > https://software-dl.ti.com/tisci/esd/latest/2_tisci_msgs/general/core.html#tisci-query-msmc ok
Hi Udit, On 13/04/23 10:45, Udit Kumar wrote: > Hi Nishanth, > > On 13/04/23 01:26, Nishanth Menon wrote: >> On 23:06-20230412, Udit Kumar wrote: >>> On J721S2 SOC, l3cache-sram size is configured as zero by >>> system firmware. >>> Also top 64K of msmc_ram (0x703F_0000 to 0x703F_FFFF) is used by system >>> firmware tifs-sram. >>> >>> This patch removes l3cache-sram node and update range for tifs-sram. >>> >>> Fixes: b8545f9d3a54 ("arm64: dts: ti: Add initial support for J721S2 >>> SoC") >>> >>> Signed-off-by: Udit Kumar <u-kumar1@ti.com> >>> --- >>> arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 7 ++----- >>> 1 file changed, 2 insertions(+), 5 deletions(-) >>> >>> diff --git a/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi >>> b/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi >>> index 2dd7865f7654..cbc784f915a9 100644 >>> --- a/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi >>> +++ b/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi >>> @@ -17,13 +17,10 @@ atf-sram@0 { >>> reg = <0x0 0x20000>; >>> }; >>> - tifs-sram@1f0000 { >>> - reg = <0x1f0000 0x10000>; >>> + tifs-sram@3f0000 { >>> + reg = <0x3f0000 0x10000>; >>> }; >>> - l3cache-sram@200000 { >>> - reg = <0x200000 0x200000>; >>> - }; >>> }; >>> gic500: interrupt-controller@1800000 { >>> -- >>> 2.34.1 >>> >> Are you saying that j721s2 is incapable of l3 cache? say some level 1 >> errata? > No >> or is it because, the chip is really capable of l3 cache and we are >> really setting it to 0? >> >> https://git.ti.com/cgit/k3-image-gen/k3-image-gen/tree/soc/j721s2/evm/board-cfg.c#n71 > This is because, l3 cache size is set to zero. >> unless the chip has an errata, you are supposed to fix it up based on >> configuration by using the API and this patch is a NAK >> https://software-dl.ti.com/tisci/esd/latest/2_tisci_msgs/general/core.html#tisci-query-msmc > ok U-Boot already does this. See fdt_fixup_msmc_ram() at board/ti/j721s2/evm.c tifs-sram fixup probably is still needed and possible bug in the original patch?
Thanks Raghavendra On 13/04/23 10:53, Vignesh Raghavendra wrote: > Hi Udit, > > On 13/04/23 10:45, Udit Kumar wrote: >> Hi Nishanth, >> >> On 13/04/23 01:26, Nishanth Menon wrote: >>> On 23:06-20230412, Udit Kumar wrote: >>>> [..] >>> Are you saying that j721s2 is incapable of l3 cache? say some level 1 >>> errata? >> No >>> or is it because, the chip is really capable of l3 cache and we are >>> really setting it to 0? >>> >>> https://git.ti.com/cgit/k3-image-gen/k3-image-gen/tree/soc/j721s2/evm/board-cfg.c#n71 >> This is because, l3 cache size is set to zero. >>> unless the chip has an errata, you are supposed to fix it up based on >>> configuration by using the API and this patch is a NAK >>> https://software-dl.ti.com/tisci/esd/latest/2_tisci_msgs/general/core.html#tisci-query-msmc >> ok > U-Boot already does this. See fdt_fixup_msmc_ram() at board/ti/j721s2/evm.c > > tifs-sram fixup probably is still needed and possible bug in the original patch? Let me fix in u-boot Regards Udit >
diff --git a/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi b/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi index 2dd7865f7654..cbc784f915a9 100644 --- a/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi +++ b/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi @@ -17,13 +17,10 @@ atf-sram@0 { reg = <0x0 0x20000>; }; - tifs-sram@1f0000 { - reg = <0x1f0000 0x10000>; + tifs-sram@3f0000 { + reg = <0x3f0000 0x10000>; }; - l3cache-sram@200000 { - reg = <0x200000 0x200000>; - }; }; gic500: interrupt-controller@1800000 {