All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dean Anderson <dean@sensoray.com>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: Greg KH <greg@kroah.com>,
	Markus Rechberger <mrechberger@gmail.com>,
	video4linux-list@redhat.com, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org, mchehab@infradead.org,
	v4l-dvb-maintainer@linuxtv.org
Subject: Re: [v4l-dvb-maintainer] [PATCH] USB: add Sensoray 2255 v4l driver
Date: Thu, 15 May 2008 08:34:42 -0700	[thread overview]
Message-ID: <482C5812.9090903@sensoray.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0805142006130.23876@shell4.speakeasy.net>

Trent Piepho wrote:
> On Wed, 14 May 2008, Greg KH wrote:
>   
>> On Thu, May 15, 2008 at 03:17:42AM +0200, Markus Rechberger wrote:
>>     
>>> Hi Dean, Greg,
>>>       
>> Adding dean to the cc: line...  :)
>>     
>>> On 5/14/08, Greg KH <greg@kroah.com> wrote:
>>>       
>>>> From: Dean Anderson <dean@sensoray.com>
>>>>
>>>>         
>> <big patch snipped>
>>
>>     
>>> Why do you do those conversions in kernelspace?
>>> ffmpeg/libswscale has optimized code for colourspace conversions.
>>> I know a few drivers do that in kernelspace but it's way more flexible
>>> in userspace and depending on the optimization requires less CPU
>>> power.
>>>       
>> I thought they were there as needed by some V4L1 applications, but that
>> code was recently removed by Dean I think.  If they don't need to be
>> there, and userspace apps can properly handle the different colorspace,
>> then I'll be glad to remove them.
>>     
>
> Virtually all apps (V4L1 & 2) can handle YUV and RGB colorspaces.
> Certainly all the major ones do and all the major libraries as well.
>
> The problem is when the device only supports some vendor specific or
> otherwise very uncommon format.  In that case not doing the conversion in
> the kernel means the device won't work with any existing software without
> patches.  In this case, while it's not "the right way", drivers often end
> up including an in kernel conversion for pragmatic reasons.
>
> This was a problem with the bayer format, but now userspace support for
> that format is more common.
>   

I agree the conversions don't belong in a driver. For the record, the 
following are done in the 2255 hardware: V4L2_PIX_FMT_GREY and 
V4L2_PIX_FMT_YUV422P.

Since planar YUV formats such as V4L2_PIX_FMT_YUV422P are still not that 
well supported, is it possible to keep at least one packed YUV 
format(V4L2_PIX_FMT_YUYV) in the driver?  If not, let me know.  I will 
strongly suggest that the hardware Engineers add YUY2 or YUYV on board 
in the DSP firmware.  Thanks, Dean











  reply	other threads:[~2008-05-15 15:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 20:59 [PATCH] USB: add Sensoray 2255 v4l driver Greg KH
2008-05-15  1:17 ` [v4l-dvb-maintainer] " Markus Rechberger
2008-05-15  1:17   ` Markus Rechberger
2008-05-15  2:41   ` Greg KH
2008-05-15  3:12     ` Trent Piepho
2008-05-15  3:12       ` Trent Piepho
2008-05-15 15:34       ` Dean Anderson [this message]
2008-05-15 16:57         ` Markus Rechberger
2008-05-15 16:57           ` Markus Rechberger
2008-05-16  2:59         ` Mauro Carvalho Chehab
2008-05-15 11:38 ` Oliver Neukum
2008-05-15 12:03   ` Oliver Neukum
2008-05-15 18:44     ` Greg KH
2008-05-15 19:54       ` Oliver Neukum
2008-05-15 20:10         ` Greg KH
2008-05-15 20:13           ` Oliver Neukum
2008-05-16  2:51 ` Mauro Carvalho Chehab
2008-05-16  2:51   ` Mauro Carvalho Chehab
2008-05-16  6:28   ` Oliver Neukum
2008-05-16 15:57     ` dean
2008-05-16 16:04       ` Oliver Neukum
2008-05-16 18:17       ` Mauro Carvalho Chehab
2008-05-16 18:17         ` Mauro Carvalho Chehab
2008-05-16 14:53   ` dean
2008-05-16 15:34     ` Mauro Carvalho Chehab
2008-05-16 15:34       ` Mauro Carvalho Chehab

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=482C5812.9090903@sensoray.com \
    --to=dean@sensoray.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=mrechberger@gmail.com \
    --cc=v4l-dvb-maintainer@linuxtv.org \
    --cc=video4linux-list@redhat.com \
    --cc=xyzzy@speakeasy.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 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.