From: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
<alexandre.belloni@bootlin.com>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<jarkko.nikula@linux.intel.com>, <linux-i3c@lists.infradead.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <andersson@kernel.org>, <konradybcio@kernel.org>
Subject: Re: [PATCH v2 1/3] dt-bindings: i3c: Add Qualcomm I3C master controller
Date: Sat, 29 Mar 2025 20:01:03 +0530 [thread overview]
Message-ID: <838dfc8d-24c3-4f03-9c24-863259bb22b1@quicinc.com> (raw)
In-Reply-To: <04945ad2-1372-4c73-beae-fc6449fb9a76@kernel.org>
On 3/29/2025 4:36 PM, Krzysztof Kozlowski wrote:
> On 29/03/2025 10:08, Mukesh Kumar Savaliya wrote:
>>>>>> + I3C in master mode supports up to 12.5MHz, SDR mode data transfer in mixed
>>>>>> + bus mode (I2C and I3C target devices on same i3c bus). It also supports
>>>>>> + hotjoin, IBI mechanism.
>>>>>> +
>>>>>> + I3C Controller nodes must be child of GENI based Qualcomm Universal
>>>>>> + Peripharal. Please refer GENI based QUP wrapper controller node bindings
>>>>>> + described in Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml.
>>>>>> +
>>>>>> +allOf:
>>>>>> + - $ref: i3c.yaml#
>>>>>> +
>>>>>> +properties:
>>>>>> + compatible:
>>>>>> + const: qcom,i3c-master
>>>>>
>>>>> And this got worse. It makes also no sense either: how can you claim
>>>>> that this covers all possible future I3C masters from Qualcomm?
>>>>>
>>>>> What was the resolution of previous discussion?
>>>>>
>>>> Below was my understanding and reply.
>>>> "
>>>> I think i should remove const. kept it for now as no other compatible to
>>>> be added as of now.
>>>> let me remove const.
>>>> SoC name is not required, as this compatible is generic to all the SOCs.
>>>
>>> I don't see any talks about const, what are you referring to?
>>>
>> +properties:
>> + compatible:
>> + : qcom,i3c-geni
>> will this be fine ?
>
> Yes, I think that was also suggested by Rob. Or rather follow existing
> style so qcom,geni-i3c for the compatible and filename.
>
Sure, makes sense. With below i3c becomes similar in naming conventions
to spi, i2c, serial uart.
Driver file name : i3c-qcom-geni.c
dt-binding file name: qcom,i3c-geni-qcom.yaml
compatible = "qcom,geni-i3c";
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2025-03-29 14:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 14:16 [PATCH v2 0/3] Add Qualcomm i3c master controller driver support Mukesh Kumar Savaliya
2025-03-26 14:16 ` [PATCH v2 1/3] dt-bindings: i3c: Add Qualcomm I3C master controller Mukesh Kumar Savaliya
2025-03-26 14:23 ` Krzysztof Kozlowski
2025-03-28 14:28 ` Mukesh Kumar Savaliya
2025-03-28 14:33 ` Krzysztof Kozlowski
2025-03-29 9:08 ` Mukesh Kumar Savaliya
2025-03-29 11:06 ` Krzysztof Kozlowski
2025-03-29 14:31 ` Mukesh Kumar Savaliya [this message]
2025-03-30 9:42 ` Krzysztof Kozlowski
2025-03-31 6:52 ` Mukesh Kumar Savaliya
2025-03-31 7:06 ` Mukesh Kumar Savaliya
2025-03-26 14:16 ` [PATCH v2 2/3] i3c: master: Add Qualcomm I3C controller driver Mukesh Kumar Savaliya
2025-03-26 14:28 ` Krzysztof Kozlowski
2025-03-28 14:28 ` Mukesh Kumar Savaliya
2025-03-28 14:35 ` Krzysztof Kozlowski
2025-03-26 20:03 ` Frank Li
2025-03-29 9:09 ` Mukesh Kumar Savaliya
2025-03-28 13:19 ` Markus Elfring
2025-03-28 14:29 ` Mukesh Kumar Savaliya
2025-03-28 19:04 ` [v2 " Markus Elfring
2025-03-29 9:08 ` Mukesh Kumar Savaliya
2025-03-29 9:43 ` Markus Elfring
2025-03-29 10:48 ` Alexandre Belloni
2025-03-29 13:16 ` Markus Elfring
2025-03-29 14:27 ` Mukesh Kumar Savaliya
2025-03-28 13:28 ` [PATCH v2 " Markus Elfring
2025-03-28 14:29 ` Mukesh Kumar Savaliya
2025-03-26 14:16 ` [PATCH v2 3/3] MAINTAINERS: Add maintainer for Qualcomm's I3C driver 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=838dfc8d-24c3-4f03-9c24-863259bb22b1@quicinc.com \
--to=quic_msavaliy@quicinc.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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