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: Tue, 26 Nov 2024 17:18:43 +0100 [thread overview]
Message-ID: <8b6085b9-9b21-4043-af5e-e7fc4962236f@denx.de> (raw)
In-Reply-To: <SJ0PR12MB6965E6448CFB1095584B114C992F2@SJ0PR12MB6965.namprd12.prod.outlook.com>
On 11/26/24 6:25 AM, Gajjar, Parth wrote:
> Hi Marek,
Hi,
> Yes we are using https://github.com/Xilinx/linux-xlnx/tree/xlnx_rebase_v6.6_LTS. We are also checking with upstream kernel. Will update you on that.
Please do test mainline Linux (currently 6.12 or next), not some
downstream fork. Downstream forks tests have no relevance in mainline
Linux testing.
> Can you share please your artifacts.
>
> The blobs I use are 2019.1
> [Parth]: You are using 2019.1 BOOT.bin and rootfs and upstream kernel Image right?
FSBL and PMUFW are built from embedded-sw 2019.1 , rootfs is currently
debian unstable or OE scarthgap based .
> Also I don't think any changes with respect to this. Let me also double check once.
I'll wait for this.
next prev parent reply other threads:[~2024-11-26 16:22 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
2024-11-26 5:25 ` Gajjar, Parth
2024-11-26 16:18 ` Marek Vasut [this message]
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=8b6085b9-9b21-4043-af5e-e7fc4962236f@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