linux-kernel - Re: [Patch RESEND 3/4] memory: tegra: add check if MRQ_EMC_DVFS

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZLASGT0mN9aj9ewL@orome>
Date:   Thu, 13 Jul 2023 17:02:49 +0200
From:   Thierry Reding <thierry.reding@...il.com>
To:     Sumit Gupta <sumitg@...dia.com>
Cc:     krzysztof.kozlowski@...aro.org, treding@...dia.com,
        jonathanh@...dia.com, linux-kernel@...r.kernel.org,
        linux-tegra@...r.kernel.org, bbasu@...dia.com, talho@...dia.com
Subject: Re: [Patch RESEND 3/4] memory: tegra: add check if
 MRQ_EMC_DVFS_LATENCY is supported

On Wed, Jun 21, 2023 at 07:13:59PM +0530, Sumit Gupta wrote:
> Add check to ensure that "MRQ_EMC_DVFS_LATENCY" is supported by the
> BPMP-FW before making the MRQ request. Currently, if the BPMP-FW
> doesn't support this MRQ, then the "tegra186_emc_probe" fails.
> Due to this the Memory Interconnect initialization also doesn't
> happen. Memory Interconnect is not dependent on this MRQ and can
> initialize even when this MRQ is not supported in any platform.
> The check ensures that the MRQ is called only when it is supported
> by the BPMP-FW and Interconnect initializes independent of this MRQ.
> Also, moved the code to new function for better readability.
> 
> Signed-off-by: Sumit Gupta <sumitg@...dia.com>
> ---
>  drivers/memory/tegra/tegra186-emc.c | 136 +++++++++++++++-------------
>  1 file changed, 71 insertions(+), 65 deletions(-)

Acked-by: Thierry Reding <treding@...dia.com>

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)