public inbox for linux-i3c@lists.infradead.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Rob Herring <robh@kernel.org>,
	Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
Cc: alexandre.belloni@bootlin.com, 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
Subject: Re: [PATCH v1 1/3] dt-bindings: i3c: Add Qualcomm I3C master controller bindings
Date: Wed, 12 Feb 2025 07:54:03 +0100	[thread overview]
Message-ID: <046a3fd9-8c31-4639-9da1-ea7f26b08249@kernel.org> (raw)
In-Reply-To: <20250211213924.GA1215572-robh@kernel.org>

On 11/02/2025 22:39, Rob Herring wrote:
> On Mon, Feb 10, 2025 at 09:42:03PM +0530, Mukesh Kumar Savaliya wrote:
>> Thanks Krzysztof !
>>
>>>
>> Sure. I reviewed other files and seems i should write as below. Please help
>> confirm.
>>
>>   compatible:
>>     items:
>>       - enum:
>>           - qcom,sm8550-i3c-master
>>       - const: qcom,i3c-master
> 
> No, that's even worse. I doubt there is some universal, never changing 
> QCom I3C master.
> 
>>>>
>>>> SoC name is not required, as this compatible is generic to all the SOCs.
>>>
>>> That's the statement you make. I accept it. I will bookmark this thread
>>> and use it whenever you try to add any future property here (to be
>>> clear: you agree you will not add new properties to fulfill *FUTURE* SoC
>>> differences).
>>>
>> Sorry, i am not saying there won't be any other compatible but i was saying
>> base driver will use "qcom,i3c-master".
>> After checking other files i realized there can be const compatible but
>> other SOC specific can be added as enum.  Hope above given way is fine.
> 
> AIUI, "geni" is some firmware based multi-protocol serial i/o controller 
> and we already have other "geni" bindings. So really, it's probably more 
> coupled to firmware versions than SoC versions. If we haven't had 
> problems with per SoC quirks with the other geni bindings, then I think 
> using the same "geni" here is fine. But we won't be happy if we start 
> seeing per SoC quirk properties.

Qualcomm IP blocks are heavily versioned. Sometimes it is version per
SoC (about which you commented enough) but mostly multiple SoCs use same
IP block. Therefore maybe this should be simply versioned according to
firmware/IP block?


Best regards,
Krzysztof

-- 
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

  reply	other threads:[~2025-02-12  6:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 14:31 [PATCH v1 0/3] Add Qualcomm i3c master controller driver support Mukesh Kumar Savaliya
2025-02-05 14:31 ` [PATCH v1 1/3] dt-bindings: i3c: Add Qualcomm I3C master controller bindings Mukesh Kumar Savaliya
2025-02-05 14:42   ` Krzysztof Kozlowski
2025-02-06 13:43     ` Mukesh Kumar Savaliya
2025-02-07 12:03       ` Mukesh Kumar Savaliya
2025-02-09 11:46         ` Krzysztof Kozlowski
2025-02-10 16:11           ` Mukesh Kumar Savaliya
2025-02-09 11:45       ` Krzysztof Kozlowski
2025-02-10 16:12         ` Mukesh Kumar Savaliya
2025-02-11 21:39           ` Rob Herring
2025-02-12  6:54             ` Krzysztof Kozlowski [this message]
2025-02-12 14:15             ` Mukesh Kumar Savaliya
2025-02-05 14:31 ` [PATCH v1 2/3] i3c: master: Add Qualcomm I3C master controller driver Mukesh Kumar Savaliya
2025-02-05 14:46   ` Krzysztof Kozlowski
2025-02-07 12:03     ` Mukesh Kumar Savaliya
2025-02-09 11:40       ` Krzysztof Kozlowski
2025-02-10 16:11         ` Mukesh Kumar Savaliya
2025-02-11 21:41           ` Rob Herring
2025-02-12 19:29             ` Mukesh Kumar Savaliya
2025-02-12 19:39               ` Krzysztof Kozlowski
2025-02-12 19:49                 ` Mukesh Kumar Savaliya
2025-02-06 16:48   ` Frank Li
2025-02-07 12:16     ` Mukesh Kumar Savaliya
2025-02-05 14:31 ` [PATCH v1 3/3] MAINTAINERS: Add maintainer for Qualcomm's I3C driver Mukesh Kumar Savaliya
2025-02-05 16:23 ` [PATCH v1 0/3] Add Qualcomm i3c master controller driver support Wolfram Sang
2025-02-07 12:05   ` 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=046a3fd9-8c31-4639-9da1-ea7f26b08249@kernel.org \
    --to=krzk@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_msavaliy@quicinc.com \
    --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