public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	linux-media@vger.kernel.org,
	sakari.ailus@maxwell.research.nokia.com
Subject: Re: [RFC/PATCH v2 7/7] v4l: subdev: Generic ioctl support
Date: Sat, 10 Jul 2010 14:23:00 -0300	[thread overview]
Message-ID: <4C38AC74.60008@redhat.com> (raw)
In-Reply-To: <201007101831.49445.hverkuil@xs4all.nl>

Em 10-07-2010 13:31, Hans Verkuil escreveu:
> On Saturday 10 July 2010 16:08:46 Mauro Carvalho Chehab wrote:
>> Em 09-07-2010 12:31, Laurent Pinchart escreveu:

>> Hmm... private ioctls at subdev... I'm not sure if I like this idea. I prefer to merge this patch
>> only after having a driver actually needing it, after discussing why not using a standard ioctl
>> for that driver.
> 
> Part of the reason for making these subdev device nodes is to actually allow
> private ioctls (after properly discussing it and with documentation). SoCs tend
> to have a lot of very hardware specific features that do not translate to generic
> ioctls. Until now these are either ignored or handled through custom drivers, but
> but it is much better to handle them in a 'controlled' fashion.

I understand that SoC's may have lots of features that are currently not being exposed,
but if they'll be either be shown as CTRL or as new ioctls need further discussions. That's
why I prefer to receive this patch in a patch series where such needed is required.

Cheers,
Mauro.

  reply	other threads:[~2010-07-10 17:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09 15:31 [RFC/PATCH v2 0/7] V4L2 subdev userspace API Laurent Pinchart
2010-07-09 15:31 ` [RFC/PATCH v2 1/7] v4l: subdev: Don't require core operations Laurent Pinchart
2010-07-09 15:31 ` [RFC/PATCH v2 2/7] v4l: Merge v4l2_i2c_new_subdev_cfg and v4l2_i2c_new_subdev Laurent Pinchart
2010-07-09 15:31 ` [RFC/PATCH v2 3/7] v4l: subdev: Add device node support Laurent Pinchart
2010-07-09 15:31 ` [RFC/PATCH v2 4/7] v4l: subdev: Uninline the v4l2_subdev_init function Laurent Pinchart
2010-07-09 15:31 ` [RFC/PATCH v2 5/7] v4l: subdev: Control ioctls support Laurent Pinchart
2010-07-09 15:31 ` [RFC/PATCH v2 6/7] v4l: subdev: Events support Laurent Pinchart
2010-07-10 13:59   ` Mauro Carvalho Chehab
2010-07-12 11:06     ` Sakari Ailus
2010-07-12 11:37       ` Laurent Pinchart
2010-07-09 15:31 ` [RFC/PATCH v2 7/7] v4l: subdev: Generic ioctl support Laurent Pinchart
2010-07-10 14:08   ` Mauro Carvalho Chehab
2010-07-10 16:31     ` Hans Verkuil
2010-07-10 17:23       ` Mauro Carvalho Chehab [this message]
2010-07-12  9:33   ` Pawel Osciak
2010-07-12 11:39     ` Laurent Pinchart
2010-07-10 16:38 ` [RFC/PATCH v2 0/7] V4L2 subdev userspace API Hans Verkuil

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=4C38AC74.60008@redhat.com \
    --to=mchehab@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@maxwell.research.nokia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox