Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Thomas Turner <tturner@lineageos.org>, semen.protsenko@linaro.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	peter.griffin@linaro.org, alim.akhtar@samsung.com,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: exynos850: Add GPU/Mali Bifrost node
Date: Thu, 20 Aug 2026 16:48:59 +0200	[thread overview]
Message-ID: <afedcd3b-04ea-45c6-a895-a172e3640f84@kernel.org> (raw)
In-Reply-To: <20260820140439.83220-3-tturner@lineageos.org>

On 20/08/2026 16:04, Thomas Turner wrote:
> This can provide basic GPU functionality for the Exynos850 platform.
> Tested on the SM-A217F device. Does not provide support for temperature
> throttling, DVFS, power domains, governor support, boosting and voltage
> control. Once PMIC is properly implemented, support will hopefully
> increase. However the panfrost driver probes, the Mali-G52 GPU
> initializes and the core clock is set-up.
> 
> Signed-off-by: Thomas Turner <tturner@lineageos.org>

Slow down!

It's another version? Duplicate? I already responded to v2 (which was
labeled v1), so is this vX?

What is happening with this patchset?

Best regards,
Krzysztof

      reply	other threads:[~2026-08-20 14:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260820110620.1881-1-tturner@lineageos.org>
2026-08-20 14:04 ` [PATCH 0/2] Exynos850 GPU support Thomas Turner
2026-08-20 14:04   ` [PATCH 1/2] dt-bindings: gpu: arm,mali-bifrost: add exynos850-mali compatible Thomas Turner
2026-08-20 18:13     ` Conor Dooley
2026-08-20 14:04   ` [PATCH 2/2] arm64: dts: exynos850: Add GPU/Mali Bifrost node Thomas Turner
2026-08-20 14:48     ` Krzysztof Kozlowski [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=afedcd3b-04ea-45c6-a895-a172e3640f84@kernel.org \
    --to=krzk@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=peter.griffin@linaro.org \
    --cc=robh@kernel.org \
    --cc=semen.protsenko@linaro.org \
    --cc=tturner@lineageos.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