From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.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 1/4] dt-bindindgs: i2c: qcom,i2c-geni: Document shared flag
Date: Mon, 2 Dec 2024 12:13:29 +0100 [thread overview]
Message-ID: <fa3ee895-5353-44f5-b816-9d17b6a7d199@kernel.org> (raw)
In-Reply-To: <904ae8ea-d970-4b4b-a30a-cd1b65296a9b@kernel.org>
On 02/12/2024 12:04, Krzysztof Kozlowski wrote:
> On 02/12/2024 11:38, Mukesh Kumar Savaliya wrote:
>>>
>>> Come with one flag or enum, if needed, covering all your cases like this.
>>>
>> Let me explain, this feature is one of the additional software case
>> adding on base protocol support. if we dont have more than one usecase
>> or repurposing this feature, why do we need to add enums ? I see one
>> flag gpi_mode but it's internal to driver not exposed to user or expose
>> any usecase/feature.
>>
>> Below was our earlier context, just wanted to add for clarity.
>> --
>> > Is sharing of IP blocks going to be also for other devices? If yes, then
>> > this should be one property for all Qualcomm devices. If not, then be
>> > sure that this is the case because I will bring it up if you come with
>> > one more solution for something else.
>
>
> You keep repeating the same. You won't receive any other answer.
>
>> >
>> IP blocks like SE can be shared. Here we are talking about I2C sharing.
>> In future it can be SPI sharing. But design wise it fits better to add
>> flag per SE node. Same we shall be adding for SPI too in future.
>
>
> How flag per SE node is relevant? I did not ask to move the property.
>
>>
>> Please let me know your further suggestions.
> We do not talk about I2C or SPI here only. We talk about entire SoC.
> Since beginning. Find other patch proposals and align with rest of
> Qualcomm developers so that you come with only one definition for this
> feature/characteristic. Or do you want to say that I am free to NAK all
> further properties duplicating this one?
>
> Please confirm that you Qualcomm engineers understand the last statement
> and that every block will use se-shared, even if we speak about UFS for
> example.
>
I think I was pretty clear also 2 months ago what do I expect from this:
https://lore.kernel.org/all/52f83419-cc5e-49f3-90a7-26a5b4ddd5a0@kernel.org/
I do not see this addressing qcom-wide way at all. Four new versions of
patch and you still did not address first fedback you got.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-12-02 11:13 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 [this message]
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
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=fa3ee895-5353-44f5-b816-9d17b6a7d199@kernel.org \
--to=krzk@kernel.org \
--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_msavaliy@quicinc.com \
--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