On Thu, 26 Nov 2009, Guennadi Liakhovetski wrote:
From 8b24c617e1ac4d324538a3eec476d48b85c2091f Mon Sep 17 00:00:00 2001
From: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
Date: Thu, 26 Nov 2009 18:20:45 +0100
Subject: [PATCH] v4l: add a media-bus API for configuring v4l2 subdev pixel and frame formats
Video subdevices, like cameras, decoders, connect to video bridges over
specialised busses. Data is being transferred over these busses in various
formats, which only loosely correspond to fourcc codes, describing how video
data is stored in RAM. This is not a one-to-one correspondence, therefore we
cannot use fourcc codes to configure subdevice output data formats. This patch
adds codes for several such on-the-bus formats and an API, similar to the
familiar .s_fmt(), .g_fmt(), .try_fmt(), .enum_fmt() API for configuring those
codes. After all users of the old API in struct v4l2_subdev_video_ops are
converted, it will be removed. Also add helper routines to support generic
pass-through mode for the soc-camera framework.
Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
---
v2 -> v3: more comments:
1. moved enum v4l2_mbus_packing, enum v4l2_mbus_order, and struct
v4l2_mbus_pixelfmt to soc-camera specific header, renamed them into
soc-namespace.
2. commented enum v4l2_mbus_pixelcode and removed unused values.
v1 -> v2: addressed comments from Hans, namely:
1. renamed image bus to media bus, now using "mbus" as a shorthand in
function and data type names.
2. made media-bus helper functions soc-camera local.
3. moved colorspace from struct v4l2_mbus_pixelfmt to struct
v4l2_mbus_framefmt.
4. added documentation for data types and enums.
5. added
V4L2_MBUS_FMT_FIXED = 1,
format as the first in enum.
soc-camera driver port will follow tomorrow.
Thanks
Guennadi
drivers/media/video/Makefile | 2 +-
drivers/media/video/soc_mediabus.c | 157 ++++++++++++++++++++++++++++++++++++
include/media/soc_mediabus.h | 84 +++++++++++++++++++
include/media/v4l2-mediabus.h | 59 ++++++++++++++
include/media/v4l2-subdev.h | 19 ++++-
<cut>
diff --git a/include/media/v4l2-mediabus.h b/include/media/v4l2-mediabus.h
new file mode 100644
index 0000000..359840c
--- /dev/null
+++ b/include/media/v4l2-mediabus.h
@@ -0,0 +1,59 @@
+/*
+ * Media Bus API header
+ *
+ * Copyright (C) 2009, Guennadi Liakhovetski <g.liakhovetski@xxxxxx>
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ */
+
+#ifndef V4L2_MEDIABUS_H
+#define V4L2_MEDIABUS_H
+
+/*
+ * These pixel codes uniquely identify data formats on the media bus. Mostly
+ * they correspond to similarly named V4L2_PIX_FMT_* formats, format 0 is
+ * reserved, V4L2_MBUS_FMT_FIXED shall be used by host-client pairs, where the
+ * data format is fixed. Additionally, "2X8" means that one pixel is transferred
+ * in two 8-bit samples, "BE" or "LE" specify in which order those samples
+ * should be stored in RAM, and "PADHI" and "PADLO" define which bits - low or
+ * high, in the incomplete high byte, are filled with padding bits.
+ */
Hi Guennadi,
This still needs some improvement. There are two things that need to be changed here:
1) add the width of the data bus to the format name: so V4L2_MBUS_FMT_YUYV
becomes _FMT_YUYV_8. This is required since I know several video receivers
that can be programmed to use one of several data widths (8, 10, 12 bits per
color component). Perhaps _1X8 is even better since that is nicely consistent
with the 2X8 suffix that you already use. The PADHI and PADLO naming convention
is fine and should be used whereever it is neeeded. Ditto for BE and LE.
2) Rephrase '"BE" or "LE" specify in which order those samples should be stored
in RAM' to:
'"BE" or "LE" specify in which order those samples are transferred over the bus:
BE means that the most significant bits are transferred first, "LE" means that
the least significant bits are transferred first.'
This also means that formats like RGB555 need to be renamed to RGB555_2X8_PADHI_LE.
I think that this would make this list of pixelcodes unambiguous and
understandable.
Regards,
Hans
+enum v4l2_mbus_pixelcode {
+ V4L2_MBUS_FMT_FIXED = 1,
+ V4L2_MBUS_FMT_YUYV,
+ V4L2_MBUS_FMT_YVYU,
+ V4L2_MBUS_FMT_UYVY,
+ V4L2_MBUS_FMT_VYUY,
+ V4L2_MBUS_FMT_RGB555,
+ V4L2_MBUS_FMT_RGB555X,
+ V4L2_MBUS_FMT_RGB565,
+ V4L2_MBUS_FMT_RGB565X,
+ V4L2_MBUS_FMT_SBGGR8,
+ V4L2_MBUS_FMT_SBGGR10,
+ V4L2_MBUS_FMT_GREY,
+ V4L2_MBUS_FMT_Y10,
+ V4L2_MBUS_FMT_SBGGR10_2X8_PADHI_BE,
+ V4L2_MBUS_FMT_SBGGR10_2X8_PADLO_BE,
+ V4L2_MBUS_FMT_SBGGR10_2X8_PADHI_LE,
+ V4L2_MBUS_FMT_SBGGR10_2X8_PADLO_LE,
+};
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
