linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kuldeep Singh <singh.kuldeep87k@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	Kuldeep Singh <singh.kuldeep87k@gmail.com>
Subject: [PATCH v2 0/4] Geni based QUP controller binding cleanups
Date: Mon,  4 Apr 2022 23:59:33 +0530	[thread overview]
Message-ID: <20220404182938.29492-1-singh.kuldeep87k@gmail.com> (raw)

v1 link:
https://lore.kernel.org/lkml/20220402051206.6115-1-singh.kuldeep87k@gmail.com/

Updates:
- Address Krzysztof's comments
- Drop patch 5/5 and merge with 4/5 of v1
- In-patch updates
---

Geni based QUP controller currently has child nodes bindings defined in
same parent schema. Documentation of few other properties were also
omitted intially. The list becomes too long with addition of these
properties. Therefore, move out child bindings from parent schema to
respective places as a part of cleanup process and update reference for
it. Please note, individual bindings will now stand complete as
previously some properties were defined in core and rest in parent
schema.

This patchset adds individual bindings for uart and i2c controller, spi
controller is taken care by Krzystof. SPI patches[1] are required for
complete changes. Once all bindings gets places correctly, remove common
properties defined in parent as the final step.

[1] https://lore.kernel.org/linux-devicetree/20220404064017.68634-1-krzysztof.kozlowski@linaro.org/

Looking forward for feeback and review comments. Thanks!

Kuldeep Singh (4):
  dt-bindings: I2C: Add Qualcomm Geni based QUP I2C bindings
  dt-bindings: qcom: geni-se: Update I2C schema reference
  dt-bindings: serial: Update Qualcomm geni based QUP UART bindings
  dt-bindings: qcom: geni-se: Update UART schema reference

 .../bindings/i2c/qcom,i2c-geni-qcom.yaml      | 100 ++++++++++++++++++
 .../serial/qcom,serial-geni-qcom.yaml         |  86 +++++++++++++++
 .../bindings/soc/qcom/qcom,geni-se.yaml       |  77 +-------------
 3 files changed, 188 insertions(+), 75 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/i2c/qcom,i2c-geni-qcom.yaml
 create mode 100644 Documentation/devicetree/bindings/serial/qcom,serial-geni-qcom.yaml

-- 
2.25.1


             reply	other threads:[~2022-04-04 21:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 18:29 Kuldeep Singh [this message]
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 ` [PATCH v2 2/4] dt-bindings: qcom: geni-se: Update I2C schema reference Kuldeep Singh
2022-04-21 14:27   ` (subset) " 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-1-singh.kuldeep87k@gmail.com \
    --to=singh.kuldeep87k@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.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).