Linux Media Controller development
 help / color / mirror / Atom feed
From: John Cox <jc@kynesim.co.uk>
To: "Ezequiel Garcia" <ezequiel.garcia@collabora.com>
Cc: "Hans Verkuil" <hverkuil@xs4all.nl>,
	"Linux Media Mailing List" <linux-media@vger.kernel.org>
Subject: Re: Dynamic array control support: please test!
Date: Wed, 12 May 2021 16:20:35 +0100	[thread overview]
Message-ID: <e9sn9gp7kk0f6fepfm7trt7oq6bor137iv@4ax.com> (raw)
In-Reply-To: <5212-609bc880-9-623f1400@218746912>

Hi Ezequiel

>Hi John,
> 
>On Thursday, April 29, 2021 14:56 -03, John Cox <jc@kynesim.co.uk> wrote: 
> 
>> Hi
>> 
>> >Hi Ezequiel, John,
>> >
>> >After creating extensive new compliance tests for this feature I am now
>> >confident enough about the implementation.
>> >
>> >You can find it here:
>> >
>> >https://git.linuxtv.org/hverkuil/media_tree.git/log/?h=ctrl-refactor
>> >
>> >There are two items that I want to fix before I will post this:
>> >
>> >1) The new flag needs to be documented
>> >2) I think there are some simplifications possible w.r.t. storing the
>> >   size of the new array, I want to look at that a bit more.
>> >
>> >In the meantime it would be great if some testing of this series can be
>> >done with real drivers instead of just vivid.
>> 
>> Well I finally managed to put together your patch (in 5.10), tweaked
>> driver & ffmpeg to have a variable noof slice headers and it all seems
>> to work well. With the code I have it doesn't give a significant
>> improvement in performance over 1 slice at a time but that is probably
>> because I have multithreaded userland code and take liberties with
>> buffer returns from the driver that Ezequiel disaproves of (but my
>> ffmpeg code is happy with).
>> 
>
>I don't think I have ever disapproved anything (and if I made it sound like that, it was a mistake). Quite the opposite, I am more than supportive to see get more drivers merged upstream.

Yes - sorry - my mistake - I was thinking of one person and typed
another. And in any case, even if I had the right name, that wasn't a
constructive remark on my part.

Please accept my apologies

John Cox

>Thanks!
>Ezequiel

  reply	other threads:[~2021-05-12 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27 12:28 Dynamic array control support: please test! Hans Verkuil
2021-04-29 17:56 ` John Cox
2021-05-12 12:21   ` Ezequiel Garcia
2021-05-12 15:20     ` John Cox [this message]
2021-08-10 12:19 ` John Cox

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=e9sn9gp7kk0f6fepfm7trt7oq6bor137iv@4ax.com \
    --to=jc@kynesim.co.uk \
    --cc=ezequiel.garcia@collabora.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.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