Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Turner <tturner@lineageos.org>
To: Sam Protsenko <semen.protsenko@linaro.org>,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	peter.griffin@linaro.org
Cc: 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 v2 0/2] Exynos850 GPU support
Date: Mon, 24 Aug 2026 11:37:15 +0100	[thread overview]
Message-ID: <91a95ba1-504d-41ef-b44f-59408b0939b8@lineageos.org> (raw)
In-Reply-To: <9c83836b-b4a6-40af-97b1-bbf696258547@kernel.org>

Hi,

 > Can you please tell us a bit about how you tested this patch, and on
 > which board? As DPU is not currently enabled on Exynos850 SoC, I'm not
 > sure how exactly GPU can be useful. If you have a use case or a
 > testing procedure we can run on the E850-96 board, please share.

I tested this patch by running phosh (PostMarketOS) on the Samsung 
Galaxy A21s device, in my tests logs indicated that the GPU hardware was 
probed successfully and things were working. As for DPU, I simply 
enabled CONFIG_DRM_SIMPLEDRM and that was enough since the bootloader 
configured the related DPU bits. Since I don't own the e850-96 dev board 
myself a testing procedure you could do is.

1) Set status="okay"
2) Enable CONFIG_DRM_SIMPLEDRM and CONFIG_DRM_PANFROST
3) Try and boot some form of GUI and compare logs from dmesg with mine.
4) NOTE: we set up fixed regulators during our testing with some support 
from a secondary bootloader, however it should work with dummy regulators.

 > Would be nice to have a more detailed commit message overall. In
 > addition to the above, it probably makes sense to also discuss current
 > limitations. E.g. thermal, PD, and DVFS, which are enabled in the
 > downstream kernel's GPU node [1].

Yes, I have updated the commit message in v2 of the patch series to be 
more descriptive about what does and does not work, I hope that level of 
detail is sufficient but feel free to point out any sections I may have 
missed.

 > How? The node is disabled.

Not sure if the e850-96 device supports this functionality so for the 
mean time I left it as "disabled", but would be interesting to see if 
Sam or Alexey could test it too.

 > Also, you need to version your patches correctly. This is v2. You also
 > need changelog under ---.

Again, sorry for not including this I am still getting my head around 
the process, but in the v3 of the patch series I will make sure to 
include it.

 > You almost never use this parameter.
 > git format patch; scripts/getmaintainers; git send email

Got it thanks, Sam has been helping me with some of the kernel etiquette 
and procedures in a private thread so hopefully the next patch set 
should be lots clearer :).


One other thing I wanted to ask, do you think it would be best to 
include the logs about the GPU probing in the commit message of v3?

In the next patch version I am going to reword the commit msg to be more 
precise, i.e Add nodes for GPU. Can add more information about how I 
tested it and possibly logs from dmesg.

Cheers,
Tom.


      reply	other threads:[~2026-08-24 10:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <GVYP280MB12139AB976CA7ACF49FEB768A1A52@GVYP280MB1213.SWEP280.PROD.OUTLOOK.COM>
2026-08-20 13:35 ` [PATCH] arm64: dts: exynos850: Add GPU/Mali Bifrost node Thomas Turner
2026-08-20 14:13   ` Krzysztof Kozlowski
2026-08-20 14:23 ` [PATCH v2 0/2] Exynos850 GPU support Thomas Turner
2026-08-20 14:23   ` [PATCH v2 1/2] dt-bindings: gpu: arm,mali-bifrost: add exynos850-mali compatible Thomas Turner
2026-08-20 14:23   ` [PATCH v2 2/2] arm64: dts: exynos850: Add GPU/Mali Bifrost node Thomas Turner
2026-08-20 14:28   ` [PATCH v2 0/2] Exynos850 GPU support Krzysztof Kozlowski
     [not found]     ` <GVYP280MB1213F9511E062056470AE74AA1A42@GVYP280MB1213.SWEP280.PROD.OUTLOOK.COM>
2026-08-20 16:22       ` thomas_turner@talktalk.net
2026-08-20 18:15         ` Krzysztof Kozlowski
2026-08-24 10:37           ` Thomas Turner [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=91a95ba1-504d-41ef-b44f-59408b0939b8@lineageos.org \
    --to=tturner@lineageos.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 \
    /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