Re: [PATCH] input/touchscreen/sur40: use COLORSPACE_RAW

2019-06-30 Thread Dmitry Torokhov
On Wed, Jun 26, 2019 at 11:52:16AM +0200, Hans Verkuil wrote: > This driver set the colorspace to SRGB, but that makes no sense for > a touchscreen. Use RAW instead. This also ensures consistency with the > v4l_pix_format_touch() call that's used in v4l2-ioctl.c. > > Signed-off-by: Hans Verkuil >

Re: [PATCH] input/touchscreen/sur40: use COLORSPACE_RAW

2019-06-28 Thread Florian Echtler
On 27.06.19 10:20, Hans Verkuil wrote: > On 6/27/19 10:12 AM, Florian Echtler wrote: >> On 26.06.19 11:52, Hans Verkuil wrote: >>> This driver set the colorspace to SRGB, but that makes no sense for >>> a touchscreen. Use RAW instead. This also ensures consistency with the >>> v4l_pix_format_touch(

Re: [PATCH] input/touchscreen/sur40: use COLORSPACE_RAW

2019-06-27 Thread Hans Verkuil
On 6/27/19 10:12 AM, Florian Echtler wrote: > On 26.06.19 11:52, Hans Verkuil wrote: >> This driver set the colorspace to SRGB, but that makes no sense for >> a touchscreen. Use RAW instead. This also ensures consistency with the >> v4l_pix_format_touch() call that's used in v4l2-ioctl.c. > > One

Re: [PATCH] input/touchscreen/sur40: use COLORSPACE_RAW

2019-06-27 Thread Florian Echtler
On 26.06.19 11:52, Hans Verkuil wrote: > This driver set the colorspace to SRGB, but that makes no sense for > a touchscreen. Use RAW instead. This also ensures consistency with the > v4l_pix_format_touch() call that's used in v4l2-ioctl.c. One question for clarification: this will only affect use

[PATCH] input/touchscreen/sur40: use COLORSPACE_RAW

2019-06-26 Thread Hans Verkuil
This driver set the colorspace to SRGB, but that makes no sense for a touchscreen. Use RAW instead. This also ensures consistency with the v4l_pix_format_touch() call that's used in v4l2-ioctl.c. Signed-off-by: Hans Verkuil --- Dmitry, do you want to take this, or shall I? I have no preference. -