linux-kernel - Re: [PATCH V3 1/3] soc/tegra: pmc: Update address mapping sequence for PMC apertures

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]

Date: Fri, 16 Feb 2024 12:20:07 +0100
From: Thierry Reding <thierry.reding@...il.com>
To: thierry.reding@...il.com,
	jonathanh@...dia.com,
	robh+dt@...nel.org,
	krzysztof.kozlowski+dt@...aro.org,
	conor+dt@...nel.org,
	p.zabel@...gutronix.de,
	dmitry.osipenko@...labora.com,
	ulf.hansson@...aro.org,
	kkartik@...dia.com,
	cai.huoqing@...ux.dev,
	spatra@...dia.com,
	linux-tegra@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	devicetree@...r.kernel.org,
	Petlozu Pravareshwar <petlozup@...dia.com>
Subject: Re: [PATCH V3 1/3] soc/tegra: pmc: Update address mapping sequence for PMC apertures

From: Thierry Reding <treding@...dia.com>


On Sun, 11 Feb 2024 17:17:25 +0000, Petlozu Pravareshwar wrote:
> On Tegra SoCs prior to Tegra186, PMC has single address range only.
> Starting from and after Tegra186, PMC has additional address ranges
> apart from base address range. Currently in PMC driver, we try to
> map these additional address ranges on all SoCs and if we fail then
> we assume that the range is not valid for an SoC. This change makes
> it more explicit on which address ranges are expected to be present
> on which SoCs and maps the additional address ranges only on SoCs
> from and after Tegra186.
> 
> [...]

Applied, thanks!

Best regards,
-- 
Thierry Reding <treding@...dia.com>