public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
To: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>,
	<andi.shyti@kernel.org>, <linux-arm-msm@vger.kernel.org>,
	<linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <quic_srichara@quicinc.com>, <quic_varada@quicinc.com>
Subject: Re: [PATCH 1/1] i2c: qcom-geni: add 32MHz I2C SE clock support for IPQ5424
Date: Wed, 25 Sep 2024 15:33:12 +0530	[thread overview]
Message-ID: <e989c40b-e104-469b-84c1-f6c8e59ccfba@quicinc.com> (raw)
In-Reply-To: <ad86f820-1e9f-4e15-b106-3e2136dbf438@quicinc.com>



On 9/25/2024 3:25 PM, Mukesh Kumar Savaliya wrote:
> Thanks manikanta !
> 
> On 9/25/2024 2:14 PM, Manikanta Mylavarapu wrote:
>>
>>
>> On 9/25/2024 1:06 PM, Mukesh Kumar Savaliya wrote:
>>> Hi Manikanta,
>>>
>>> On 9/24/2024 12:20 PM, Manikanta Mylavarapu wrote:
>>>> The IPQ5424 I2C SE clock operates at a frequency of 32MHz. Since the
>>> would it be better to say , I2C SE is sourced from 32MHZ ?
>>
>> Okay, sure.
>>
>>>> existing map table is based on 19.2MHz, this patch incorporate the
>>> based on 19.2MHz. this patch /,/.
>>
>> Okay, sure.
>>
>>>> clock map table to derive the SCL clock from the 32MHz SE clock.
>>> from the 32MHz Source Clock frequency.
>>> SE = Expand OR  (I2C Serial Engine Controller)
>>
>> Okay, sure.
>>
> Please also mention the reason why 32MHz got added ? Need to describe evolution to understand the purpose behind this change.

Okay, sure.

Thanks & Regards,
Manikanta.

      reply	other threads:[~2024-09-25 10:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-24  6:50 [PATCH 1/1] i2c: qcom-geni: add 32MHz I2C SE clock support for IPQ5424 Manikanta Mylavarapu
2024-09-24 20:45 ` Bjorn Andersson
2024-09-25  5:54   ` Manikanta Mylavarapu
2024-09-25  5:39 ` Vladimir Zapolskiy
2024-09-25  6:22   ` Manikanta Mylavarapu
2024-09-25  7:36 ` Mukesh Kumar Savaliya
2024-09-25  8:44   ` Manikanta Mylavarapu
2024-09-25  9:55     ` Mukesh Kumar Savaliya
2024-09-25 10:03       ` Manikanta Mylavarapu [this message]

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=e989c40b-e104-469b-84c1-f6c8e59ccfba@quicinc.com \
    --to=quic_mmanikan@quicinc.com \
    --cc=andi.shyti@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_msavaliy@quicinc.com \
    --cc=quic_srichara@quicinc.com \
    --cc=quic_varada@quicinc.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