linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	linux-media <linux-media@vger.kernel.org>
Subject: subdev: fps enum_frame_interval
Date: Tue, 30 Jun 2015 09:34:08 +0200	[thread overview]
Message-ID: <CAPybu_2dTaf_RF2NR1mSqzW5=Hw0m+Ngm=UxE5T-VNKfCeHcrg@mail.gmail.com> (raw)

Hello

I have a subdevice that can produce images at a programmable interval,
i.e. at different fps.

I was using the callback enum_frameintervals to "negotiate" the frame
rate, but since 4.1 it is gone in favor of enum_frame_interval.


enum_frame_interval, seems to only return one value for fps. How can I
make the bridge driver aware of the possible fps?

Regards!!!

-- 
Ricardo Ribalda

                 reply	other threads:[~2015-06-30  7:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAPybu_2dTaf_RF2NR1mSqzW5=Hw0m+Ngm=UxE5T-VNKfCeHcrg@mail.gmail.com' \
    --to=ricardo.ribalda@gmail.com \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).