public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
To: Rob Herring <robh@kernel.org>
Cc: <konrad.dybcio@linaro.org>, <andersson@kernel.org>,
	<andi.shyti@kernel.org>, <linux-arm-msm@vger.kernel.org>,
	<dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-i2c@vger.kernel.org>, <conor+dt@kernel.org>,
	<agross@kernel.org>, <devicetree@vger.kernel.org>,
	<vkoul@kernel.org>, <linux@treblig.org>,
	<dan.carpenter@linaro.org>, <Frank.Li@nxp.com>,
	<konradybcio@kernel.org>, <bryan.odonoghue@linaro.org>,
	<krzk+dt@kernel.org>, <quic_vdadhani@quicinc.com>
Subject: Re: [PATCH v4 1/4] dt-bindindgs: i2c: qcom,i2c-geni: Document shared flag
Date: Sun, 17 Nov 2024 23:15:51 +0530	[thread overview]
Message-ID: <ff20d185-4db4-482b-b6dd-06e46124b8ab@quicinc.com> (raw)
In-Reply-To: <20241115173156.GA3432253-robh@kernel.org>

Thanks Rob for your review and comments !

On 11/15/2024 11:01 PM, Rob Herring wrote:
> On Wed, Nov 13, 2024 at 09:44:10PM +0530, Mukesh Kumar Savaliya wrote:
>> Adds qcom,is-shared flag usage. Use this flag when I2C serial controller
> 
> Doesn't match the property name.
Sure, i need to change the name here as qcom,shared-se, will upload a 
new patch.
> 
>> needs to be shared in multiprocessor system(APPS,Modem,ADSP) environment.
>>
>> Two clients from different processors can share an I2C controller for same
>> slave device OR their owned slave devices. Assume I2C Slave EEPROM device
>> connected with I2C controller. Each client from ADSP SS and APPS Linux SS
>> can perform i2c transactions.
>>
>> Transfer gets serialized by Lock TRE + DMA xfer + Unlock TRE at HW level.
>>
>> Signed-off-by: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
>> ---
>>   Documentation/devicetree/bindings/i2c/qcom,i2c-geni-qcom.yaml | 4 ++++
>>   1 file changed, 4 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/i2c/qcom,i2c-geni-qcom.yaml b/Documentation/devicetree/bindings/i2c/qcom,i2c-geni-qcom.yaml
>> index 9f66a3bb1f80..fe36938712f7 100644
>> --- a/Documentation/devicetree/bindings/i2c/qcom,i2c-geni-qcom.yaml
>> +++ b/Documentation/devicetree/bindings/i2c/qcom,i2c-geni-qcom.yaml
>> @@ -60,6 +60,10 @@ properties:
>>     power-domains:
>>       maxItems: 1
>>   
>> +  qcom,shared-se:
> 
> What is 'se'? Is that defined somewhere?
> 
SE is Serial Engine acting as I2C controller. Let me add second line for 
SE here also.

It's mentioned in source code in Patch 3 where it's used.
 >>> True if serial engine is shared between multiprocessors OR 
Execution Environment.

>> +    description: True if I2C controller is shared between two or more system processors.
>> +    type: boolean
>> +
>>     reg:
>>       maxItems: 1
>>   
>> -- 
>> 2.25.1
>>

  reply	other threads:[~2024-11-17 17:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-13 16:14 [PATCH v4 0/4] Enable shared SE support over I2C Mukesh Kumar Savaliya
2024-11-13 16:14 ` [PATCH v4 1/4] dt-bindindgs: i2c: qcom,i2c-geni: Document shared flag Mukesh Kumar Savaliya
2024-11-15 17:31   ` Rob Herring
2024-11-17 17:45     ` Mukesh Kumar Savaliya [this message]
2024-11-25  8:11       ` Krzysztof Kozlowski
2024-11-29 14:43         ` Mukesh Kumar Savaliya
2024-11-29 15:12           ` Krzysztof Kozlowski
2024-11-13 16:14 ` [PATCH v4 2/4] dmaengine: gpi: Add Lock and Unlock TRE support to access I2C exclusively Mukesh Kumar Savaliya
2024-11-15 19:23   ` Konrad Dybcio
2024-11-18  5:46     ` Mukesh Kumar Savaliya
2024-11-22 13:40       ` Konrad Dybcio
2024-11-25  5:01         ` Mukesh Kumar Savaliya
2024-11-13 16:14 ` [PATCH v4 3/4] soc: qcom: geni-se: Do not keep GPIOs to sleep state for shared SE usecase Mukesh Kumar Savaliya
2024-11-13 16:14 ` [PATCH v4 4/4] i2c: i2c-qcom-geni: Enable i2c controller sharing between two subsystems Mukesh Kumar Savaliya
2024-11-15 19:28   ` Konrad Dybcio
2024-11-18  5:45     ` Mukesh Kumar Savaliya
2024-11-22 13:42       ` Konrad Dybcio
2024-11-25  5:26         ` Mukesh Kumar Savaliya

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=ff20d185-4db4-482b-b6dd-06e46124b8ab@quicinc.com \
    --to=quic_msavaliy@quicinc.com \
    --cc=Frank.Li@nxp.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@treblig.org \
    --cc=quic_vdadhani@quicinc.com \
    --cc=robh@kernel.org \
    --cc=vkoul@kernel.org \
    /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