All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Scott Jiang <scott.jiang.linux@gmail.com>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	LMML <linux-media@vger.kernel.org>,
	uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: extend v4l2_mbus_framefmt
Date: Mon, 11 Jun 2012 10:33:47 +0200	[thread overview]
Message-ID: <201206111033.47369.hverkuil@xs4all.nl> (raw)
In-Reply-To: <CAHG8p1AW6577=oGPo3o8S0LgF2p8_cfmLLnvYbikk7kEaYdxzw@mail.gmail.com>

On Mon 11 June 2012 10:18:06 Scott Jiang wrote:
> Hi Guennadi and Hans,
> 
> We use v4l2_mbus_framefmt to get frame format on the media bus in
> bridge driver. It only contains width and height. It's not a big
> problem in SD. But we need more info like front porch, sync width and
> back porch (similar to disp_format_s in v4l2_formats.h) in HD. I want
> to add these fields in v4l2_mbus_framefmt or do you have any better
> solution?

Just a quick note for those who are wondering: disp_format_s was a custom
extension from a work-in-progress driver from Cisco. We are working hard on
upstreaming it, and the final version won't have that change.

Anyway, who exactly needs that information? Normally that information is set
or queried via VIDIOC_ENUM/G/S/QUERY_DV_TIMINGS (ENUM and QUERY got merged
in 3.5, see http://hverkuil.home.xs4all.nl/spec/media.html for the latest
documentation on these new ioctls).

I would expect that the combination of v4l2_mbus_framefmt + v4l2_dv_timings
gives you the information you need.

Regards,

	Hans

  reply	other threads:[~2012-06-11  8:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11  8:18 extend v4l2_mbus_framefmt Scott Jiang
2012-06-11  8:33 ` Hans Verkuil [this message]
2012-06-12  5:42   ` Scott Jiang
2012-06-12  7:05     ` Hans Verkuil
2012-06-13  5:31   ` Scott Jiang
2012-06-13 13:53     ` Hans Verkuil
2012-06-14  3:17       ` Scott Jiang
2012-06-15 11:34         ` Hans Verkuil
2012-06-20  9:05           ` Scott Jiang
2012-06-20 10:25             ` Sakari Ailus
2012-06-20 11:00               ` Hans Verkuil
2012-06-21  6:53                 ` Sakari Ailus
2012-06-21 10:02                   ` Hans Verkuil
2012-06-21 11:28                     ` Sakari Ailus

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=201206111033.47369.hverkuil@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-media@vger.kernel.org \
    --cc=scott.jiang.linux@gmail.com \
    --cc=uclinux-dist-devel@blackfin.uclinux.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 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.