linux-kernel - Re: [PATCH] arm64: dts: exynos: Specify reserved secure memory explicitly

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <173487756773.3738.7711760267747537170.b4-ty@linaro.org>
Date: Sun, 22 Dec 2024 15:26:07 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Krzysztof Kozlowski <krzk+dt@...nel.org>, Rob Herring <robh@...nel.org>, 
 Sam Protsenko <semen.protsenko@...aro.org>
Cc: Conor Dooley <conor+dt@...nel.org>, 
 Alim Akhtar <alim.akhtar@...sung.com>, linux-arm-kernel@...ts.infradead.org, 
 linux-samsung-soc@...r.kernel.org, devicetree@...r.kernel.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: exynos: Specify reserved secure memory
 explicitly


On Tue, 10 Dec 2024 21:30:27 -0600, Sam Protsenko wrote:
> Instead of carving out the secure area in 'memory' node, let's describe
> it in 'reserved-memory'. That makes it easier to understand both RAM
> regions and particular secure world memory region. Originally the device
> tree was created in a way to make sure it was well aligned with the way
> LittleKernel bootloader modified it. But later it was found the
> LittleKernel works fine with properly described reserved regions, so
> it's possible now to define those in a cleaner way.
> 
> [...]

Applied, thanks!

[1/1] arm64: dts: exynos: Specify reserved secure memory explicitly
      https://git.kernel.org/krzk/linux/c/11fd6c9b047c30c72dcea3f79c0acb7deb69c822

Best regards,
-- 
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>