[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <de748b0f-6e05-4c36-a6ad-cc5b09718e0b@web.de>
Date: Tue, 6 Aug 2024 20:56:53 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Lizhi Hou <lizhi.hou@....com>, dri-devel@...ts.freedesktop.org,
Oded Gabbay <ogabbay@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>, George Yang <George.Yang@....com>,
king.tam@....com, Max Zhen <max.zhen@....com>, Min Ma <min.ma@....com>,
Narendra Gutta <VenkataNarendraKumar.Gutta@....com>,
Sonal Santan <sonal.santan@....com>
Subject: Re: [PATCH V2 00/10] AMD XDNA driver
>> https://lkml.org/lkml/2024/7/19/803
>> https://lore.kernel.org/linux-kernel/010a46ba-9dc4-e3e3-7894-b28b312c6ab1@amd.com/
>> [01/10] accel/amdxdna: Add a new driver for AMD AI Engine
>> “guard looks cleaner. We will use it.”
> We reconsidered this request
Interesting …
> and searched accel and drm subsystem. I did not see it was used.
Do you notice how applications of scope-based resource management are growing
in other subsystem areas?
> This does not look like a required change for upstream at this moment.
Maybe.
> We would keep the current code for this patch series.
Will further collateral evolution become more attractive anyhow?
Regards,
Markus
Powered by blists - more mailing lists