From: Steven Price <steven.price@arm.com>
To: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
dri-devel@lists.freedesktop.org
Cc: "Rob Herring" <robh@kernel.org>,
"Tomeu Vizoso" <tomeu.vizoso@collabora.com>,
"David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Nícolas F . R . A . Prado" <nfraprado@collabora.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/9] dt-bindings: Add compatible for Mali Valhall (JM)
Date: Thu, 26 May 2022 09:49:12 +0100 [thread overview]
Message-ID: <226e48d3-5772-bed5-443b-db9acd1365b8@arm.com> (raw)
In-Reply-To: <20220525145754.25866-2-alyssa.rosenzweig@collabora.com>
On 25/05/2022 15:57, Alyssa Rosenzweig wrote:
> From the kernel's perspective, (pre-CSF, "Job Manager") Valhall is more
> or less compatible with Bifrost, although they differ to userspace. Add
> a compatible for Valhall to the existing Bifrost bindings documentation.
>
> As the first SoC with a Valhall GPU receiving mainline support, add a
> specific compatible for the MediaTek MT8192, which instantiates a
> Mali-G57.
>
> v2: Change compatible to arm,mali-valhall-jm (Daniel Stone).
>
> Signed-off-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
> CC: devicetree@vger.kernel.org
Reviewed-by: Steven Price <steven.price@arm.com>
> ---
> .../bindings/gpu/arm,mali-bifrost.yaml | 25 +++++++++++--------
> 1 file changed, 15 insertions(+), 10 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml b/Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml
> index 85f8d4764740..78964c140b46 100644
> --- a/Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml
> +++ b/Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml
> @@ -14,16 +14,21 @@ properties:
> pattern: '^gpu@[a-f0-9]+$'
>
> compatible:
> - items:
> - - enum:
> - - amlogic,meson-g12a-mali
> - - mediatek,mt8183-mali
> - - realtek,rtd1619-mali
> - - renesas,r9a07g044-mali
> - - renesas,r9a07g054-mali
> - - rockchip,px30-mali
> - - rockchip,rk3568-mali
> - - const: arm,mali-bifrost # Mali Bifrost GPU model/revision is fully discoverable
> + oneOf:
> + - items:
> + - enum:
> + - amlogic,meson-g12a-mali
> + - mediatek,mt8183-mali
> + - realtek,rtd1619-mali
> + - renesas,r9a07g044-mali
> + - renesas,r9a07g054-mali
> + - rockchip,px30-mali
> + - rockchip,rk3568-mali
> + - const: arm,mali-bifrost # Mali Bifrost GPU model/revision is fully discoverable
> + - items:
> + - enum:
> + - mediatek,mt8192-mali
> + - const: arm,mali-valhall-jm # Mali Valhall GPU model/revision is fully discoverable
>
> reg:
> maxItems: 1
prev parent reply other threads:[~2022-05-26 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220525145754.25866-1-alyssa.rosenzweig@collabora.com>
2022-05-25 14:57 ` [PATCH v2 1/9] dt-bindings: Add compatible for Mali Valhall (JM) Alyssa Rosenzweig
2022-05-26 1:56 ` Rob Herring
2022-05-26 8:49 ` Steven Price [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=226e48d3-5772-bed5-443b-db9acd1365b8@arm.com \
--to=steven.price@arm.com \
--cc=airlied@linux.ie \
--cc=alyssa.rosenzweig@collabora.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfraprado@collabora.com \
--cc=robh@kernel.org \
--cc=tomeu.vizoso@collabora.com \
/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).