mirror of https://lore.kernel.org/lkml/
 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 v2 1/1] i2c: qcom-geni: Support systems with 32MHz serial engine clock
Date: Thu, 26 Sep 2024 13:13:04 +0530	[thread overview]
Message-ID: <66719d1d-71a5-429b-b3b0-84cfb3cf8ded@quicinc.com> (raw)
In-Reply-To: <732bdb12-a52b-4abe-8edb-afed44406011@quicinc.com>



On 9/26/2024 11:44 AM, Mukesh Kumar Savaliya wrote:
> Hi Manikanta, My suggestion:
> 
> i2c: qcom-geni: Support systems with 32MHz serial engine clock
> [Derive i2c clock from 32MHz Sourced clock]
> 

As per Bjorn suggestion, i used this commit title "i2c: qcom-geni: Support systems with 32MHz serial engine clock".

> On 9/26/2024 9:13 AM, Manikanta Mylavarapu wrote:
>> In existing socs, I2C serial engine is sourced from XO (19.2MHz).
>> Where as in IPQ5424, I2C serial engine is sourced from GPLL0 (32MHz).
>>
>> The existing map table is based on 19.2MHz. This patch incorporate
> incorporate/s/incorporates

Okay, sure.

Thanks & Regards,
Manikanta.

  reply	other threads:[~2024-09-26  7:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26  3:43 Manikanta Mylavarapu
2024-09-26  6:14 ` Mukesh Kumar Savaliya
2024-09-26  7:43   ` Manikanta Mylavarapu [this message]
2024-09-26 12:44   ` Bjorn Andersson
2024-09-26 10:28 ` Vladimir Zapolskiy
2024-09-26 12:48   ` Bjorn Andersson
2024-09-29  6:32     ` Manikanta Mylavarapu
2024-09-29  6:36   ` Manikanta Mylavarapu
2024-09-30 14:45     ` Manikanta Mylavarapu
2024-10-03  7:51       ` Vladimir Zapolskiy

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=66719d1d-71a5-429b-b3b0-84cfb3cf8ded@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
all inboxes | Powered by JetHome®