From: Heiko Stuebner <heiko@sntech.de>
To: Johan Jonker <jbx6244@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-rockchip@lists.infradead.org, robh+dt@kernel.org
Subject: Re: (subset) [PATCH v2 1/4] ARM: dts: rockchip: add QoS register compatibles for rk3066/rk3188
Date: Sat, 9 Jan 2021 16:39:49 +0100 [thread overview]
Message-ID: <161020678303.3482489.18290216929874336363.b4-ty@sntech.de> (raw)
In-Reply-To: <20201206103711.7465-1-jbx6244@gmail.com>
On Sun, 6 Dec 2020 11:37:08 +0100, Johan Jonker wrote:
> With the conversion of syscon.yaml minItems for compatibles
> was set to 2. Current Rockchip dtsi files only use "syscon" for
> QoS registers. Add Rockchip QoS compatibles for rk3066/rk3188
> to reduce notifications produced with:
>
> make ARCH=arm dtbs_check
> DT_SCHEMA_FILES=Documentation/devicetree/bindings/mfd/syscon.yaml
Applied, thanks!
[3/4] arm64: dts: rockchip: add QoS register compatibles for rk3399
commit: bd3fd04910ab5e4d571c19f50c341de175597dfa
[4/4] arm64: dts: rockchip: add QoS register compatibles for px30
commit: 6c3ae9f9a133d387ef4e1b4297c9df4e9a1c469d
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
prev parent reply other threads:[~2021-01-09 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 10:37 [PATCH v2 1/4] ARM: dts: rockchip: add QoS register compatibles for rk3066/rk3188 Johan Jonker
2020-12-06 10:37 ` [PATCH v2 2/4] ARM: dts: rockchip: add QoS register compatibles for rk3288 Johan Jonker
2020-12-06 10:37 ` [PATCH v2 3/4] arm64: dts: rockchip: add QoS register compatibles for rk3399 Johan Jonker
2020-12-06 10:37 ` [PATCH v2 4/4] arm64: dts: rockchip: add QoS register compatibles for px30 Johan Jonker
2021-01-09 15:39 ` Heiko Stuebner [this message]
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=161020678303.3482489.18290216929874336363.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=jbx6244@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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).