From: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
To: Bjorn Andersson <andersson@kernel.org>
Cc: <konrad.dybcio@linaro.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>
Subject: Re: [PATCH v3 1/4] dt-bindindgs: i2c: qcom,i2c-geni: Document shared flag
Date: Wed, 13 Nov 2024 21:38:52 +0530 [thread overview]
Message-ID: <af19d4d7-cc74-44dd-bd69-266007f68d5e@quicinc.com> (raw)
In-Reply-To: <anfqjd5rcslplfqannqqli2k2gnq2p4qsnkyrfgmavdpll7p42@c7o4tdouiav4>
Thanks Bjorn !
On 9/30/2024 8:50 AM, Bjorn Andersson wrote:
> On Fri, Sep 27, 2024 at 12:01:05PM GMT, Mukesh Kumar Savaliya wrote:
>> Adds qcom,shared-se flag usage. Use this when particular I2C serial
>> controller needs to be shared between two subsystems.
>>
>
> https://docs.kernel.org/process/submitting-patches.html#describe-your-changes
>
>> SE = Serial Engine, meant for I2C controller here.
>> TRE = Transfer Ring Element, refers to Queued Descriptor.
>> SS = Subsystems (APPS processor, Modem, TZ, ADSP etc).
>
> Expressing yourself in terms of abbreviations just makes the text harder
> to read. The dictionary is nice, but I don't see that it adds value to
> introduce these abbreviations with the reader.
Sure, thought it will ease the explanations of abbreviations. I learnt
that not to use it and directly use complete name in opensource way.
>
>>
>> Example :
>> Two clients from different SS can share an I2C SE 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.
>> This gets serialized by lock TRE + DMA Transfers + Unlock TRE at HW level.
>>
>
> Don't describe your problem using a bullet-point list. You should be
> able to express it in a flowing English sentence/paragraph.
Sure Bjorn.
>
>> 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..3b9b20a0edff 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:
>> + description: True if I2C needs to be shared between two or more subsystems(SS).
>
> I see no value in establishing the "SS" abbreviation here, what would be
> useful is to write this sentence such that it establishes the "SE"
> abbreviation (to avoid having to expand the property).
>
> On the other hand, it's a boolean property in a serial-engine node, so
> I don't know if it's worth repeating "se" here. "qcom,is-shared" sounds
> like a better boolean in a se-node.
>
Sure, Done. I thought shared-se will make it understand that SE is
shared. I will modify to qcom,is-shared as recommended.
Also i am removing SS and make it multiprocessor as asked by Bryan.
> Regards,
> Bjorn
>
>> + type: boolean
>> +
>> reg:
>> maxItems: 1
>>
>> --
>> 2.25.1
>>
next prev parent reply other threads:[~2024-11-13 16:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 6:31 [PATCH v3 0/4] Enable shared SE support over I2C Mukesh Kumar Savaliya
2024-09-27 6:31 ` [PATCH v3 1/4] dt-bindindgs: i2c: qcom,i2c-geni: Document shared flag Mukesh Kumar Savaliya
2024-09-27 9:24 ` Krzysztof Kozlowski
2024-09-27 11:20 ` Konrad Dybcio
2024-09-27 12:03 ` Krzysztof Kozlowski
2024-11-13 16:08 ` Mukesh Kumar Savaliya
2024-11-19 9:13 ` Krzysztof Kozlowski
2024-09-27 10:01 ` Krzysztof Kozlowski
2024-11-13 16:06 ` Mukesh Kumar Savaliya
2024-09-30 3:20 ` Bjorn Andersson
2024-11-13 16:08 ` Mukesh Kumar Savaliya [this message]
2024-09-27 6:31 ` [PATCH v3 2/4] dma: gpi: Add Lock and Unlock TRE support to access SE exclusively Mukesh Kumar Savaliya
2024-10-14 18:31 ` Vinod Koul
2024-11-13 16:10 ` Mukesh Kumar Savaliya
2024-10-25 18:48 ` Konrad Dybcio
2024-11-13 16:06 ` Mukesh Kumar Savaliya
2024-09-27 6:31 ` [PATCH v3 3/4] soc: qcom: geni-se: Do not keep GPIOs to sleep state for shared SE usecase Mukesh Kumar Savaliya
2024-09-30 3:27 ` Bjorn Andersson
2024-11-13 16:09 ` Mukesh Kumar Savaliya
2024-10-25 18:53 ` Konrad Dybcio
2024-11-13 16:07 ` Mukesh Kumar Savaliya
2024-09-27 6:31 ` [PATCH v3 4/4] i2c: i2c-qcom-geni: Enable i2c controller sharing between two subsystems Mukesh Kumar Savaliya
2024-09-30 3:46 ` Bjorn Andersson
2024-09-30 8:21 ` Dan Carpenter
2024-10-01 2:39 ` Bjorn Andersson
2024-11-13 16:10 ` Mukesh Kumar Savaliya
2024-11-13 16:09 ` Mukesh Kumar Savaliya
2024-10-14 21:36 ` Bryan O'Donoghue
2024-11-13 16:08 ` 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=af19d4d7-cc74-44dd-bd69-266007f68d5e@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=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;
as well as URLs for NNTP newsgroup(s).