From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>,
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: Wed, 26 Mar 2025 15:23:08 +0100 [thread overview]
Message-ID: <991b0652-76f2-40d6-b49b-1e6f76e254ac@kernel.org> (raw)
In-Reply-To: <20250326141641.3471906-2-quic_msavaliy@quicinc.com>
On 26/03/2025 15:16, Mukesh Kumar Savaliya wrote:
> Add device tree bindings for the Qualcomm I3C controller. This includes
> the necessary documentation and properties required to describe the
> hardware in the device tree.
>
> Signed-off-by: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
> ---
> .../bindings/i3c/qcom,i3c-master.yaml | 60 +++++++++++++++++++
> 1 file changed, 60 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/i3c/qcom,i3c-master.yaml
>
> diff --git a/Documentation/devicetree/bindings/i3c/qcom,i3c-master.yaml b/Documentation/devicetree/bindings/i3c/qcom,i3c-master.yaml
> new file mode 100644
> index 000000000000..af6b393f2327
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/i3c/qcom,i3c-master.yaml
Naming: nothing improved.
> @@ -0,0 +1,60 @@
> +# SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/i3c/qcom,i3c-master.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm Geni based QUP I3C Controller
> +
> +maintainers:
> + - Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
> +
> +description:
> + 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?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-26 14:23 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 [this message]
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
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=991b0652-76f2-40d6-b49b-1e6f76e254ac@kernel.org \
--to=krzk@kernel.org \
--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=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