From: Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Mukesh Kumar Savaliya <mukesh.savaliya@oss.qualcomm.com>,
Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/3] dt-bindings: i2c: Add Qualcomm I2C slave controller
Date: Mon, 27 Jul 2026 10:06:09 +0530 [thread overview]
Message-ID: <0581856f-bcc6-4a2f-b13a-db9fe356c3c4@oss.qualcomm.com> (raw)
In-Reply-To: <2a21f549-294e-43b4-aed6-b779d84cfd4b@kernel.org>
On 6/29/2026 12:02 PM, Krzysztof Kozlowski wrote:
> On 28/06/2026 16:39, Viken Dadhaniya wrote:
>> +description:
>> + The Qualcomm I2C slave controller is a dedicated hardware IP found on
>> + Qualcomm SoCs that operates exclusively as an I2C slave device on the bus.
>> + It supports FIFO (PIO) mode for data transfer and does not function as an
>> + I2C master.
>> +
>> +properties:
>> + compatible:
>> + const: qcom,i2c-slave
>
> Such compatible makes little sense in upstream. Please look at other
> bindings how to properly create a compatible. This has to be device
> specific.
>
Sure, will update with an SoC-specific compatible string
(e.g., qcom,qdu1000-i2c-target) in the next revision.
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + interrupts:
>> + maxItems: 1
>> +
>> + clocks:
>> + items:
>> + - description: XO clock for I2C slave
>> + - description: AHB clock for I2C slave
>> +
>> + clock-names:
>> + items:
>> + - const: sm_bus_xo_clk
>> + - const: sm_bus_ahb_clk
>
> Look at other bindings.
>
Sure, updated the clock names to xo and ahb in the next revision.
>> +
>> + qcom,slave-addr:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + description:
>> + The 7-bit I2C slave address programmed into the controller's device
>> + address register. This controller operates exclusively as an I2C slave
>> + and has no child nodes, so the standard 'reg' property cannot be used
>> + to convey the I2C address (it is already used for the MMIO register
>> + range). The address is configurable at runtime via a hardware register.
>> + minimum: 0x08
>> + maximum: 0x77
>> +
>> + interconnects:
>> + maxItems: 1
>> +
>> + interconnect-names:
>> + const: i2c-slave-config
>
> i2c
>
Sure, will update to i2c in the next revision.
>> +
>> + pinctrl-0: true
>> + pinctrl-1: true
>> +
>> + pinctrl-names:
>> + minItems: 1
>> + items:
>> + - const: default
>> + - const: sleep
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - interrupts
>> + - clocks
>> + - clock-names
>> + - qcom,slave-addr
>> + - interconnects
>> + - interconnect-names
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/interrupt-controller/arm-gic.h>
>> + #include <dt-bindings/clock/qcom,qdu1000-gcc.h>
>> + #include <dt-bindings/interconnect/qcom,qdu1000-rpmh.h>
>> +
>> + i2c-slave@88ca000 {
>
> You need to fix your terminology everywhere...
>
Will update in the next revision.
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2026-07-27 4:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 14:39 [PATCH 0/3] Add Qualcomm I2C slave controller driver Viken Dadhaniya
2026-06-28 14:39 ` [PATCH v1 1/3] dt-bindings: i2c: Add Qualcomm I2C slave controller Viken Dadhaniya
2026-06-29 6:26 ` Wolfram Sang
2026-07-02 10:22 ` Mukesh Savaliya
2026-06-29 6:32 ` Krzysztof Kozlowski
2026-07-27 4:36 ` Viken Dadhaniya [this message]
2026-06-28 14:39 ` [PATCH v1 2/3] i2c: qcom-slave: Add driver for " Viken Dadhaniya
2026-06-29 6:34 ` Krzysztof Kozlowski
2026-08-02 13:18 ` Viken Dadhaniya
2026-07-02 10:53 ` Mukesh Savaliya
2026-07-05 15:53 ` Bjorn Andersson
2026-07-05 16:40 ` Wolfram Sang
2026-08-02 13:22 ` Viken Dadhaniya
2026-06-28 14:39 ` [PATCH v1 3/3] MAINTAINERS: Add entry " Viken Dadhaniya
2026-06-29 6:35 ` Krzysztof Kozlowski
2026-08-02 13:23 ` Viken Dadhaniya
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=0581856f-bcc6-4a2f-b13a-db9fe356c3c4@oss.qualcomm.com \
--to=viken.dadhaniya@oss.qualcomm.com \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.savaliya@oss.qualcomm.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