[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aa55c03c-6d22-9718-a2a5-28d9ce114954@nvidia.com>
Date: Thu, 28 Apr 2022 17:35:56 +0100
From: Jon Hunter <jonathanh@...dia.com>
To: Mikko Perttunen <cyndis@...si.fi>,
Thierry Reding <thierry.reding@...il.com>,
Cai Huoqing <cai.huoqing@...ux.dev>
Cc: Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...ux.ie>, linux-kernel@...r.kernel.org,
Christian König <christian.koenig@....com>,
linaro-mm-sig@...ts.linaro.org, dri-devel@...ts.freedesktop.org,
Sumit Semwal <sumit.semwal@...aro.org>,
linux-media@...r.kernel.org, linux-tegra@...r.kernel.org
Subject: Re: [PATCH v2 0/4] drm/nvdla: Add driver support for NVDLA
On 28/04/2022 16:56, Mikko Perttunen wrote:
> On 4/28/22 17:10, Thierry Reding wrote:
>> On Tue, Apr 26, 2022 at 02:07:57PM +0800, Cai Huoqing wrote:
>>> The NVIDIA Deep Learning Accelerator (NVDLA) is an open source IP
>>> which is integrated into NVIDIA Jetson AGX Xavier,
>>> so add driver support for this accelerator."
>>
>> Hi,
>>
>> nice to see this work going on. For subsequent revisions, can you please
>> also Cc the Tegra mailing list (linux-tegra@...r.kernel.org) as well as
>> the Tegra platform maintainers (that's Jon Hunter and myself). This will
>> make sure that more people with an interest in this will see your work.
>> Not everyone follows dri-devel, linaro-mm-sig or linux-media.
>>
>> Thanks,
>> Thierry
>
> From a quick glance it looks like this driver pokes DLA hardware
> directly which is not the intended programming model on Tegra hardware
> (there are Falcon microcontrollers that offload task scheduling and
> synchronization from the CPU). The hardware is also behind the Host1x
> bus so a simple platform device is not sufficient.
>
> Was this driver developed against some platform with OpenDLA hardware
> (i.e. not Tegra)?
>
> If so, we'd need to verify if the hardware matches the hardware in
> Tegra194. Also, this driver may not be ideal for Tegra platforms since
> we would lack the hardware scheduling and synchronization facilities. It
> is likely necessary to have separate drivers for OpenDLA and Tegra's DLA
> integration.
I believe that this is derived from the following github project ...
https://github.com/nvdla/sw
Jon
--
nvpublic
Powered by blists - more mailing lists