dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Emil Renner Berthing <kernel@esmil.dk>,
	Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	dri-devel@lists.freedesktop.org,
	Hans Verkuil <hans.verkuil@cisco.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	kernel@pengutronix.de, Steve Longerbeam <slongerbeam@gmail.com>,
	Russell King <rmk+kernel@arm.linux.org.uk>
Subject: Re: [PATCH v2 05/10] Add RGB666_1X24_CPADHI media bus format
Date: Thu, 05 Feb 2015 10:42:46 +0100	[thread overview]
Message-ID: <1423129366.3207.7.camel@pengutronix.de> (raw)
In-Reply-To: <54D22EB0.1080602@linux.intel.com>

Hi Sakari,

Am Mittwoch, den 04.02.2015, 16:37 +0200 schrieb Sakari Ailus:
> Hi Philipp,
> 
> Could you add linux-media next time you send the set, please? I think 
> that's the most relevant list for the format related patches.

Will do in the next round. Let's see what Mauro thinks about your
concern regarding potential conflicts in
include/uapi/linux/media-bus-format.h when merging changes through both
drm and media.

> Philipp Zabel wrote:
> > Commit 9e74d2926a28 ("staging: imx-drm: add LVDS666 support for parallel
> > display") describes a 24-bit bus format where three 6-bit components each
> > take the lower part of 8 bits with the two high bits zero padded. Add a
> > component-wise padded media bus format RGB666_1X24_CPADHI to support this
> > connection.
> >
> > Cc: Emil Renner Berthing <kernel@esmil.dk>
> > Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> > ---
> >   Documentation/DocBook/media/v4l/subdev-formats.xml | 30 ++++++++++++++++++++++
> >   include/uapi/linux/media-bus-format.h              |  3 ++-
> >   2 files changed, 32 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/DocBook/media/v4l/subdev-formats.xml b/Documentation/DocBook/media/v4l/subdev-formats.xml
> > index 8d1f624..c02af7a 100644
> > --- a/Documentation/DocBook/media/v4l/subdev-formats.xml
> > +++ b/Documentation/DocBook/media/v4l/subdev-formats.xml
> > @@ -480,6 +480,36 @@ see <xref linkend="colorspaces" />.</entry>
> >   	      <entry>b<subscript>1</subscript></entry>
> >   	      <entry>b<subscript>0</subscript></entry>
> >   	    </row>
> > +	    <row id="MEDIA-BUS-FMT-RGB666-1X24_CPADHI">
> > +	      <entry>MEDIA_BUS_FMT_RGB666_1X24_CPADHI</entry>
> 
> Could you add a note on "C" in front of PADHI to the explanation in 
> media-bus-format.h?

Thanks, how about this addition:

-----8<-----
From: Philipp Zabel <p.zabel@pengutronix.de>
Subject: [PATCH] fixup! [media] Add RGB666_1X24_CPADHI media bus format

---
 Documentation/DocBook/media/v4l/subdev-formats.xml | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/Documentation/DocBook/media/v4l/subdev-formats.xml b/Documentation/DocBook/media/v4l/subdev-formats.xml
index 0b022a1..a9f62e9 100644
--- a/Documentation/DocBook/media/v4l/subdev-formats.xml
+++ b/Documentation/DocBook/media/v4l/subdev-formats.xml
@@ -91,7 +91,9 @@ see <xref linkend="colorspaces" />.</entry>
 	<listitem><para>For formats where the total number of bits per pixel is smaller
 	than the number of bus samples per pixel times the bus width, a padding
 	value stating if the bytes are padded in their most high order bits
-	(PADHI) or low order bits (PADLO).</para></listitem>
+	(PADHI) or low order bits (PADLO). A "C" prefix is used for component-wise
+	padding in the most high order bits (CPADHI) or low order bits (CPADLO)
+	of each separate component.</para></listitem>
 	<listitem><para>For formats where the number of bus samples per pixel is larger
 	than 1, an endianness value stating if the pixel is transferred MSB first
 	(BE) or LSB first (LE).</para></listitem>
@@ -103,6 +105,10 @@ see <xref linkend="colorspaces" />.</entry>
       samples per pixel with the most significant bits (padding, red and half of
       the green value) transferred first will be named
       <constant>MEDIA_BUS_FMT_RGB555_2X8_PADHI_BE</constant>.
+      A format where pixels are encoded as 6-bit red, green and blue values,
+      transferred as 1 24-bit sample per pixel where each component is padded to
+      8-bits with the 2-bit padding in the most significant bits will be named
+      <constant>MEDIA_BUS_FMT_RGB666_1X24_CPADHI</constant>.
       </para>
 
       <para>The following tables list existing packed RGB formats.</para>
-- 
2.1.4
----->8-----

regards
Philipp

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-02-05  9:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03 18:34 [PATCH v2 00/10] Use media bus formats in imx-drm and add drm panel support Philipp Zabel
2015-02-03 18:34 ` [PATCH v2 01/10] Add RGB444_1X12 and RGB565_1X16 media bus formats Philipp Zabel
2015-02-03 18:34 ` [PATCH v2 02/10] Add LVDS RGB " Philipp Zabel
2015-02-03 18:34 ` [PATCH v2 03/10] Add BGR888_1X24 and GBR888_1X24 " Philipp Zabel
2015-02-03 18:34 ` [PATCH v2 04/10] Add YUV8_1X24 media bus format Philipp Zabel
2015-02-03 18:34 ` [PATCH v2 05/10] Add RGB666_1X24_CPADHI " Philipp Zabel
2015-02-04 14:37   ` Sakari Ailus
2015-02-05  9:42     ` Philipp Zabel [this message]
2015-02-05 10:04       ` Sakari Ailus
2015-02-03 18:35 ` [PATCH v2 06/10] drm/imx: switch to use media bus formats Philipp Zabel
2015-02-03 18:35 ` [PATCH v2 07/10] drm/imx: consolidate bus format variable names Philipp Zabel
2015-02-03 18:35 ` [PATCH v2 08/10] drm/imx: imx-ldb: add drm_panel support Philipp Zabel
2015-02-03 18:35 ` [PATCH v2 09/10] drm/imx: imx-ldb: reset display clock input when disabling LVDS Philipp Zabel
2015-02-03 18:35 ` [PATCH v2 10/10] drm/imx: imx-ldb: allow to determine bus format from the connected panel Philipp Zabel

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=1423129366.3207.7.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hans.verkuil@cisco.com \
    --cc=kernel@esmil.dk \
    --cc=kernel@pengutronix.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=mchehab@osg.samsung.com \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=sakari.ailus@linux.intel.com \
    --cc=slongerbeam@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