From: Philipp Zabel <p.zabel@pengutronix.de>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Mauro Carvalho Chehab <m.chehab@samsung.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
linux-media@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH v2 1/3] Add BGR888_1X24 and GBR888_1X24 media bus formats
Date: Mon, 02 Feb 2015 16:21:00 +0100 [thread overview]
Message-ID: <1422890460.6112.9.camel@pengutronix.de> (raw)
In-Reply-To: <54CF92DD.6020308@xs4all.nl>
Am Montag, den 02.02.2015, 16:08 +0100 schrieb Hans Verkuil:
> On 12/03/2014 02:53 PM, Philipp Zabel wrote:
> > This patch adds two more 24-bit RGB formats. BGR888 is more or less common,
> > GBR888 is used on the internal connection between the IPU display interface
> > and the TVE (VGA DAC) on i.MX53 SoCs.
> >
> > Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> > Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>
> This three-part patch series doesn't apply. Is it on top of another patch
> series?
It is on top of "Add RGB444_1X12 and RGB565_1X16 media bus formats" and
"Add LVDS RGB media bus formats".
> Anyway, it can't be merged unless it is actually used in a driver.
I'd like to use these in the imx-drm driver, so this is kind of a
chicken and egg situation. Shall I submit a patch that uses the defines
to dri-devel and reference it here?
regards
Philipp
next prev parent reply other threads:[~2015-02-02 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 13:53 [PATCH v2 1/3] Add BGR888_1X24 and GBR888_1X24 media bus formats Philipp Zabel
2014-12-03 13:53 ` [PATCH v2 2/3] Add YUV8_1X24 media bus format Philipp Zabel
2014-12-03 13:53 ` [PATCH 3/3] Add RGB666_1X24_CPADHI " Philipp Zabel
2015-02-02 15:08 ` [PATCH v2 1/3] Add BGR888_1X24 and GBR888_1X24 media bus formats Hans Verkuil
2015-02-02 15:21 ` Philipp Zabel [this message]
2015-02-02 15:24 ` Mauro Carvalho Chehab
2015-02-02 15:34 ` Philipp Zabel
2015-02-02 15:48 ` Boris Brezillon
2015-02-02 16:51 ` Philipp Zabel
2015-02-04 14:43 ` Sakari Ailus
2015-03-24 9:40 ` 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=1422890460.6112.9.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=boris.brezillon@free-electrons.com \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=kernel@pengutronix.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@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