From: Marek Vasut <marex@denx.de>
To: "Gajjar, Parth" <parth.gajjar@amd.com>,
"Sagar, Vishal" <vishal.sagar@amd.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
"Simek, Michal" <michal.simek@amd.com>,
Stephen Boyd <sboyd@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Allagadapa, Varunkumar" <varunkumar.allagadapa@amd.com>
Subject: Re: [PATCH] clk: zynqmp: Work around broken DT GPU node
Date: Wed, 13 Nov 2024 20:55:47 +0100 [thread overview]
Message-ID: <14d05680-3112-4ad6-9d4c-e892359fc9d4@denx.de> (raw)
In-Reply-To: <PH7PR12MB69557B0065EE5D4E51EE13FF995A2@PH7PR12MB6955.namprd12.prod.outlook.com>
On 11/13/24 2:32 PM, Gajjar, Parth wrote:
> Hi Marek,
Hi,
> 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.
Is this the heavily patched kernel version from
https://github.com/Xilinx/linux-xlnx branch xlnx/xlnx_rebase_v6.6_LTS
with
865 files changed, 216895 insertions(+), 8276 deletions(-)
or an actual stock 6.6.40 ?
> Is it maybe possible some newer blob(s) enable both PP0 and PP1 internally to work around this clocking issue in Linux ?
The blobs I use are 2019.1 , so what about this question ^ ?
next prev parent reply other threads:[~2024-11-13 20:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 16:59 [PATCH] clk: zynqmp: Work around broken DT GPU node Marek Vasut
2024-11-11 14:33 ` Sagar, Vishal
2024-11-11 16:25 ` Marek Vasut
2024-11-12 13:17 ` Gajjar, Parth
2024-11-12 20:00 ` Marek Vasut
2024-11-13 13:32 ` Gajjar, Parth
2024-11-13 19:55 ` Marek Vasut [this message]
2024-11-26 5:25 ` Gajjar, Parth
2024-11-26 16:18 ` Marek Vasut
2024-11-28 14:35 ` Gajjar, Parth
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=14d05680-3112-4ad6-9d4c-e892359fc9d4@denx.de \
--to=marex@denx.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=mturquette@baylibre.com \
--cc=parth.gajjar@amd.com \
--cc=sboyd@kernel.org \
--cc=varunkumar.allagadapa@amd.com \
--cc=vishal.sagar@amd.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