From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Nicolas Chauvet <kwizart-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: VDE for tegra124 ?
Date: Thu, 16 Jul 2020 15:04:46 +0200 [thread overview]
Message-ID: <20200716130446.GF535268@ulmo> (raw)
In-Reply-To: <CABr+WTm79nGMahuudkZtB6nizP8mxwwi6o4r2LUuN8ykoTrONA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]
On Fri, Jun 26, 2020 at 04:20:08PM +0200, Nicolas Chauvet wrote:
> Hi,
>
> I'm interested in having at least initial VDE support merged upstream
> for tegra124 (not yet tested).
> I was wondering if merging the dts part and the needed compatible
> along with few fixes (2) would be enough to work with the current
> userspace ? (libvdpau-tegra)
>
> I plan to have it tried after 5.18-rc3 land and report.
>
> Thanks for your advice.
>
> (1) https://github.com/thierryreding/linux/commits/for-4.22/vde
> (2) currently testing patches:
> ae8cd25401f9 ARM: tegra: Enable SMMU for VDE on Tegra124
> 53e4822d773a staging: media: tegra-vde: Keep VDE in reset when unused
> eb5b12a86651 staging: media: tegra-vde: Print out invalid FD
> c28810efcb90 staging: media: tegra-vde: Support BSEV clock and reset
> 55266929b386 staging: media: tegra-vde: Properly mark invalid entries
> 3aae01ea407f ARM: tegra: Add BSEV clock and reset for VDE on Tegra30
> f5e6a834c766 ARM: tegra: Add BSEV clock and reset for VDE on Tegra20
> 615bf7bab259 ARM: tegra: Enable VDE on Tegra124
I don't think those patches are enough to make this work on Tegra124. I
think you basically need all of the patches from that branch, at least
up to the point where the V4L2 conversion starts.
Given that the V4L2 conversion has stalled, it might be worth reviving
this relatively short series once more. I can look into rebasing only
the VDE patches and see if they still work.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-07-16 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 14:20 VDE for tegra124 ? Nicolas Chauvet
[not found] ` <CABr+WTm79nGMahuudkZtB6nizP8mxwwi6o4r2LUuN8ykoTrONA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-07-16 13:04 ` Thierry Reding [this message]
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=20200716130446.GF535268@ulmo \
--to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=kwizart-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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).