Received-SPF: pass (google.com: domain of linux-kernel+bounces-68509-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
From: Thierry Reding <thierry.reding@gmail.com>
To: thierry.reding@gmail.com,
	jonathanh@nvidia.com,
	robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org,
	conor+dt@kernel.org,
	p.zabel@pengutronix.de,
	dmitry.osipenko@collabora.com,
	ulf.hansson@linaro.org,
	kkartik@nvidia.com,
	cai.huoqing@linux.dev,
	spatra@nvidia.com,
	linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org,
	Petlozu Pravareshwar <petlozup@nvidia.com>
Subject: Re: [PATCH V3 1/3] soc/tegra: pmc: Update address mapping sequence for PMC apertures
Date: Fri, 16 Feb 2024 12:20:07 +0100
Message-ID: <170808233530.197509.809812872766738307.b4-ty@nvidia.com>
In-Reply-To: <20240211171727.914595-1-petlozup@nvidia.com>
References: <20240211171727.914595-1-petlozup@nvidia.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

From: Thierry Reding <treding@nvidia.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@nvidia.com>