[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3f024bd8-3388-4984-a962-531e3fe88c6a@quicinc.com>
Date: Wed, 21 May 2025 11:55:14 +0530
From: Mukesh Kumar Savaliya <quic_msavaliy@...cinc.com>
To: Andi Shyti <andi.shyti@...nel.org>
CC: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@....qualcomm.com>,
"Viken
Dadhaniya" <quic_vdadhani@...cinc.com>,
Manikanta Mylavarapu
<quic_mmanikan@...cinc.com>,
Bjorn Andersson <andersson@...nel.org>, <linux-i2c@...r.kernel.org>,
<linux-arm-msm@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<stable@...nel.org>
Subject: Re: [PATCH] i2c: qcom-geni: fix I2C frequency table to achieve
accurate bus rates
Looks good to me, Thanks Kathiravan, Andi !
On 5/16/2025 2:16 PM, Andi Shyti wrote:
> Hi Mukesh,
>
> On Fri, May 16, 2025 at 12:23:46AM +0530, Mukesh Kumar Savaliya wrote:
>>>> /* source_clock = 32 MHz */
>>>> static const struct geni_i2c_clk_fld geni_i2c_clk_map_32mhz[] = {
>>>> - { I2C_MAX_STANDARD_MODE_FREQ, 8, 14, 18, 40 },
>>>> - { I2C_MAX_FAST_MODE_FREQ, 4, 3, 11, 20 },
>>>> - { I2C_MAX_FAST_MODE_PLUS_FREQ, 2, 3, 6, 15 },
>>>> + { I2C_MAX_STANDARD_MODE_FREQ, 8, 14, 18, 38 },
>>>> + { I2C_MAX_FAST_MODE_FREQ, 4, 3, 9, 19 },
>>>> + { I2C_MAX_FAST_MODE_PLUS_FREQ, 2, 3, 5, 15 },
>>>
>>> argh!
>>>
>>> Can someone from Qualcomm look at this fix? Mukesh, Viken?
>> Yes, I am reviewing internally and verifying the same with latest Guidance
>> and updates. Let me update on this once reviewed.
>
> thanks a lot! It's very much appreciated!
>
Reviewed-by: Mukesh Kumar Savaliya <quic_msavaliy@...cinc.com>
> Andi
Powered by blists - more mailing lists