From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Nicolas Dufresne <nicolas.dufresne@collabora.com>
Cc: Justin Green <greenjustin@chromium.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
linux-media@vger.kernel.org,
"tiffany.lin@mediatek.com" <tiffany.lin@mediatek.com>,
"andrew-ct.chen@mediatek.com" <andrew-ct.chen@mediatek.com>,
mchehab@kernel.org,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>
Subject: Re: [PATCH] mediatek/vcodec: Enable incoherent buffer allocation
Date: Tue, 7 Jun 2022 18:57:55 +0900 [thread overview]
Message-ID: <Yp8hI3654zQ+3WcE@google.com> (raw)
In-Reply-To: <92a0163fa2bb20a5c577ca0222e497f0e2bee926.camel@collabora.com>
On (22/06/01 11:13), Nicolas Dufresne wrote:
> I'd be very interested to learn from Sergey on why this feature wasn't enable
> more broadly.
Well, we needed this for one particular device and we didn't plan on
expanding this to drivers that we cannot test, verify, etc. and for
the hardware that we don't run.
> I notice though the begin/end access bits have not been
> implemented, so when used with DMABuf, this isn't going to behave quite right by
> default.
We cared only for MMAP buffers. Got time to cook patches?
next prev parent reply other threads:[~2022-06-07 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 21:10 [PATCH] mediatek/vcodec: Enable incoherent buffer allocation Justin Green
2022-06-01 1:38 ` Sergey Senozhatsky
2022-06-01 14:00 ` Justin Green
2022-06-01 15:13 ` Nicolas Dufresne
2022-06-07 9:57 ` Sergey Senozhatsky [this message]
2022-06-08 14:12 ` Nicolas Dufresne
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=Yp8hI3654zQ+3WcE@google.com \
--to=senozhatsky@chromium.org \
--cc=andrew-ct.chen@mediatek.com \
--cc=greenjustin@chromium.org \
--cc=linux-media@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=tiffany.lin@mediatek.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.