From: Rob Herring <robh@kernel.org>
To: Michael Riesch <michael.riesch@wolfvision.net>
Cc: 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,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Heiko Stuebner <heiko@sntech.de>,
Peter Geis <pgwipeout@gmail.com>,
Nicolas Frattaroli <frattaroli.nicolas@gmail.com>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Alex Bee <knaerzche@gmail.com>, Liang Chen <cl@rock-chips.com>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH v5 1/5] dt-bindings: gpu: mali-bifrost: describe clocks for the rk356x gpu
Date: Wed, 9 Feb 2022 11:52:59 -0600 [thread overview]
Message-ID: <YgP/e29ZPgBW/c05@robh.at.kernel.org> (raw)
In-Reply-To: <20220209085110.3588035-2-michael.riesch@wolfvision.net>
On Wed, Feb 09, 2022 at 09:51:06AM +0100, Michael Riesch wrote:
> 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..21409c8d3813 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: core
> + - const: bus
Please don't invent new names. We already have 'gpu' and 'bus' defined.
'core' and 'gpu' sound like the same thing to me, and the h/w doesn't
have different clocks from vendor to vendor.
Rob
_______________________________________________
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 17:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 8:51 [PATCH v5 0/5] Add GPU for RK356x SoCs Michael Riesch
2022-02-09 8:51 ` [PATCH v5 1/5] dt-bindings: gpu: mali-bifrost: describe clocks for the rk356x gpu Michael Riesch
2022-02-09 15:35 ` Rob Herring
2022-02-09 15:46 ` Michael Riesch
2022-02-09 16:28 ` Heiko Stübner
2022-02-09 17:48 ` Rob Herring
2022-02-09 17:52 ` Rob Herring [this message]
2022-02-09 8:51 ` [PATCH v5 2/5] arm64: dts: rockchip: add gpu node to rk356x Michael Riesch
2022-02-09 8:51 ` [PATCH v5 3/5] arm64: dts: rockchip: add cooling map and trip points for gpu " Michael Riesch
2022-02-09 8:51 ` [PATCH v5 4/5] arm64: dts: rockchip: enable the gpu on quartz64-a Michael Riesch
2022-02-09 8:51 ` [PATCH v5 5/5] arm64: dts: rockchip: enable the gpu on rk3568-evb1-v10 Michael Riesch
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=YgP/e29ZPgBW/c05@robh.at.kernel.org \
--to=robh@kernel.org \
--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=michael.riesch@wolfvision.net \
--cc=pgwipeout@gmail.com \
--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).