From: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Mukesh Kumar Savaliya <mukesh.savaliya@oss.qualcomm.com>,
Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>,
Andi Shyti <andi.shyti@kernel.org>,
Manikanta Mylavarapu <quic_mmanikan@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>,
linux-i2c@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] i2c: qcom-geni: update frequency table to fix timing parameters
Date: Tue, 18 Aug 2026 16:28:00 +0530 [thread overview]
Message-ID: <62eedb1a-1da7-4e65-99db-7c510844bd99@oss.qualcomm.com> (raw)
In-Reply-To: <e3b06684-496c-4efe-9bc4-65d29583cb7a@oss.qualcomm.com>
On 8/17/2026 7:25 PM, Konrad Dybcio wrote:
> On 8/12/26 10:30 AM, Kathiravan Thirumoorthy wrote:
>> In IPQ5424, to meet the setup and hold timing requirements in the
>> standard mode, update the frequency table with the values recommended by
>> HW design team.
> Does this have any ipq5424 specifics, or are these just adjusted for
> the generic case of srcclk=32mhz?
As far as I know, IPQ5424 is the first SoC which uses srcclk as 32MHz.
IPQ5210 and IPQ9650 also uses srcclk as 32MHz which leverages the same
SCL configuration.
>
> Konrad
next prev parent reply other threads:[~2026-08-18 10:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 8:30 [PATCH v2 0/2] I2C SCL counter updates for Qualcomm IPQ5424 SoC Kathiravan Thirumoorthy
2026-08-12 8:30 ` [PATCH v2 1/2] i2c: qcom-geni: update frequency table to fix timing parameters Kathiravan Thirumoorthy
2026-08-12 17:45 ` Mukesh Savaliya
2026-08-17 13:55 ` Konrad Dybcio
2026-08-18 10:58 ` Kathiravan Thirumoorthy [this message]
2026-08-24 9:22 ` Konrad Dybcio
2026-08-12 8:30 ` [PATCH v2 2/2] i2c: qcom-geni: add I2C frequency table for 32 MHz firmware-based SEs Kathiravan Thirumoorthy
2026-08-12 17:56 ` Mukesh Savaliya
2026-08-24 9:24 ` Konrad Dybcio
2026-08-25 17:20 ` Praveen Talari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=62eedb1a-1da7-4e65-99db-7c510844bd99@oss.qualcomm.com \
--to=kathiravan.thirumoorthy@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.savaliya@oss.qualcomm.com \
--cc=quic_mmanikan@quicinc.com \
--cc=quic_msavaliy@quicinc.com \
--cc=stable@vger.kernel.org \
--cc=viken.dadhaniya@oss.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox