From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lelvem-ot01.ext.ti.com (lelvem-ot01.ext.ti.com [198.47.23.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AF90D1DAC88; Tue, 28 Jan 2025 16:22:13 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.47.23.234 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1738081335; cv=none; b=ggY28FTLWbcRKKU6u6tOWsPJovC6jFKnSSlfvy7Ow7IIPlvu9ahZbfL3gr3MFG+ieFQ5i3ncjxGXZT5Nn/TTSMuTK8ztpjnGwBva8tkgZ1QeyXgRciU34pi21o/PeBAS91W9uWF3mO5xa7VE+xX5DqmuzGA1+Kd+15Ms3lyrbds= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1738081335; c=relaxed/simple; bh=uH/lxq8lu5P/j8Dc3+jG777lJ5HIU52S1rxPE7hA1DE=; h=Message-ID:Date:MIME-Version:Subject:To:CC:References:From: In-Reply-To:Content-Type; b=ksZz/qZ3wgWmS7igxZ2nCsSCuaSvOwzJib7swnIiP7kFZ0BXVU1ukrywyJ534//VjwHaNl/SlaQmaYLItgrV8JsB0nid8wVthY2a0iLFBgyfLSke5tPqVZ8do/5gC01r4JyS9WejL2YAGrr7wLfd59Pcl8LCukOUiqsJP4DOzSU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ti.com; spf=pass smtp.mailfrom=ti.com; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b=uqtrmIdi; arc=none smtp.client-ip=198.47.23.234 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ti.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ti.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="uqtrmIdi" Received: from lelv0266.itg.ti.com ([10.180.67.225]) by lelvem-ot01.ext.ti.com (8.15.2/8.15.2) with ESMTPS id 50SGM5Em2031163 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 28 Jan 2025 10:22:05 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1738081325; bh=a993OaTmApiSLYlbcO9FRYc1TtEbUHIgXSDEucVTzdo=; h=Date:Subject:To:CC:References:From:In-Reply-To; b=uqtrmIdiNt8YICveSIYOuI4iwA71sM7ttGG2uTrkhJTbYn5kxfvrxKj76cPznY8EM j/Sxck0VqJE5fFNDHIxI5P6E+jQ6sL4hTcBVaH4SN8/TsclA+ry9aukayjHAT7Qabs DDaqvHvt3gCH8GJGpxOEK7pQGdCEVXxnaaDQrDF4= Received: from DLEE108.ent.ti.com (dlee108.ent.ti.com [157.170.170.38]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTP id 50SGM5oY004743; Tue, 28 Jan 2025 10:22:05 -0600 Received: from DLEE107.ent.ti.com (157.170.170.37) 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.23; Tue, 28 Jan 2025 10:22:04 -0600 Received: from lelvsmtp5.itg.ti.com (10.180.75.250) 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.23 via Frontend Transport; Tue, 28 Jan 2025 10:22:04 -0600 Received: from [10.250.32.214] ([10.250.32.214]) by lelvsmtp5.itg.ti.com (8.15.2/8.15.2) with ESMTP id 50SGM4Zv083379; Tue, 28 Jan 2025 10:22:04 -0600 Message-ID: <950a1e23-a943-41b0-979a-4e7a4a264fdd@ti.com> Date: Tue, 28 Jan 2025 10:22:04 -0600 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 1/4] arm64: dts: ti: k3-am62-wakeup: Add wakeup r5f node To: Judith Mendez , Nishanth Menon , Vignesh Raghavendra CC: Rob Herring , Krzysztof Kozlowski , Conor Dooley , , , , Devarsh Thakkar , Hari Nagalla References: <20250127221631.3974583-1-jm@ti.com> <20250127221631.3974583-2-jm@ti.com> Content-Language: en-US From: Andrew Davis In-Reply-To: <20250127221631.3974583-2-jm@ti.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-C2ProcessedOrg: 333ef613-75bf-4e12-a4b1-8e3623f5dcea On 1/27/25 4:16 PM, Judith Mendez wrote: > From: Hari Nagalla > > AM62 SoC devices have a single core R5F processor in wakeup domain. > The R5F processor in wakeup domain is used as a device manager > for the SoC. > > Co-authored-by: Devarsh Thakkar > Signed-off-by: Hari Nagalla > [Judith: Fix commit message header] > Signed-off-by: Judith Mendez > --- > arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi | 24 ++++++++++++++++++++++ > 1 file changed, 24 insertions(+) > > diff --git a/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi > index 9b8a1f85aa15c..79708c1c214f8 100644 > --- a/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi > +++ b/arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi > @@ -106,6 +106,30 @@ wkup_rti0: watchdog@2b000000 { > status = "reserved"; > }; > > + wkup_r5fss0: r5fss@78000000 { > + compatible = "ti,am62-r5fss"; > + #address-cells = <1>; > + #size-cells = <1>; > + ranges = <0x78000000 0x00 0x78000000 0x8000>, > + <0x78100000 0x00 0x78100000 0x8000>; > + power-domains = <&k3_pds 119 TI_SCI_PD_EXCLUSIVE>; > + > + wkup_r5fss0_core0: r5f@78000000 { > + compatible = "ti,am62-r5f"; > + reg = <0x78000000 0x00008000>, > + <0x78100000 0x00008000>; > + reg-names = "atcm", "btcm"; > + ti,sci = <&dmsc>; > + ti,sci-dev-id = <121>; > + ti,sci-proc-ids = <0x01 0xff>; > + resets = <&k3_reset 121 1>; > + firmware-name = "ti-sysfw/ti-fs-stub-firmware-am62x-gp-signed.bin"; What is this firmware name? This doesn't exist in linux-firmware, should use the normal name like "am62-wkup-r5f0_0-fw", then we can use symlinks in our userspace to map to whatever firmware we want to run. Andrew > + ti,atcm-enable = <1>; > + ti,btcm-enable = <1>; > + ti,loczrama = <1>; > + }; > + }; > + > wkup_vtm0: temperature-sensor@b00000 { > compatible = "ti,j7200-vtm"; > reg = <0x00 0xb00000 0x00 0x400>,