[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yr26oSKOhIBMaKsS@kroah.com>
Date: Thu, 30 Jun 2022 17:00:49 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Vijaya Krishna Nivarthi <quic_vnivarth@...cinc.com>
Cc: agross@...nel.org, bjorn.andersson@...aro.org,
konrad.dybcio@...ainline.org, jirislaby@...nel.org,
linux-arm-msm@...r.kernel.org, linux-serial@...r.kernel.org,
linux-kernel@...r.kernel.org, quic_msavaliy@...cinc.com,
dianders@...omium.org, mka@...omium.org, swboyd@...omium.org
Subject: Re: [V2] tty: serial: qcom-geni-serial: Fix get_clk_div_rate() which
otherwise could return a sub-optimal clock rate.
On Wed, Jun 29, 2022 at 03:30:41PM +0530, Vijaya Krishna Nivarthi wrote:
> In the logic around call to clk_round_rate(), for some corner conditions,
> get_clk_div_rate() could return an sub-optimal clock rate. Also, if an
> exact clock rate was not found lowest clock was being returned.
>
> Search for suitable clock rate in 2 steps
> a) exact match or within 2% tolerance
> b) within 5% tolerance
> This also takes care of corner conditions.
>
> Reported-by: kernel test robot <lkp@...el.com>
Did the test robot really report the original issue, or just the v2
change?
thanks,
greg k-h
Powered by blists - more mailing lists