[PATCH] clk: zynqmp: Work around broken DT GPU node
Gajjar, Parth
parth.gajjar at amd.com
Wed Nov 13 05:32:32 PST 2024
Hi Marek,
We tried running kmscube application with lima driver and it is working fine.
Attaching application logs and boot logs.
We are using our 6.6 kernel.
Meanwhile we will also check with upstream kernel.
Which kernel version are you using?
Regards,
Parth
-----Original Message-----
From: Marek Vasut <marex at denx.de>
Sent: Wednesday, November 13, 2024 1:31 AM
To: Gajjar, Parth <parth.gajjar at amd.com>; Sagar, Vishal <vishal.sagar at amd.com>; linux-clk at vger.kernel.org
Cc: Michael Turquette <mturquette at baylibre.com>; Simek, Michal <michal.simek at amd.com>; Stephen Boyd <sboyd at kernel.org>; linux-arm-kernel at lists.infradead.org; Allagadapa, Varunkumar <varunkumar.allagadapa at amd.com>
Subject: Re: [PATCH] clk: zynqmp: Work around broken DT GPU node
On 11/12/24 2:17 PM, Gajjar, Parth wrote:
> Hi Marek,
Hello everyone,
> We tried running glmark2-es2-wayland application with mali and lima driver and didn’t observed any hang. We will also check with kmscube application.
>
> Attaching logs for clock summary.
>
> Did you try with mali or lima driver?
I only use lima driver.
Can you share full boot log of this machine , including the firmware blob versions ? Is it maybe possible some newer blob(s) enable both PP0 and PP1 internally to work around this clocking issue in Linux ?
--
Best regards,
Marek Vasut
-------------- next part --------------
A non-text attachment was scrubbed...
Name: zcu106_bootlog_lima_driver.log
Type: application/octet-stream
Size: 44857 bytes
Desc: zcu106_bootlog_lima_driver.log
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20241113/c4a80315/attachment.obj>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: kmscube_log.txt
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20241113/c4a80315/attachment.txt>
More information about the linux-arm-kernel
mailing list