From: Michael Riesch <michael.riesch@wolfvision.net>
To: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Peter Geis <pgwipeout@gmail.com>,
Nicolas Frattaroli <frattaroli.nicolas@gmail.com>,
Michael Riesch <michael.riesch@wolfvision.net>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Alex Bee <knaerzche@gmail.com>, Liang Chen <cl@rock-chips.com>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: [PATCH v6 1/5] dt-bindings: gpu: mali-bifrost: describe clocks for the rk356x gpu
Date: Wed, 9 Feb 2022 22:55:45 +0100 [thread overview]
Message-ID: <20220209215549.94524-2-michael.riesch@wolfvision.net> (raw)
In-Reply-To: <20220209215549.94524-1-michael.riesch@wolfvision.net>
From: Alex Bee <knaerzche@gmail.com>
The Bifrost GPU in Rockchip RK356x SoCs has a core and a bus clock.
Reflect this in the SoC specific part of the binding.
Signed-off-by: Alex Bee <knaerzche@gmail.com>
[move the changes to the SoC section]
Signed-off-by: Michael Riesch <michael.riesch@wolfvision.net>
---
.../devicetree/bindings/gpu/arm,mali-bifrost.yaml | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml b/Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml
index 63a08f3f321d..4d6bfae0653c 100644
--- a/Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml
+++ b/Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml
@@ -159,6 +159,21 @@ allOf:
power-domains:
maxItems: 1
sram-supply: false
+ - if:
+ properties:
+ compatible:
+ contains:
+ const: rockchip,rk3568-mali
+ then:
+ properties:
+ clocks:
+ minItems: 2
+ clock-names:
+ items:
+ - const: gpu
+ - const: bus
+ required:
+ - clock-names
examples:
- |
--
2.30.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-02-09 21:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 21:55 [PATCH v6 0/5] Add GPU for RK356x SoCs Michael Riesch
2022-02-09 21:55 ` Michael Riesch [this message]
2022-02-11 17:07 ` [PATCH v6 1/5] dt-bindings: gpu: mali-bifrost: describe clocks for the rk356x gpu Rob Herring
2022-02-09 21:55 ` [PATCH v6 2/5] arm64: dts: rockchip: add gpu node to rk356x Michael Riesch
2022-02-09 21:55 ` [PATCH v6 3/5] arm64: dts: rockchip: add cooling map and trip points for gpu " Michael Riesch
2022-02-09 21:55 ` [PATCH v6 4/5] arm64: dts: rockchip: enable the gpu on quartz64-a Michael Riesch
2022-02-09 21:55 ` [PATCH v6 5/5] arm64: dts: rockchip: enable the gpu on rk3568-evb1-v10 Michael Riesch
2022-02-11 19:24 ` (subset) [PATCH v6 0/5] Add GPU for RK356x SoCs Heiko Stuebner
2022-02-11 19:30 ` 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=20220209215549.94524-2-michael.riesch@wolfvision.net \
--to=michael.riesch@wolfvision.net \
--cc=airlied@linux.ie \
--cc=cl@rock-chips.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=frattaroli.nicolas@gmail.com \
--cc=heiko@sntech.de \
--cc=knaerzche@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/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).