linux-kernel - Re: [PATCH RESEND v3 0/7] Cleanup Tegra210 EMC frequency scaling

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]

Date: Mon, 27 May 2024 11:15:13 +0100
From: Diogo Ivo <diogo.ivo@...nico.ulisboa.pt>
To: krzysztof.kozlowski@...aro.org, thierry.reding@...il.com, 
	jonathanh@...dia.com, linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: diogo.ivo@...nico.ulisboa.pt
Subject: Re: [PATCH RESEND v3 0/7] Cleanup Tegra210 EMC frequency scaling

Hello,

On Tue, May 07, 2024 at 10:30:43AM GMT, Diogo Ivo wrote:
> Hello,
> 
> This patch series consists of a general cleanup of the Tegra210 EMC
> frequency scaling code for revision 7.
> 
> Currently the code is relying heavily on a function, update_clock_tree_delay(),
> that is responsible for too many things, making it long and confusing.
> The general idea with these patches is to simplify this function and its
> surrounding code, making it more modular.
> 
> The motivation behind these changes (besides improving readability and
> maintainability) is to make it simpler to add support in the future for
> frequency change revisions other than 7, where we can reuse a large
> portion of the modularized code rather than essentially repeating 2k
> lines of code with minimal changes.

Gentle ping on this patch series. I think this version addressed all of
the review comments, is there anything missing?

Best regards,
Diogo