public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: "Erik Andrén" <erik.andren@gmail.com>
Cc: m560x driver devel <m560x-driver-devel@lists.sourceforge.net>,
	video4linux-list@redhat.com
Subject: Re: [GSPCA] A couple of questions
Date: Mon, 22 Sep 2008 20:17:05 +0200	[thread overview]
Message-ID: <48D7E121.50002@hhs.nl> (raw)
In-Reply-To: <48D7DAE1.7040204@gmail.com>

Erik Andrén wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi,
> I've begun the working investigating the possibility of converting the
> m5602 driver to the gspca framework.

Great! You rock, really you do :)

> I currently have the following questions:
> 1) From my understanding each driver implementing the gspca framework
> has a static list of v4l2 controls. In the m5602 driver, each sensor has
> its own set of v4l2 controls with different resolutions.
> Is there a obious solution to this problem?
> 

Yes and no, for now the solution is to make your sd_desc non const and update 
the ctrls member to point to the right array. In the future I want to add a 
const struct sd_desc *sensor_ctrls to the main gspca struct, which you can then 
set at probe time, as there are more subdrivers with this issue.

Feel free todo that now in your patch if that suits you. My idea is to have per 
bridge controls in sd_desc, and per sensor controls in gspca_dev.

> 2) In the sd_desc struct, is it necessary to implement the dq_callback
> or does the gspca driver automagically requeue buffers?

There is no need to implement this, its just a callback for when you want todo 
something each frame from a non interrupt contexts (like software autoexposure).

Don't hesitate to ask more questions!

Regards,

Hans

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

      reply	other threads:[~2008-09-22 18:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22 17:50 [GSPCA] A couple of questions Erik Andrén
2008-09-22 18:17 ` Hans de Goede [this message]

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=48D7E121.50002@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --cc=erik.andren@gmail.com \
    --cc=m560x-driver-devel@lists.sourceforge.net \
    --cc=video4linux-list@redhat.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