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, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org
Subject: [PATCH 5/5] dt-bindings: qcom: geni-se: Remove common controller properties
Date: Sat, 2 Apr 2022 10:42:06 +0530 [thread overview]
Message-ID: <20220402051206.6115-6-singh.kuldeep87k@gmail.com> (raw)
In-Reply-To: <20220402051206.6115-1-singh.kuldeep87k@gmail.com>
Now that Geni serial engine controllers(spi, i2c and uart) have their
own individual bindings, it's time to remove all common properties of
the controllers from parent schema.
Signed-off-by: Kuldeep Singh <singh.kuldeep87k@gmail.com>
---
.../bindings/soc/qcom/qcom,geni-se.yaml | 33 -------------------
1 file changed, 33 deletions(-)
diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml b/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml
index 9f72c676b22c..c8e1a4a87ba8 100644
--- a/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml
+++ b/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml
@@ -64,39 +64,6 @@ required:
- ranges
patternProperties:
- "^.*@[0-9a-f]+$":
- type: object
- description: Common properties for GENI Serial Engine based I2C, SPI and
- UART controller.
-
- properties:
- reg:
- description: GENI Serial Engine register address and length.
- maxItems: 1
-
- clock-names:
- const: se
-
- clocks:
- description: Serial engine core clock needed by the device.
- maxItems: 1
-
- interconnects:
- minItems: 2
- maxItems: 3
-
- interconnect-names:
- minItems: 2
- items:
- - const: qup-core
- - const: qup-config
- - const: qup-memory
-
- required:
- - reg
- - clock-names
- - clocks
-
"spi@[0-9a-f]+$":
type: object
description: GENI serial engine based SPI controller. SPI in master mode
--
2.25.1
next prev parent reply other threads:[~2022-04-02 5:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220402051206.6115-1-singh.kuldeep87k@gmail.com>
2022-04-02 5:12 ` [PATCH 1/5] dt-bindings: i2c: Add Qualcomm Geni based QUP i2c bindings Kuldeep Singh
2022-04-02 12:29 ` Krzysztof Kozlowski
2022-04-02 19:44 ` Kuldeep Singh
2022-04-02 19:57 ` Krzysztof Kozlowski
2022-04-02 18:24 ` Krzysztof Kozlowski
2022-04-02 19:34 ` Kuldeep Singh
2022-04-02 5:12 ` [PATCH 2/5] dt-bindings: qcom: geni-se: Update i2c schema reference Kuldeep Singh
2022-04-02 12:30 ` Krzysztof Kozlowski
2022-04-02 5:12 ` [PATCH 3/5] dt-bindings: serial: Update Qualcomm geni based QUP uart bindings Kuldeep Singh
2022-04-02 15:37 ` Krzysztof Kozlowski
2022-04-02 19:24 ` Kuldeep Singh
2022-04-02 5:12 ` [PATCH 4/5] dt-bindings: qcom: geni-se: Update uart schema reference Kuldeep Singh
2022-04-02 15:39 ` Krzysztof Kozlowski
2022-04-02 19:28 ` Kuldeep Singh
2022-04-02 5:12 ` Kuldeep Singh [this message]
2022-04-02 15:41 ` [PATCH 5/5] dt-bindings: qcom: geni-se: Remove common controller properties Krzysztof Kozlowski
2022-04-02 19:32 ` Kuldeep Singh
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=20220402051206.6115-6-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=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