All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Patrick Doyle <wpdster@gmail.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: v4l2_subdev_queryctrl and friends
Date: Tue, 16 May 2017 18:13:09 +0200	[thread overview]
Message-ID: <2075aeff-6ef9-8fa8-696e-f932d68a03ea@xs4all.nl> (raw)
In-Reply-To: <CAF_dkJBOf16Xz=wx6KT4FLqU_X+Ok+0ZbsV=JfRGs_tN+YKHeQ@mail.gmail.com>

On 16/05/17 16:31, Patrick Doyle wrote:
> There is a statement in the v4l2-controls.txt in my 4.4.55 kernel that
> v4l2_subdev_queryctrl and friends will be removed "Once all the V4L2
> drivers that depend on subdev drivers are converted to the control
> framework".
> 
> How would I be able to tell if my driver (isc-atmel.c) has been
> converted to the control framework?  I would have expected that to be
> the case, given that I have backported the driver (from linux-media in
> the last week or two), but I am not seeing controls that I create in
> my subdev.

Yes, atmel-isc.c has been converted. If a driver has a v4l2_ctrl_handler
struct, then it's OK.

However, it seems it never inherits the controls from the subdev.

It needs something like this (taken from rcar-vin.c):

        ret = v4l2_ctrl_add_handler(&vin->ctrl_handler, sd->ctrl_handler, NULL);
        if (ret < 0)
                return ret;

to do this.

Regards,

	Hans

> As long as I am backporting the driver, I may as well do it right.
> Unless there is some reason why the control framework is known to be
> broken in 4.4.
> 
> Any thoughts?
> 
> --wpd
> 

  reply	other threads:[~2017-05-16 16:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-16 14:31 v4l2_subdev_queryctrl and friends Patrick Doyle
2017-05-16 16:13 ` Hans Verkuil [this message]
2017-05-16 17:01   ` Patrick Doyle

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=2075aeff-6ef9-8fa8-696e-f932d68a03ea@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=wpdster@gmail.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 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.