From: Diederik de Haas <didi.debian@cknow.org>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: Diederik de Haas <didi.debian@cknow.org>,
Dragan Simic <dsimic@manjaro.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: rockchip: Fix several DT validation errors
Date: Mon, 7 Oct 2024 12:28:15 +0200 [thread overview]
Message-ID: <20241007105657.6203-2-didi.debian@cknow.org> (raw)
This is a set of 4 small device-tree validation fixes.
Patch 1 adds the power-domains property to the csi dphy node on rk356x.
Patch 2 removes the 2nd interrupt from the hdmi node on rk3328.
Patch 3 replaces 'wake' with 'wakeup' on brcm BT nodes.
Patch 4 replaces 'reset-gpios' with 'shutdown-gpios' on brcm BT nodes.
arch/arm64/boot/dts/rockchip/rk3328.dtsi | 3 +--
arch/arm64/boot/dts/rockchip/rk3566-box-demo.dts | 4 ++--
arch/arm64/boot/dts/rockchip/rk3566-pinenote.dtsi | 6 +++---
arch/arm64/boot/dts/rockchip/rk3566-radxa-cm3.dtsi | 2 +-
arch/arm64/boot/dts/rockchip/rk356x.dtsi | 1 +
5 files changed, 8 insertions(+), 8 deletions(-)
next reply other threads:[~2024-10-07 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 10:28 Diederik de Haas [this message]
2024-10-07 10:28 ` [PATCH 1/4] arm64: dts: rockchip: Add PD to csi dphy node on rk356x Diederik de Haas
2024-10-07 10:28 ` [PATCH 2/4] arm64: dts: rockchip: Remove hdmi's 2nd interrupt on rk3328 Diederik de Haas
2024-10-07 10:28 ` [PATCH 3/4] arm64: dts: rockchip: Fix wakeup prop names on brcm BT nodes Diederik de Haas
2024-10-07 14:06 ` Heiko Stübner
2024-10-07 14:22 ` Diederik de Haas
2024-10-07 10:28 ` [PATCH 4/4] arm64: dts: rockchip: Fix reset-gpios prop " Diederik de Haas
2024-10-07 14:04 ` Heiko Stübner
2024-10-07 14:28 ` Diederik de Haas
2024-10-07 18:44 ` rockchip: Fix several DT validation errors Rob Herring (Arm)
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=20241007105657.6203-2-didi.debian@cknow.org \
--to=didi.debian@cknow.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@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).