All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/3] NVIDIA Tegra NVDEC support
Date: Mon, 15 Feb 2021 10:50:59 +0100	[thread overview]
Message-ID: <YCpEA8K6vgxfz8uC@ulmo.localdomain> (raw)
In-Reply-To: <8a50f133-12ed-e81c-47a5-07c51924ec6a@baylibre.com>


[-- Attachment #1.1: Type: text/plain, Size: 1270 bytes --]

On Mon, Feb 15, 2021 at 10:10:26AM +0100, Neil Armstrong wrote:
> Hi,
> 
> On 13/02/2021 11:15, Mikko Perttunen wrote:
> > Hi all,
> > 
> > with the release of documentation headers for Tegra multimedia engines
> > (NVDEC, NVENC, NVJPG) [1], I have started working on the corresponding
> > implementations. Here's the first one, NVDEC.
> > 
> > The kernel driver is a simple Falcon boot driver based on the VIC
> > driver. Some code sharing should be considered there in the future.
> > The userspace driver to accompany this is a bit more complicated -
> > I have expanded vaapi-tegra-driver[2] to support MPEG2 decoding.
> > It should be noted that the implementation is still very clunky
> > and has poor performance, but it's a start.
> 
> Funny how all this tries to avoid all the DRM, remoteproc, V4L2-M2M stateless & co
> all the other vendors tries to make usage of...

Care to elaborate why you think this is trying to avoid anything? Mikko
pointed you at the documentation for these engines, provided a link to
an open-source (albeit work in progress) userspace driver and posts an
extension to an existing DRM driver to add the required kernel
functionality. That's a standard approach for submitting this kind of
driver.

Thierry

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2021-02-15  9:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-13 10:15 [PATCH 0/3] NVIDIA Tegra NVDEC support Mikko Perttunen
2021-02-13 10:15 ` Mikko Perttunen
2021-02-13 10:15 ` [PATCH 1/3] dt-bindings: Add YAML bindings for Host1x and NVDEC Mikko Perttunen
2021-02-13 10:15   ` Mikko Perttunen
2021-02-15  9:09   ` Neil Armstrong
2021-02-17 20:24   ` Rob Herring
2021-02-17 20:24     ` Rob Herring
2021-02-17 21:49   ` Rob Herring
2021-02-17 21:49     ` Rob Herring
2021-02-18 11:04     ` Mikko Perttunen
2021-02-18 11:04       ` Mikko Perttunen
2021-02-18 16:45       ` Rob Herring
2021-02-18 16:45         ` Rob Herring
2021-02-13 10:15 ` [PATCH 2/3] arm64: tegra: Add NVDEC to Tegra186 device tree Mikko Perttunen
2021-02-13 10:15   ` Mikko Perttunen
2021-02-13 10:15 ` [PATCH 3/3] drm/tegra: Add NVDEC driver Mikko Perttunen
2021-02-13 10:15   ` Mikko Perttunen
2021-02-13 12:40   ` kernel test robot
2021-02-13 12:40     ` kernel test robot
2021-02-13 12:40     ` kernel test robot
2021-02-16 15:16   ` Jon Hunter
2021-02-16 15:16     ` Jon Hunter
2021-02-15  9:10 ` [PATCH 0/3] NVIDIA Tegra NVDEC support Neil Armstrong
2021-02-15  9:50   ` Thierry Reding [this message]
2021-02-15 10:21     ` Neil Armstrong
2021-02-15 10:54       ` Thierry Reding

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=YCpEA8K6vgxfz8uC@ulmo.localdomain \
    --to=thierry.reding@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=narmstrong@baylibre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.