From: Rob Herring <robh@kernel.org>
To: Alex Bee <knaerzche@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: gpu: mali-bifrost: Allow up to two clocks
Date: Wed, 1 Dec 2021 17:31:58 -0600 [thread overview]
Message-ID: <YagF7jJD4fvtr2ut@robh.at.kernel.org> (raw)
In-Reply-To: <20211126151729.1026566-2-knaerzche@gmail.com>
On Fri, Nov 26, 2021 at 04:17:26PM +0100, Alex Bee wrote:
> Commit b681af0bc1cc ("drm: panfrost: add optional bus_clock")
> added an optional bus_clock to support Allwinner H6 T-720 GPU.
That's midgard and this is bifrost... Driver changes are somewhat
irrelevant.
> Increase the max clock items in the dt-binding to reflect this.
>
> Bifrost GPU in Rockchip RK3568 SoCs also has a core and a bus clock
> and it gets added here in a (very) similar way it was done for
> allwinner,sun50i-h6-mali compatible in arm,mali-midgard binding.
I guess that one is insufficient.
>
> Signed-off-by: Alex Bee <knaerzche@gmail.com>
> ---
> .../bindings/gpu/arm,mali-bifrost.yaml | 20 ++++++++++++++++++-
> 1 file changed, 19 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml b/Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml
> index 6f98dd55fb4c..2849a7a97d73 100644
> --- a/Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml
> +++ b/Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml
> @@ -39,7 +39,14 @@ properties:
> - const: gpu
>
> clocks:
> - maxItems: 1
> + minItems: 1
> + maxItems: 2
> +
> + clock-names:
> + minItems: 1
> + items:
> + - const: core
> + - const: bus
>
> mali-supply: true
>
> @@ -118,6 +125,17 @@ allOf:
> power-domains:
> maxItems: 1
> sram-supply: false
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: rockchip,rk3568-mali
> + then:
> + properties:
> + clocks:
> + minItems: 2
clock-names:
minItems: 2
> + required:
> + - clock-names
else:
properties:
clocks:
maxItems: 1
clock-names:
maxItems: 1
>
> examples:
> - |
> --
> 2.30.2
>
>
next prev parent reply other threads:[~2021-12-01 23:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 15:17 [PATCH 0/4] add GPU for RK356x SoCs Alex Bee
2021-11-26 15:17 ` [PATCH 1/4] dt-bindings: gpu: mali-bifrost: Allow up to two clocks Alex Bee
2021-12-01 23:31 ` Rob Herring [this message]
2021-11-26 15:17 ` [PATCH 2/4] arm64: dts: rockchip: Add GPU node for rk3568 Alex Bee
2021-11-26 15:17 ` [PATCH 3/4] arm64: dts: rockchip: Add cooling map / trip points for RK356x' GPU Alex Bee
2021-11-26 15:17 ` [PATCH 4/4] arm64: dts: rockchip: Enable the GPU on Quartz64 Model A Alex Bee
2022-01-14 16:25 ` Piotr Oniszczuk
2022-01-14 16:42 ` Robin Murphy
2022-01-14 17:56 ` Piotr Oniszczuk
2021-11-29 12:15 ` [PATCH 0/4] add GPU for RK356x SoCs Ezequiel Garcia
2022-01-18 15:18 ` Heiko Stübner
-- strict thread matches above, loose matches on Subject: below --
2021-07-30 16:45 [PATCH v2 0/4] RK3568 GPU Ezequiel Garcia
2021-07-30 16:45 ` [PATCH 1/4] dt-bindings: gpu: mali-bifrost: Allow up to two clocks Ezequiel Garcia
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=YagF7jJD4fvtr2ut@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@vanguardiasur.com.ar \
--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 \
/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).