From: Johan Jonker <jbx6244@gmail.com>
To: heiko@sntech.de
Cc: robh+dt@kernel.org, kishon@ti.com, vkoul@kernel.org,
t.schramm@manjaro.org, linux-phy@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v7 0/5] convert grf.txt to YAML
Date: Tue, 1 Jun 2021 18:47:55 +0200 [thread overview]
Message-ID: <20210601164800.7670-1-jbx6244@gmail.com> (raw)
Changed V7:
rebase
add compatible for rk3308 USB grf
add "rockchip,rk3308-usb2phy-grf" to "usb2phy@[0-9a-f]+$"
patternProperties too
add USB support to rk3308.dtsi
restyle
limit grf reg size
change sub nodename
remove applied patches
Changed V6:
remove some #phy-cells in rockchip-usb-phy.yaml
rename nodename for phy-rockchip-inno-usb2
remove applied patches
Changed V5:
changed compatibles for rk3066/rk3188
add rockchip-usb-phy.yaml
move and restyle grf nodes rk3066/rk3188
remove applied patches
Changed V4:
revert separate schemas for each 'if' subset
add additionalProperties
move properties to top level
Changed V3:
remove select
change unevaluatedProperties
add separate schemas for each 'if' subset
Changed V2:
add rockchip,rk3328-grf-gpio.yaml
rename grf-gpio nodename
Johan Jonker (3):
dt-bindings: phy: rename phy nodename in phy-rockchip-inno-usb2.yaml
ARM: dts: rockchip: rename nodename for phy-rockchip-inno-usb2
arm64: dts: rockchip: rename nodename for phy-rockchip-inno-usb2
Tobias Schramm (2):
dt-bindings: soc: rockchip: grf: add compatible for RK3308 USB grf
arm64: dts: rockchip: add USB support to rk3308.dtsi
.../bindings/phy/phy-rockchip-inno-usb2.yaml | 11 +---
.../devicetree/bindings/soc/rockchip/grf.yaml | 6 +-
arch/arm/boot/dts/rk322x.dtsi | 4 +-
arch/arm/boot/dts/rv1108.dtsi | 2 +-
arch/arm64/boot/dts/rockchip/px30.dtsi | 2 +-
arch/arm64/boot/dts/rockchip/rk3308.dtsi | 74 +++++++++++++++++++++-
arch/arm64/boot/dts/rockchip/rk3328.dtsi | 2 +-
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 4 +-
8 files changed, 87 insertions(+), 18 deletions(-)
--
2.11.0
next reply other threads:[~2021-06-01 16:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 16:47 Johan Jonker [this message]
2021-06-01 16:47 ` [PATCH v7 1/5] dt-bindings: phy: rename phy nodename in phy-rockchip-inno-usb2.yaml Johan Jonker
2021-06-03 5:54 ` Vinod Koul
2021-06-03 8:58 ` Heiko Stübner
2021-06-07 13:16 ` Rob Herring
2021-06-07 13:38 ` Johan Jonker
2021-06-07 14:18 ` [PATCH] dt-bindings: soc: rockchip: drop unnecessary #phy-cells from grf.yaml Heiko Stuebner
2021-06-07 15:37 ` Johan Jonker
2021-06-10 7:30 ` Heiko Stübner
2021-06-01 16:47 ` [PATCH v7 2/5] dt-bindings: soc: rockchip: grf: add compatible for RK3308 USB grf Johan Jonker
2021-06-02 18:17 ` Rob Herring
2021-06-01 16:47 ` [PATCH v7 3/5] ARM: dts: rockchip: rename nodename for phy-rockchip-inno-usb2 Johan Jonker
2021-06-01 16:47 ` [PATCH v7 4/5] arm64: " Johan Jonker
2021-06-01 16:48 ` [PATCH v7 5/5] arm64: dts: rockchip: add USB support to rk3308.dtsi Johan Jonker
2021-06-03 9:56 ` [PATCH v7 0/5] convert grf.txt to YAML Heiko Stuebner
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=20210601164800.7670-1-jbx6244@gmail.com \
--to=jbx6244@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=t.schramm@manjaro.org \
--cc=vkoul@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).