From: Cai Huoqing <cai.huoqing@linux.dev>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: "Mikko Perttunen" <cyndis@kapsi.fi>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@linux.ie>,
linux-kernel@vger.kernel.org,
"Christian König" <christian.koenig@amd.com>,
linaro-mm-sig@lists.linaro.org, dri-devel@lists.freedesktop.org,
"Sumit Semwal" <sumit.semwal@linaro.org>,
linux-media@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2 0/4] drm/nvdla: Add driver support for NVDLA
Date: Fri, 29 Apr 2022 11:37:33 +0800 [thread overview]
Message-ID: <20220429033733.GA15753@chq-T47> (raw)
In-Reply-To: <aa55c03c-6d22-9718-a2a5-28d9ce114954@nvidia.com>
On 28 4月 22 17:35:56, Jon Hunter wrote:
>
> 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@vger.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
>
Sure, based on https://github.com/nvdla/sw
The copyright retain in this driver,
like "Copyright (C) 2017-2018 NVIDIA CORPORATION"
Thanks
Cai
> Jon
>
> --
> nvpublic
next prev parent reply other threads:[~2022-04-29 3:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 6:07 [PATCH v2 0/4] drm/nvdla: Add driver support for NVDLA Cai Huoqing
2022-04-26 6:07 ` [PATCH v2 1/4] MAINTAINERS: Add the driver info of the NVDLA Cai Huoqing
2022-04-26 6:07 ` [PATCH v2 2/4] drm/nvdla: Add driver support for NVDLA Cai Huoqing
2022-04-28 15:18 ` Thierry Reding
2022-04-28 15:19 ` Thierry Reding
2022-04-26 6:08 ` [PATCH v2 3/4] drm/nvdla: Add register head file of NVDLA Cai Huoqing
2022-04-28 14:31 ` Thierry Reding
2022-04-26 6:08 ` [PATCH v2 4/4] drm/nvdla/uapi: Add UAPI of NVDLA driver Cai Huoqing
2022-04-26 6:31 ` Christian König
2022-04-26 8:23 ` Cai Huoqing
2022-04-26 8:29 ` Christian König
2022-04-28 14:45 ` Thierry Reding
2022-04-29 3:58 ` Cai Huoqing
2022-04-26 10:50 ` [Linaro-mm-sig] " Arnd Bergmann
2022-04-26 12:24 ` Cai Huoqing
2022-04-26 12:38 ` Arnd Bergmann
2022-04-26 10:12 ` kernel test robot
2022-04-26 11:23 ` kernel test robot
2022-04-28 14:40 ` Thierry Reding
2022-04-28 14:10 ` [PATCH v2 0/4] drm/nvdla: Add driver support for NVDLA Thierry Reding
2022-04-28 15:56 ` Mikko Perttunen
2022-04-28 16:35 ` Jon Hunter
2022-04-29 3:37 ` Cai Huoqing [this message]
2022-04-29 3:28 ` Cai Huoqing
2022-05-02 17:04 ` Thierry Reding
2022-05-07 9:05 ` Cai Huoqing
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=20220429033733.GA15753@chq-T47 \
--to=cai.huoqing@linux.dev \
--cc=airlied@linux.ie \
--cc=christian.koenig@amd.com \
--cc=cyndis@kapsi.fi \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=thierry.reding@gmail.com \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).