devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: gregkh@linuxfoundation.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org,
	s.hauer@pengutronix.de, xu.yang_2@nxp.com
Cc: kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
	linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, jun.li@nxp.com,
	Peng Fan <peng.fan@nxp.com>
Subject: [PATCH V5 0/9] dt-bindings: usb: covert ci-hdrc-usb2/usbmisc-imx to yaml
Date: Sun, 19 Mar 2023 19:54:47 +0800	[thread overview]
Message-ID: <20230319115456.716969-1-peng.fan@oss.nxp.com> (raw)

From: Peng Fan <peng.fan@nxp.com>

This is target for i.MX8M* System-Ready IR 2.0 Cert.

V5:
 Fix dt warning
 Add more properties that existed in dts and driver to address dtbs check error
 Update NXP device tree to follow compatible rule
 A few dtbs fix to NXP dtbs

V4:
 Merged V3 patch 1,2,3 into one patch
 Merged V3 patch 4,5,6 into one patch
 Added patch 3,4,5,6 for dts update
 Addressed Rob's comments to v3 patch 1, patch 4 for compatible, deprecated property

V3:
 Sorry for this long time delay for V3. I thought this should be V5, but actually
 I only posted two versions before.
 Add myself ad maintainer
 The major changes are in patch 4:
   Added some properties to address dtbs_check error, for qcom, fsl. But I still leave
   some properties not introduced, such as phy-select for qcom,
   nvidia,needs-double-reset operating-points-v2 for nvidia, which I would expect
   sub-soc maintainers continue on it.

 Add A-b from Rob
 Add a new patch 7

v2:
 patch order changed, usbmisc-imx moved to first
 Add Xu Yang as maintainer
 Typo fix
 Not define properties within if/then/else
 Set additionalProperties to false
 Drop duplicated compatibles
 Fix checkpatch issue
 For pinctrl-names: I think there is restrictin in allOf, so not list items
 Add fsl,usbmisc: ref
 Define items for mux-control-names
 Rename usbmisc-imx.yaml to fsl,usbmisc.yaml

 Hope I not miss any comments

 Note: there will still be dtbs_check failure if run with only a single patch,
 with this patchset applied, there is no related dtbs_check failure.


This patchset is to convert ci-hdrc-usb2 and usbmisc-imx to yaml format.
There are compatible strings not landed in binding doc, but in device tree,
so run dtbs_check on the single yaml conversion patch will report
dtbs_check failure. If apply the whole patchset, there will be no failure.




Peng Fan (9):
  dt-bindings: usb: usbmisc-imx: convert to DT schema
  dt-bindings: usb: ci-hdrc-usb2: convert to DT schema format
  arm64: dts: imx8mn: update usb compatible
  arm64: dts: imx8mm: update usb compatible
  arm64: dts: imx8: update usb compatible
  arm64: dts: imx8dxl: update usb compatible
  arm64: dts: imx8dxl: drop #stream-id-cells for usb node
  arm64: dts: imx8-apalis-v1.1: drop ci-disable-lpm
  ARM64: dts: imx7ulp: update usb compatible

 .../devicetree/bindings/usb/ci-hdrc-usb2.txt  | 159 -------
 .../devicetree/bindings/usb/ci-hdrc-usb2.yaml | 449 ++++++++++++++++++
 .../devicetree/bindings/usb/fsl,usbmisc.yaml  |  68 +++
 .../devicetree/bindings/usb/usbmisc-imx.txt   |  19 -
 arch/arm/boot/dts/imx7ulp.dtsi                |   5 +-
 .../boot/dts/freescale/imx8-apalis-v1.1.dtsi  |   1 -
 .../boot/dts/freescale/imx8-ss-conn.dtsi      |   4 +-
 .../boot/dts/freescale/imx8dxl-ss-conn.dtsi   |   5 +-
 arch/arm64/boot/dts/freescale/imx8mm.dtsi     |  10 +-
 arch/arm64/boot/dts/freescale/imx8mn.dtsi     |   5 +-
 10 files changed, 533 insertions(+), 192 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt
 create mode 100644 Documentation/devicetree/bindings/usb/ci-hdrc-usb2.yaml
 create mode 100644 Documentation/devicetree/bindings/usb/fsl,usbmisc.yaml
 delete mode 100644 Documentation/devicetree/bindings/usb/usbmisc-imx.txt

-- 
2.37.1


             reply	other threads:[~2023-03-19 11:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19 11:54 Peng Fan (OSS) [this message]
2023-03-19 11:54 ` [PATCH V5 1/9] dt-bindings: usb: usbmisc-imx: convert to DT schema Peng Fan (OSS)
2023-03-19 11:54 ` [PATCH V5 2/9] dt-bindings: usb: ci-hdrc-usb2: convert to DT schema format Peng Fan (OSS)
2023-03-19 11:54 ` [PATCH V5 3/9] arm64: dts: imx8mn: update usb compatible Peng Fan (OSS)
2023-03-19 11:54 ` [PATCH V5 4/9] arm64: dts: imx8mm: " Peng Fan (OSS)
2023-03-19 11:54 ` [PATCH V5 5/9] arm64: dts: imx8: " Peng Fan (OSS)
2023-03-19 11:54 ` [PATCH V5 6/9] arm64: dts: imx8dxl: " Peng Fan (OSS)
2023-03-19 11:54 ` [PATCH V5 7/9] arm64: dts: imx8dxl: drop #stream-id-cells for usb node Peng Fan (OSS)
2023-03-19 11:54 ` [PATCH V5 8/9] arm64: dts: imx8-apalis-v1.1: drop ci-disable-lpm Peng Fan (OSS)
2023-03-19 11:54 ` [PATCH V5 9/9] ARM64: dts: imx7ulp: update usb compatible Peng Fan (OSS)

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=20230319115456.716969-1-peng.fan@oss.nxp.com \
    --to=peng.fan@oss.nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jun.li@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=xu.yang_2@nxp.com \
    /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).