From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
dri-devel@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
linux-media@vger.kernel.org,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/5] video: move mediabus format definition to a more standard place
Date: Tue, 30 Sep 2014 09:37:57 +0200 [thread overview]
Message-ID: <20140930093757.003741ac@bbrezillon> (raw)
In-Reply-To: <3849580.CgKEmcV7as@avalon>
On Mon, 29 Sep 2014 23:41:09 +0300
Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:
> Hi Boris,
>
> Thank you for the patch.
>
> On Monday 29 September 2014 16:02:39 Boris Brezillon wrote:
> > Rename mediabus formats and move the enum into a separate header file so
> > that it can be used by DRM/KMS subsystem without any reference to the V4L2
> > subsystem.
> >
> > Old V4L2_MBUS_FMT_ definitions are now macros that points to VIDEO_BUS_FMT_
> > definitions.
> >
> > Signed-off-by: Boris BREZILLON <boris.brezillon@free-electrons.com>
> > Acked-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> > ---
> > include/uapi/linux/Kbuild | 1 +
> > include/uapi/linux/v4l2-mediabus.h | 183 +++++++++++++------------------
> > include/uapi/linux/video-bus-format.h | 127 +++++++++++++++++++++++
> > 3 files changed, 207 insertions(+), 104 deletions(-)
> > create mode 100644 include/uapi/linux/video-bus-format.h
>
> One of the self-inflicted rules in V4L2 is to properly document every new
> media bus format when adding it to the kernel. The documentation is located in
> Documentation/DocBook/media/v4l/subdev-formats.xml. If we move the formats to
> a centralized header (which I believe is a good idea), we should also update
> the documentation, and possibly its location. I really want to avoid getting
> undocumented formats merged, and this will happen if we don't make the rule
> clear and/or don't make the documentation easily accessible.
Any idea where this new documentation should go
(Documentation/DocBook/video/video-bus-formats.xml) ?
>
> Incidentally, patch 2/5 in this series is missing a documentation update ;-)
Yep, regarding this patch, I wonder if it's really necessary to add
new formats to the v4l2_mbus_pixelcode enum.
If we want to move to this new common definition (across the video
related subsytems), we should deprecate the old enum
v4l2_mbus_pixelcode, and this start by not adding new formats, don't
you think ?
Best Regards,
Boris
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-30 7:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 14:02 [PATCH v2 0/5] video: describe data bus formats Boris Brezillon
2014-09-29 14:02 ` [PATCH v2 1/5] video: move mediabus format definition to a more standard place Boris Brezillon
2014-09-29 14:10 ` Boris BREZILLON
2014-09-29 14:40 ` Thierry Reding
2014-09-29 20:41 ` Laurent Pinchart
2014-09-30 7:37 ` Boris Brezillon [this message]
2014-09-30 8:39 ` Thierry Reding
2014-09-30 9:44 ` Boris Brezillon
2014-09-30 21:00 ` Laurent Pinchart
2014-11-03 11:03 ` Boris Brezillon
2014-11-03 14:06 ` Hans Verkuil
2014-09-29 14:02 ` [PATCH v2 2/5] video: add RGB444_1X12 and RGB565_1X16 bus formats Boris Brezillon
2014-11-03 18:15 ` Mauro Carvalho Chehab
2014-09-29 14:02 ` [PATCH v2 3/5] drm: add bus_formats and nbus_formats fields to drm_display_info Boris Brezillon
2014-09-29 14:02 ` [PATCH v2 4/5] drm: panel: simple-panel: add support for bus_format retrieval Boris Brezillon
2014-09-29 14:02 ` [PATCH v2 5/5] drm: panel: simple-panel: add bus format information for foxlink panel Boris Brezillon
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=20140930093757.003741ac@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=g.liakhovetski@gmx.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=thierry.reding@gmail.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