public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
	Sakari Ailus <sakari.ailus@iki.fi>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"HeungJun Kim/Mobile S/W Platform Lab(DMC)/E3"
	<riverful.kim@samsung.com>,
	"Seung-Woo Kim/Mobile S/W Platform Lab(DMC)/E4"
	<sw0312.kim@samsung.com>, Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [Q] Interleaved formats on the media bus
Date: Sat, 04 Feb 2012 12:36:53 +0100	[thread overview]
Message-ID: <2245415.4hXgTppUEj@avalon> (raw)
In-Reply-To: <Pine.LNX.4.64.1202021125210.13860@axis700.grange>

Hi Guennadi,

On Thursday 02 February 2012 12:00:57 Guennadi Liakhovetski wrote:
> On Thu, 2 Feb 2012, Laurent Pinchart wrote:
> > Do all those sensors interleave the data in the same way ? This sounds
> > quite hackish and vendor-specific to me, I'm not sure if we should try to
> > generalize that. Maybe vendor-specific media bus format codes would be
> > the way to go. I don't expect ISPs to understand the format, they will
> > likely be configured in pass-through mode. Instead of adding explicit
> > support for all those weird formats to all ISP drivers, it might make
> > sense to add a "binary blob" media bus code to be used by the ISP.
> 
> Yes, I agree, that those formats will be just forwarded as is by ISPs, but
> the user-space wants to know the contents, so, it might be more useful to
> provide information about specific components, even if their packing
> layout cannot be defined in a generic way with offsets and sizes. Even
> saying "you're getting formats YUYV and JPEG in vendor-specific packing
> #N" might be more useful, than just "vendor-specific format #N".

That's right. A single media bus code might not be the best option indeed. 
Vendor-specific blob codes (and 4CCs) then ?

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2012-02-04 11:37 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31 11:23 [Q] Interleaved formats on the media bus Sylwester Nawrocki
2012-02-01  1:44 ` Guennadi Liakhovetski
2012-02-01 10:44   ` Sylwester Nawrocki
2012-02-01 10:00 ` Sakari Ailus
2012-02-01 11:41   ` Sylwester Nawrocki
2012-02-02  9:55     ` Laurent Pinchart
2012-02-02 11:00       ` Guennadi Liakhovetski
2012-02-04 11:36         ` Laurent Pinchart [this message]
2012-02-02 11:14       ` Sylwester Nawrocki
2012-02-04 11:34         ` Laurent Pinchart
2012-02-04 17:00           ` Sylwester Nawrocki
2012-02-05 13:30             ` Laurent Pinchart
2012-02-08 22:48               ` Sylwester Nawrocki
     [not found]                 ` <12779203.vQPWKN8eZf@avalon>
2012-02-10  8:42                   ` Guennadi Liakhovetski
2012-02-10 10:19                     ` Sylwester Nawrocki
2012-02-10 10:31                       ` Sylwester Nawrocki
2012-02-10 10:33                       ` Guennadi Liakhovetski
2012-02-10 10:58                         ` Sylwester Nawrocki
2012-02-10 11:15                           ` Guennadi Liakhovetski
2012-02-10 11:35                             ` Sylwester Nawrocki
2012-02-10 11:51                               ` Guennadi Liakhovetski
2012-02-04 11:22     ` Sakari Ailus
2012-02-04 11:30       ` Laurent Pinchart
2012-02-04 15:38         ` Sylwester Nawrocki
2012-02-04 15:26       ` Sylwester Nawrocki
2012-02-04 15:43         ` Sakari Ailus
2012-02-04 18:32           ` Sylwester Nawrocki
2012-02-04 23:44             ` Guennadi Liakhovetski
2012-02-05  0:36               ` Sylwester Nawrocki
2012-02-05  0:04           ` Guennadi Liakhovetski

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=2245415.4hXgTppUEj@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=riverful.kim@samsung.com \
    --cc=s.nawrocki@samsung.com \
    --cc=sakari.ailus@iki.fi \
    --cc=sw0312.kim@samsung.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