public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Helen Koike <helen.koike@collabora.com>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
	Hans Verkuil <hverkuil@xs4all.nl>
Cc: Sakari Ailus <sakari.ailus@iki.fi>,
	linux-media@vger.kernel.org, jgebben@codeaurora.org,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH RFC 1/2] [media] v4l2: add V4L2_INPUT_TYPE_DEFAULT
Date: Mon, 3 Apr 2017 12:11:54 -0300	[thread overview]
Message-ID: <7922bf67-33cc-a377-02c3-45603f1c0ebc@collabora.com> (raw)
In-Reply-To: <20170331065714.228634d1@vento.lan>

Hi,

On 2017-03-31 06:57 AM, Mauro Carvalho Chehab wrote:
> Em Fri, 31 Mar 2017 10:29:04 +0200
> Hans Verkuil <hverkuil@xs4all.nl> escreveu:
>
>> On 30/03/17 18:02, Helen Koike wrote:
>>> Add V4L2_INPUT_TYPE_DEFAULT and helpers functions for input ioctls to be
>>> used when no inputs are available in the device
>>>
>>> Signed-off-by: Helen Koike <helen.koike@collabora.com>
>>> ---
>>>  drivers/media/v4l2-core/v4l2-ioctl.c | 27 +++++++++++++++++++++++++++
>>>  include/media/v4l2-ioctl.h           | 26 ++++++++++++++++++++++++++
>>>  include/uapi/linux/videodev2.h       |  1 +
>>>  3 files changed, 54 insertions(+)
>>>
>>> diff --git a/drivers/media/v4l2-core/v4l2-ioctl.c b/drivers/media/v4l2-core/v4l2-ioctl.c
>>> index 0c3f238..ccaf04b 100644
>>> --- a/drivers/media/v4l2-core/v4l2-ioctl.c
>>> +++ b/drivers/media/v4l2-core/v4l2-ioctl.c
>>> @@ -2573,6 +2573,33 @@ struct mutex *v4l2_ioctl_get_lock(struct video_device *vdev, unsigned cmd)
>>>  	return vdev->lock;
>>>  }
>>>
>>> +int v4l2_ioctl_enum_input_default(struct file *file, void *priv,
>>> +				  struct v4l2_input *i)
>>> +{
>>> +	if (i->index > 0)
>>> +		return -EINVAL;
>>> +
>>> +	memset(i, 0, sizeof(*i));
>>> +	i->type = V4L2_INPUT_TYPE_DEFAULT;
>>> +	strlcpy(i->name, "Default", sizeof(i->name));
>>> +
>>> +	return 0;
>>> +}
>>> +EXPORT_SYMBOL(v4l2_ioctl_enum_input_default);
>>> +
>>> +int v4l2_ioctl_g_input_default(struct file *file, void *priv, unsigned int *i)
>>> +{
>>> +	*i = 0;
>>> +	return 0;
>>> +}
>>> +EXPORT_SYMBOL(v4l2_ioctl_g_input_default);
>>> +
>>> +int v4l2_ioctl_s_input_default(struct file *file, void *priv, unsigned int i)
>>> +{
>>> +	return i ? -EINVAL : 0;
>>> +}
>>> +EXPORT_SYMBOL(v4l2_ioctl_s_input_default);
>>> +
>>>  /* Common ioctl debug function. This function can be used by
>>>     external ioctl messages as well as internal V4L ioctl */
>>>  void v4l_printk_ioctl(const char *prefix, unsigned int cmd)
>>> diff --git a/include/media/v4l2-ioctl.h b/include/media/v4l2-ioctl.h
>>> index 6cd94e5..accc470 100644
>>> --- a/include/media/v4l2-ioctl.h
>>> +++ b/include/media/v4l2-ioctl.h
>>> @@ -652,6 +652,32 @@ struct video_device;
>>>   */
>>>  struct mutex *v4l2_ioctl_get_lock(struct video_device *vdev, unsigned int cmd);
>>>
>>> +
>>> +/**
>>> + * v4l2_ioctl_enum_input_default - v4l2 ioctl helper for VIDIOC_ENUM_INPUT ioctl
>>> + *
>>> + * Plug this function in vidioc_enum_input field of the struct v4l2_ioctl_ops to
>>> + * enumerate a single input as V4L2_INPUT_TYPE_DEFAULT
>>> + */
>>> +int v4l2_ioctl_enum_input_default(struct file *file, void *priv,
>>> +				  struct v4l2_input *i);
>>> +
>>> +/**
>>> + * v4l2_ioctl_g_input_default - v4l2 ioctl helper for VIDIOC_G_INPUT ioctl
>>> + *
>>> + * Plug this function in vidioc_g_input field of the struct v4l2_ioctl_ops
>>> + * when using v4l2_ioctl_enum_input_default
>>> + */
>>> +int v4l2_ioctl_g_input_default(struct file *file, void *priv, unsigned int *i);
>>> +
>>> +/**
>>> + * v4l2_ioctl_s_input_default - v4l2 ioctl helper for VIDIOC_S_INPUT ioctl
>>> + *
>>> + * Plug this function in vidioc_s_input field of the struct v4l2_ioctl_ops
>>> + * when using v4l2_ioctl_enum_input_default
>>> + */
>>> +int v4l2_ioctl_s_input_default(struct file *file, void *priv, unsigned int i);
>>> +
>>>  /* names for fancy debug output */
>>>  extern const char *v4l2_field_names[];
>>>  extern const char *v4l2_type_names[];
>>> diff --git a/include/uapi/linux/videodev2.h b/include/uapi/linux/videodev2.h
>>> index 316be62..c10bbde 100644
>>> --- a/include/uapi/linux/videodev2.h
>>> +++ b/include/uapi/linux/videodev2.h
>>> @@ -1477,6 +1477,7 @@ struct v4l2_input {
>>>  };
>>>
>>>  /*  Values for the 'type' field */
>>> +#define V4L2_INPUT_TYPE_DEFAULT		0
>>
>> I don't think we should add a new type here.
>
> I second that. Just replied the same thing on a comment from Sakari to
> patch 2/2.
>
>> The whole point of this exercise is to
>> allow existing apps to work, and existing apps expect a TYPE_CAMERA.
>>
>> BTW, don't read to much in the term 'CAMERA': it's really a catch all for any video
>> stream, whether it is from a sensor, composite input, HDMI, etc.
>>
>> The description for V4L2_INPUT_TYPE_CAMERA in the spec is hopelessly out of date :-(
>
> Yeah, we always used "CAMERA" to mean NOT_TUNER.
>
>> Rather than creating a new type I would add a new V4L2_IN_CAP_MC capability that
>> indicates that this input is controlled via the media controller. That makes much
>> more sense and it wouldn't potentially break applications.
>>
>> Exactly the same can be done for outputs as well: add V4L2_OUT_CAP_MC and use
>> V4L2_OUTPUT_TYPE_ANALOG as the output type (again, a horrible outdated name and the
>> spec is again out of date).
>
> I don't see any sense on distinguishing IN and OUT for MC. I mean: should
> we ever allow that any driver to have their inputs controlled via V4L2 API,
> and their outputs controlled via MC (or vice-versa)? I don't think so.
>
> Either all device inputs/outputs are controlled via V4L2 or via MC. So,
> let's call it just V4L2_CAP_MC.
>
>> Regarding the name: should we use the name stored in struct video_device instead?
>> That might be more descriptive.
>
> Makes sense to me.
>
>> Alternatively use something like "Media Controller Input".
>
> Yeah, we could do that, if V4L2_CAP_MC. if not, we can use the name
> stored at video_device.

Just to clarify: the V4L2_CAP_MC would indicated that the media 
controller is enabled in general? Or just for inputs and outputs?
If it is the first case, not necessarily the inputs/outputs are 
controlled via MC (we can still have a MC capable driver, but 
inputs/outputs controlled via V4L2 no? When the driver doesn't offer the 
necessary link controls via MC), then checking if V4L2_CAP_MC then use 
the name "Media Controller Input" is not enough.
If it is the second case, then wouldn't it be better to name it 
V4L2_CAP_MC_IO ?

Thanks

Helen

>
>> More helpful (perhaps) than just "Default" or "Unknown".
>>
>> I'll make a patch to update the input/output type description in the spec.
>
> Thanks!
>
>>
>> Regards,
>>
>> 	Hans
>>
>>>  #define V4L2_INPUT_TYPE_TUNER		1
>>>  #define V4L2_INPUT_TYPE_CAMERA		2
>>>  #define V4L2_INPUT_TYPE_TOUCH		3
>>>
>>
>
>
>
> Thanks,
> Mauro
>

  reply	other threads:[~2017-04-03 15:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 16:02 [PATCH RFC 1/2] [media] v4l2: add V4L2_INPUT_TYPE_DEFAULT Helen Koike
2017-03-30 16:02 ` [PATCH 2/2] [media] docs-rst: " Helen Koike
2017-03-30 20:26   ` Sakari Ailus
2017-03-31  9:47     ` Mauro Carvalho Chehab
2017-03-30 19:56 ` [PATCH RFC 1/2] [media] v4l2: " Laurent Pinchart
2017-03-31  2:39   ` Helen Koike
2017-03-31  3:55     ` Helen Koike
2017-03-31  9:42       ` Mauro Carvalho Chehab
2017-03-31  9:51         ` Hans Verkuil
2017-03-31  8:41     ` Laurent Pinchart
2017-03-31  9:33       ` Mauro Carvalho Chehab
2017-03-31  8:29 ` Hans Verkuil
2017-03-31  8:41   ` Laurent Pinchart
2017-03-31  9:08     ` Hans Verkuil
2017-03-31  9:57   ` Mauro Carvalho Chehab
2017-04-03 15:11     ` Helen Koike [this message]
2017-04-04 13:22       ` Sakari Ailus
2017-04-07  9:46         ` Hans Verkuil
2017-04-07  9:53           ` Laurent Pinchart
2017-06-06 16:22             ` Helen Koike
2017-06-12  9:26               ` Hans Verkuil
2017-06-30 11:03                 ` Sakari Ailus
2017-06-30 11:13                   ` Hans Verkuil
2017-06-30 13:49                     ` Sakari Ailus
2017-04-07  9:36     ` Hans Verkuil
2017-06-14  4:50 ` [PATCH v2] [media] v4l2: add V4L2_CAP_IO_MC Helen Koike
2017-06-19 11:15   ` Hans Verkuil
2017-06-19 17:49     ` Helen Koike

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=7922bf67-33cc-a377-02c3-45603f1c0ebc@collabora.com \
    --to=helen.koike@collabora.com \
    --cc=hverkuil@xs4all.nl \
    --cc=jgebben@codeaurora.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@s-opensource.com \
    --cc=sakari.ailus@iki.fi \
    /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