public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	<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>, <robh@kernel.org>
Cc: <quic_vdadhani@quicinc.com>
Subject: Re: [PATCH v5 4/4] i2c: i2c-qcom-geni: Enable i2c controller sharing between two subsystems
Date: Sun, 15 Dec 2024 14:29:12 +0530	[thread overview]
Message-ID: <57815272-bc07-4c5e-8ae6-8bf8eaaca78f@quicinc.com> (raw)
In-Reply-To: <ce9f1ab1-56a0-4c0a-aa5b-f044111288ec@oss.qualcomm.com>

Hi Konrad,

On 12/13/2024 6:35 PM, Konrad Dybcio wrote:
> On 29.11.2024 3:43 PM, Mukesh Kumar Savaliya wrote:
>> Add support to share I2C controller in multiprocessor system in a mutually
>> exclusive way. Use "qcom,shared-se" flag in a particular i2c instance node
>> if the usecase requires i2c controller to be shared.
>>
>> Sharing of I2C SE(Serial engine) is possible only for GSI mode as client
>> from each processor can queue transfers over its own GPII Channel. For
>> non GSI mode, we should force disable this feature even if set by user
>> from DT by mistake.
>>
>> I2C driver just need to mark first_msg and last_msg flag to help indicate
>> GPI driver to take lock and unlock TRE there by protecting from concurrent
>> access from other EE or Subsystem.
>>
>> gpi_create_i2c_tre() function at gpi.c will take care of adding Lock and
>> Unlock TRE for the respective transfer operations.
>>
>> Since the GPIOs are also shared between two SS, do not unconfigure them
>> during runtime suspend. This will allow other SS to continue to transfer
>> the data without any disturbance over the IO lines.
>>
>> For example, Assume an I2C EEPROM device connected with an I2C controller.
>> Each client from ADSP and APPS processor can perform i2c transactions
>> without any disturbance from each other.
>>
>> Signed-off-by: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
>> ---
>>   drivers/i2c/busses/i2c-qcom-geni.c | 22 +++++++++++++++++++---
>>   1 file changed, 19 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/i2c/busses/i2c-qcom-geni.c b/drivers/i2c/busses/i2c-qcom-geni.c
>> index 7a22e1f46e60..ccf9933e2dad 100644
>> --- a/drivers/i2c/busses/i2c-qcom-geni.c
>> +++ b/drivers/i2c/busses/i2c-qcom-geni.c
>> @@ -1,5 +1,6 @@
>>   // SPDX-License-Identifier: GPL-2.0
>>   // Copyright (c) 2017-2018, The Linux Foundation. All rights reserved.
>> +// Copyright (c) 2024 Qualcomm Innovation Center, Inc. All rights reserved.
>>   
>>   #include <linux/acpi.h>
>>   #include <linux/clk.h>
>> @@ -617,6 +618,7 @@ static int geni_i2c_gpi_xfer(struct geni_i2c_dev *gi2c, struct i2c_msg msgs[], i
>>   	peripheral.clk_div = itr->clk_div;
>>   	peripheral.set_config = 1;
>>   	peripheral.multi_msg = false;
>> +	peripheral.shared_se = gi2c->se.shared_geni_se;
>>   
>>   	for (i = 0; i < num; i++) {
>>   		gi2c->cur = &msgs[i];
>> @@ -627,6 +629,8 @@ static int geni_i2c_gpi_xfer(struct geni_i2c_dev *gi2c, struct i2c_msg msgs[], i
>>   		if (i < num - 1)
>>   			peripheral.stretch = 1;
>>   
>> +		peripheral.first_msg = (i == 0);
>> +		peripheral.last_msg = (i == num - 1);
>>   		peripheral.addr = msgs[i].addr;
>>   
>>   		ret =  geni_i2c_gpi(gi2c, &msgs[i], &config,
>> @@ -815,6 +819,11 @@ static int geni_i2c_probe(struct platform_device *pdev)
>>   		gi2c->clk_freq_out = KHZ(100);
>>   	}
>>   
>> +	if (of_property_read_bool(pdev->dev.of_node, "qcom,shared-se")) {
>> +		gi2c->se.shared_geni_se = true;
>> +		dev_dbg(&pdev->dev, "I2C is shared between subsystems\n");
>> +	}
>> +
>>   	if (has_acpi_companion(dev))
>>   		ACPI_COMPANION_SET(&gi2c->adap.dev, ACPI_COMPANION(dev));
>>   
>> @@ -887,8 +896,10 @@ static int geni_i2c_probe(struct platform_device *pdev)
>>   	else
>>   		fifo_disable = readl_relaxed(gi2c->se.base + GENI_IF_DISABLE_RO) & FIFO_IF_DISABLE;
>>   
>> -	if (fifo_disable) {
>> -		/* FIFO is disabled, so we can only use GPI DMA */
>> +	if (fifo_disable || gi2c->se.shared_geni_se) {
>> +		/* FIFO is disabled, so we can only use GPI DMA.
>> +		 * SE can be shared in GSI mode between subsystems, each SS owns a GPII.
>> +		 **/
> 
> I don't think this change makes things clearer, I would drop it
Shall i revert back to previous change ? What's your suggestion ?
> 
>>   		gi2c->gpi_mode = true;
>>   		ret = setup_gpi_dma(gi2c);
>>   		if (ret) {
>> @@ -900,6 +911,12 @@ static int geni_i2c_probe(struct platform_device *pdev)
>>   		dev_dbg(dev, "Using GPI DMA mode for I2C\n");
>>   	} else {
>>   		gi2c->gpi_mode = false;
>> +
>> +		if (gi2c->se.shared_geni_se) {
>> +			dev_err(dev, "I2C sharing is not supported in non GSI mode\n");
>> +			return -EINVAL;
> 
> return dev_err_probe(dev, -EINVAL, "I2C...)
Yes, will incorporate this change in next patch. dt-binding change i am 
seeking something good writeup, then will upload V6. Thanks Konrad !
> 
> Konrad


  reply	other threads:[~2024-12-15  8:59 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-29 14:43 [PATCH v5 0/4] Enable shared SE support over I2C Mukesh Kumar Savaliya
2024-11-29 14:43 ` [PATCH v5 1/4] dt-bindindgs: i2c: qcom,i2c-geni: Document shared flag Mukesh Kumar Savaliya
2024-11-29 15:14   ` Krzysztof Kozlowski
2024-12-02  4:00     ` Mukesh Kumar Savaliya
2024-12-02  7:19       ` Krzysztof Kozlowski
2024-12-02 10:38         ` Mukesh Kumar Savaliya
2024-12-02 11:04           ` Krzysztof Kozlowski
2024-12-02 11:13             ` Krzysztof Kozlowski
2024-12-09 15:07               ` Mukesh Kumar Savaliya
2024-12-02 12:55             ` Mukesh Kumar Savaliya
2024-12-02 14:04               ` Konrad Dybcio
2024-12-09 15:01                 ` Mukesh Kumar Savaliya
2024-12-10  7:28                 ` Krzysztof Kozlowski
2024-12-10  9:09                   ` Konrad Dybcio
2024-12-10 11:53                     ` Krzysztof Kozlowski
2024-12-10 12:05                       ` Krzysztof Kozlowski
2024-12-10 12:38                         ` Konrad Dybcio
2024-12-10 15:17                           ` Mukesh Kumar Savaliya
2024-12-10 15:24                             ` Konrad Dybcio
2024-12-10 15:56                               ` Krzysztof Kozlowski
2024-12-10 17:52                           ` Bjorn Andersson
2026-03-31 11:32                             ` Mukesh Kumar Savaliya
2024-11-30  4:45   ` Bjorn Andersson
2024-12-02 10:38     ` Mukesh Kumar Savaliya
2024-12-03 15:43       ` Bjorn Andersson
2024-11-29 14:43 ` [PATCH v5 2/4] dmaengine: gpi: Add Lock and Unlock TRE support to access I2C exclusively Mukesh Kumar Savaliya
2024-12-02  6:47   ` Vinod Koul
2024-12-02 10:43     ` Mukesh Kumar Savaliya
2024-12-04 12:21       ` Vinod Koul
2024-12-18 12:34         ` Mukesh Kumar Savaliya
2024-12-24  9:58           ` Vinod Koul
2024-12-26 12:22             ` Mukesh Kumar Savaliya
2025-01-14  9:18               ` Mukesh Kumar Savaliya
2026-03-31 11:33                 ` Mukesh Kumar Savaliya
2024-11-29 14:43 ` [PATCH v5 3/4] soc: qcom: geni-se: Do not keep GPIOs to sleep state for shared SE usecase Mukesh Kumar Savaliya
2024-11-29 14:43 ` [PATCH v5 4/4] i2c: i2c-qcom-geni: Enable i2c controller sharing between two subsystems Mukesh Kumar Savaliya
2024-12-13 13:05   ` Konrad Dybcio
2024-12-15  8:59     ` Mukesh Kumar Savaliya [this message]
2024-12-16 12:10       ` Konrad Dybcio
2024-12-16 12:47         ` Mukesh Kumar Savaliya
2026-03-31 11:34           ` 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=57815272-bc07-4c5e-8ae6-8bf8eaaca78f@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=konrad.dybcio@oss.qualcomm.com \
    --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