From nobody Thu Apr 9 16:25:47 2026 Received: from mail-106118.protonmail.ch (mail-106118.protonmail.ch [79.135.106.118]) (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 05FEB34753D; Sun, 8 Mar 2026 20:40:45 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=79.135.106.118 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773002447; cv=none; b=r1/MpPAu/zzKtr099t463c5mi7s4PvcykJ9eQEYKYGNyrdnkYjCpuP9XJmA8dhC0y2+RJPWN+H7o6SM7TlPCsfuhhadcL4fRnEQzqAs+/iotk6gmUSm/alf0W54UDJGo+u+PBVtzf0B62Zs6hsF7XCW1o66Wx3rQaFd5VngEcXs= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773002447; c=relaxed/simple; bh=EHS4Q5OSPg6ebVGXWGlvXgFk9A3oDD+sIHo1a+0CNK4=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=ETvzwYPbxGhmWKu7EiUWEfj08hks7oNVWgRz2qVpqVPUkDhGnQRWcvH5ylcP4uy5oIyCnx9tqX7ADfpEP7a8jc5/23+PkIgZiwTx8KdcF4nIS65EfcLay+Jf4gkDl3pc0mcVGtG+7UIJAaHoxqoBAQgMMWg89pgECnmN4l0/BT4= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=pm.me; spf=pass smtp.mailfrom=pm.me; dkim=pass (2048-bit key) header.d=pm.me header.i=@pm.me header.b=cyTnzTmy; arc=none smtp.client-ip=79.135.106.118 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=pm.me Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=pm.me Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=pm.me header.i=@pm.me header.b="cyTnzTmy" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pm.me; s=protonmail3; t=1773002444; x=1773261644; bh=EHS4Q5OSPg6ebVGXWGlvXgFk9A3oDD+sIHo1a+0CNK4=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=cyTnzTmyYTUykzbN8PnUDHVYXpEvsYk+BH4N7NCe6c8bGgBdKTEgFv5DI/lOb7Vqi ED0adBVu9NI+ZGcIYwdQWyvG0j8QTM3iMVgzeYd+Z8S9o2NngYCmgwcUX8cELCis59 1GW81P4sHcg54Rs6rKaTdR3qXLekmXpKCgPa7KUGdK95e/2jdAf+uqjph8u3GUNU+d gRdgjRi0DVJ6ruf70Hb6fb8e5veHZp7Aqs4+hM6FQvIiabLRkQPXJ6Fl4wOqzSZPQF hJwwL7kePCjClVbINO4WMPC1V9O3eGkDFiC4tjqa/bnz8jpfKXVtt5ZILc6MPX9iZ4 0Hgt7ZZSR7CGQ== Date: Sun, 08 Mar 2026 20:40:38 +0000 To: Bjorn Andersson , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Kees Cook , Tony Luck , "Guilherme G. Piccoli" From: Alexander Koskovich Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Alexander Koskovich Subject: [PATCH 2/3] arm64: dts: qcom: sm8250: Add label for reserved-memory node Message-ID: <20260308-sm8250-asus-obiwan-v1-2-3c72941eb796@pm.me> In-Reply-To: <20260308-sm8250-asus-obiwan-v1-0-3c72941eb796@pm.me> References: <20260308-sm8250-asus-obiwan-v1-0-3c72941eb796@pm.me> Feedback-ID: 37836894:user:proton X-Pm-Message-ID: d30af95a04b963041f5a5f6990f636abfd042db2 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" For some devices it makes more sense to just redefine reserved-memory, for example on the ASUS ROG Phone 3 it is completely different with the exception of hyp_mem, xbl_aop_mem, cmd_db and smem_mem. Signed-off-by: Alexander Koskovich --- arch/arm64/boot/dts/qcom/sm8250.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/boot/dts/qcom/sm8250.dtsi b/arch/arm64/boot/dts/qco= m/sm8250.dtsi index c7dffa440074..3298c36c3e55 100644 --- a/arch/arm64/boot/dts/qcom/sm8250.dtsi +++ b/arch/arm64/boot/dts/qcom/sm8250.dtsi @@ -763,7 +763,7 @@ opp-120000000 { }; }; =20 - reserved-memory { + reserved_memory: reserved-memory { #address-cells =3D <2>; #size-cells =3D <2>; ranges; --=20 2.53.0