linux-kernel - Re: [PATCH V8 4/5] phy: freescale: fsl-samsung-hdmi: Use closest divider

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: <c655e745-0289-4d12-9d91-612c18d6e607@kontron.de>
Date: Mon, 16 Sep 2024 09:16:14 +0200
From: Frieder Schrempf <frieder.schrempf@...tron.de>
To: Adam Ford <aford173@...il.com>, linux-phy@...ts.infradead.org
Cc: dominique.martinet@...ark-techno.com, linux-imx@....com,
 festevam@...il.com, aford@...conembedded.com, Sandor.yu@....com,
 neil.armstrong@...aro.org, Vinod Koul <vkoul@...nel.org>,
 Kishon Vijay Abraham I <kishon@...nel.org>,
 Marco Felsch <m.felsch@...gutronix.de>, Lucas Stach
 <l.stach@...gutronix.de>, Uwe Kleine-König
 <u.kleine-koenig@...gutronix.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V8 4/5] phy: freescale: fsl-samsung-hdmi: Use closest
 divider

On 14.09.24 1:27 PM, Adam Ford wrote:
> Currently, if the clock values cannot be set to the exact rate,
> the round_rate and set_rate functions use the closest value found in
> the look-up-table.  In preparation of removing values from the LUT
> that can be calculated evenly with the integer calculator, it's
> necessary to ensure to check both the look-up-table and the integer
> divider clock values to get the closest values to the requested
> value.  It does this by measuring the difference between the
> requested clock value and the closest value in both integer divider
> calucator and the fractional clock look-up-table.
> 
> Which ever has the smallest difference between them is returned as
> the closest rate.
> 
> Signed-off-by: Adam Ford <aford173@...il.com>
> Reviewed-by: Dominique Martinet <dominique.martinet@...ark-techno.com>
> Tested-by: Dominique Martinet <dominique.martinet@...ark-techno.com>

Reviewed-by: Frieder Schrempf <frieder.schrempf@...tron.de>