[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1496065877.17695.82.camel@pengutronix.de>
Date: Mon, 29 May 2017 15:51:17 +0200
From: Philipp Zabel <p.zabel@...gutronix.de>
To: Hans Verkuil <hverkuil@...all.nl>
Cc: Steve Longerbeam <slongerbeam@...il.com>, robh+dt@...nel.org,
mark.rutland@....com, shawnguo@...nel.org, kernel@...gutronix.de,
fabio.estevam@....com, linux@...linux.org.uk, mchehab@...nel.org,
nick@...anahar.org, markus.heiser@...marIT.de,
laurent.pinchart+renesas@...asonboard.com, bparrot@...com,
geert@...ux-m68k.org, arnd@...db.de, sudipm.mukherjee@...il.com,
minghsiu.tsai@...iatek.com, tiffany.lin@...iatek.com,
jean-christophe.trotin@...com, horms+renesas@...ge.net.au,
niklas.soderlund+renesas@...natech.se, robert.jarzmik@...e.fr,
songjun.wu@...rochip.com, andrew-ct.chen@...iatek.com,
gregkh@...uxfoundation.org, shuah@...nel.org,
sakari.ailus@...ux.intel.com, pavel@....cz,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-media@...r.kernel.org,
devel@...verdev.osuosl.org,
Steve Longerbeam <steve_longerbeam@...tor.com>
Subject: Re: [PATCH v7 15/34] add mux and video interface bridge entity
functions
On Mon, 2017-05-29 at 15:37 +0200, Hans Verkuil wrote:
> On 05/25/2017 02:29 AM, Steve Longerbeam wrote:
> > From: Philipp Zabel <p.zabel@...gutronix.de>
> >
> > Signed-off-by: Philipp Zabel <p.zabel@...gutronix.de>
> >
> > - renamed MEDIA_ENT_F_MUX to MEDIA_ENT_F_VID_MUX
> >
> > Signed-off-by: Steve Longerbeam <steve_longerbeam@...tor.com>
> > ---
> > Documentation/media/uapi/mediactl/media-types.rst | 22 ++++++++++++++++++++++
> > include/uapi/linux/media.h | 6 ++++++
> > 2 files changed, 28 insertions(+)
> >
> > diff --git a/Documentation/media/uapi/mediactl/media-types.rst b/Documentation/media/uapi/mediactl/media-types.rst
> > index 2a5164a..47ee003 100644
> > --- a/Documentation/media/uapi/mediactl/media-types.rst
> > +++ b/Documentation/media/uapi/mediactl/media-types.rst
> > @@ -299,6 +299,28 @@ Types and flags used to represent the media graph elements
> > received on its sink pad and outputs the statistics data on
> > its source pad.
> >
> > + - .. row 29
> > +
> > + .. _MEDIA-ENT-F-VID-MUX:
> > +
> > + - ``MEDIA_ENT_F_VID_MUX``
> > +
> > + - Video multiplexer. An entity capable of multiplexing must have at
> > + least two sink pads and one source pad, and must pass the video
> > + frame(s) received from the active sink pad to the source pad. Video
> > + frame(s) from the inactive sink pads are discarded.
> > +
> > + - .. row 30
> > +
> > + .. _MEDIA-ENT-F-VID-IF-BRIDGE:
> > +
> > + - ``MEDIA_ENT_F_VID_IF_BRIDGE``
> > +
> > + - Video interface bridge. A video interface bridge entity must have at
> > + least one sink pad and one source pad. It receives video frame(s) on
> > + its sink pad in one bus format (HDMI, eDP, MIPI CSI-2, ...) and
> > + converts them and outputs them on its source pad in another bus format
> > + (eDP, MIPI CSI-2, parallel, ...).
>
> I'm unhappy with the term 'bus format'. It's too close to 'mediabus format'.
> How about calling it "bus protocol"?
How about:
"It receives video frames on its sink pad from an input video bus
of one type (HDMI, eDP, MIPI CSI-2, ...), and outputs them on its
source pad to an output video bus of another type (eDP, MIPI
CSI-2, parallel, ...)."
regards
Philipp
Powered by blists - more mailing lists