From: Kuldeep Singh <singh.kuldeep87k@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Mukesh Savaliya <msavaliy@codeaurora.org>,
Akash Asthana <akashast@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Kuldeep Singh <singh.kuldeep87k@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-arm-msm@vger.kernel.org
Subject: [PATCH v2 2/4] dt-bindings: qcom: geni-se: Update I2C schema reference
Date: Mon, 4 Apr 2022 23:59:35 +0530 [thread overview]
Message-ID: <20220404182938.29492-3-singh.kuldeep87k@gmail.com> (raw)
In-Reply-To: <20220404182938.29492-1-singh.kuldeep87k@gmail.com>
We now have geni based QUP I2C controller binding in place as
dt-bindigs/i2c/qcom,i2c-geni-qcom.yaml similar to other controllers,
update reference in parent schema and while at it, also remove
properties defined for the controller from common wrapper.
Signed-off-by: Kuldeep Singh <singh.kuldeep87k@gmail.com>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
---
v2:
- s/i2c/I2C
- s/commown/common
- Add Krzysztof's R-b tag
---
.../bindings/soc/qcom/qcom,geni-se.yaml | 26 +------------------
1 file changed, 1 insertion(+), 25 deletions(-)
diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml b/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml
index 95fcb43675d6..e6073923e03a 100644
--- a/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml
+++ b/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml
@@ -128,31 +128,7 @@ patternProperties:
"i2c@[0-9a-f]+$":
type: object
description: GENI serial engine based I2C controller.
- $ref: /schemas/i2c/i2c-controller.yaml#
-
- properties:
- compatible:
- enum:
- - qcom,geni-i2c
-
- interrupts:
- maxItems: 1
-
- "#address-cells":
- const: 1
-
- "#size-cells":
- const: 0
-
- clock-frequency:
- description: Desired I2C bus clock frequency in Hz.
- default: 100000
-
- required:
- - compatible
- - interrupts
- - "#address-cells"
- - "#size-cells"
+ $ref: /schemas/i2c/qcom,i2c-geni-qcom.yaml#
"serial@[0-9a-f]+$":
type: object
--
2.25.1
next prev parent reply other threads:[~2022-04-04 21:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 18:29 [PATCH v2 0/4] Geni based QUP controller binding cleanups Kuldeep Singh
2022-04-04 18:29 ` [PATCH v2 1/4] dt-bindings: I2C: Add Qualcomm Geni based QUP I2C bindings Kuldeep Singh
2022-04-05 11:13 ` Krzysztof Kozlowski
2022-04-28 1:44 ` Kuldeep Singh
2022-05-03 13:10 ` Rob Herring
2022-04-04 18:29 ` Kuldeep Singh [this message]
2022-04-21 14:27 ` (subset) [PATCH v2 2/4] dt-bindings: qcom: geni-se: Update I2C schema reference Bjorn Andersson
2022-04-04 18:29 ` [PATCH v2 3/4] dt-bindings: serial: Update Qualcomm geni based QUP UART bindings Kuldeep Singh
2022-04-04 18:29 ` [PATCH v2 4/4] dt-bindings: qcom: geni-se: Update UART schema reference Kuldeep Singh
2022-04-21 14:27 ` (subset) " Bjorn Andersson
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=20220404182938.29492-3-singh.kuldeep87k@gmail.com \
--to=singh.kuldeep87k@gmail.com \
--cc=agross@kernel.org \
--cc=akashast@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msavaliy@codeaurora.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).