All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: kieran.bingham+renesas@ideasonboard.com
Cc: David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org,
	linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm: rcar-du: Remove packed VYUY support
Date: Fri, 14 Sep 2018 17:00:43 +0300	[thread overview]
Message-ID: <2071986.YnXjGQr2Jv@avalon> (raw)
In-Reply-To: <7d2740f2-923c-4b5d-0d1e-c24fb4a8bceb@ideasonboard.com>

Hi Kieran,

On Friday, 14 September 2018 16:55:38 EEST Kieran Bingham wrote:
> On 14/09/18 14:51, Laurent Pinchart wrote:
> > On Friday, 14 September 2018 16:21:49 EEST Kieran Bingham wrote:
> >> The Gen3 VSP used by the DU for display does not support packed the VYUY
> >> pixel format. Gen2 VSP hardware is able to process this format, but it
> >> is not officially supported there either and thus it's output can not be
> >> guaranteed.
> > 
> > I think we could guarantee proper operation on Gen2, but as DU + VSP
> > operation isn't enabled in the drivers by default, and as the VYUY format
> > isn't a strategic target, I think we can ignore that.
> > 
> > How about updating the commit message as follows ?
> > 
> > "The Gen3 VSP used by the DU for display does not support packed the VYUY
> 
> s/packed the/the packed/
> 
> Which was a fault in my original text :)
> 
> > pixel format. Gen2 VSP hardware is able to process this format, but DU +
> > VSP operation isn't enabled on Gen2, and VYUY isn't a strategic format,
> > so it can be ignored."
> 
> That sounds fine to me, though I don't think we would even need to state
> that 'VYUY isn't a strategic format' once it's simply not available on
> the only platform that is enabled to use the VSP. But I don't object to
> stating it otherwise.

It could be enabled in the drivers (I have out-of-tree patches for testing 
purpose), so the fact that we don't need the format is still important I 
think.

> >> Remove the format from the capabilities of the DU driver.
> >> 
> >> Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
> > 
> > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > 
> >> ---
> >> 
> >>  drivers/gpu/drm/rcar-du/rcar_du_vsp.c | 2 --
> >>  1 file changed, 2 deletions(-)
> >> 
> >> diff --git a/drivers/gpu/drm/rcar-du/rcar_du_vsp.c
> >> b/drivers/gpu/drm/rcar-du/rcar_du_vsp.c index 4480243813ec..4576119e7777
> >> 100644
> >> --- a/drivers/gpu/drm/rcar-du/rcar_du_vsp.c
> >> +++ b/drivers/gpu/drm/rcar-du/rcar_du_vsp.c
> >> @@ -126,7 +126,6 @@ static const u32 formats_kms[] = {
> >>  	DRM_FORMAT_ARGB8888,
> >>  	DRM_FORMAT_XRGB8888,
> >>  	DRM_FORMAT_UYVY,
> >> -	DRM_FORMAT_VYUY,
> >>  	DRM_FORMAT_YUYV,
> >>  	DRM_FORMAT_YVYU,
> >>  	DRM_FORMAT_NV12,
> >> @@ -155,7 +154,6 @@ static const u32 formats_v4l2[] = {
> >>  	V4L2_PIX_FMT_ABGR32,
> >>  	V4L2_PIX_FMT_XBGR32,
> >>  	V4L2_PIX_FMT_UYVY,
> >> -	V4L2_PIX_FMT_VYUY,
> >>  	V4L2_PIX_FMT_YUYV,
> >>  	V4L2_PIX_FMT_YVYU,
> >>  	V4L2_PIX_FMT_NV12M,

-- 
Regards,

Laurent Pinchart

WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: kieran.bingham+renesas@ideasonboard.com
Cc: David Airlie <airlied@linux.ie>,
	linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: rcar-du: Remove packed VYUY support
Date: Fri, 14 Sep 2018 17:00:43 +0300	[thread overview]
Message-ID: <2071986.YnXjGQr2Jv@avalon> (raw)
In-Reply-To: <7d2740f2-923c-4b5d-0d1e-c24fb4a8bceb@ideasonboard.com>

Hi Kieran,

On Friday, 14 September 2018 16:55:38 EEST Kieran Bingham wrote:
> On 14/09/18 14:51, Laurent Pinchart wrote:
> > On Friday, 14 September 2018 16:21:49 EEST Kieran Bingham wrote:
> >> The Gen3 VSP used by the DU for display does not support packed the VYUY
> >> pixel format. Gen2 VSP hardware is able to process this format, but it
> >> is not officially supported there either and thus it's output can not be
> >> guaranteed.
> > 
> > I think we could guarantee proper operation on Gen2, but as DU + VSP
> > operation isn't enabled in the drivers by default, and as the VYUY format
> > isn't a strategic target, I think we can ignore that.
> > 
> > How about updating the commit message as follows ?
> > 
> > "The Gen3 VSP used by the DU for display does not support packed the VYUY
> 
> s/packed the/the packed/
> 
> Which was a fault in my original text :)
> 
> > pixel format. Gen2 VSP hardware is able to process this format, but DU +
> > VSP operation isn't enabled on Gen2, and VYUY isn't a strategic format,
> > so it can be ignored."
> 
> That sounds fine to me, though I don't think we would even need to state
> that 'VYUY isn't a strategic format' once it's simply not available on
> the only platform that is enabled to use the VSP. But I don't object to
> stating it otherwise.

It could be enabled in the drivers (I have out-of-tree patches for testing 
purpose), so the fact that we don't need the format is still important I 
think.

> >> Remove the format from the capabilities of the DU driver.
> >> 
> >> Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
> > 
> > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > 
> >> ---
> >> 
> >>  drivers/gpu/drm/rcar-du/rcar_du_vsp.c | 2 --
> >>  1 file changed, 2 deletions(-)
> >> 
> >> diff --git a/drivers/gpu/drm/rcar-du/rcar_du_vsp.c
> >> b/drivers/gpu/drm/rcar-du/rcar_du_vsp.c index 4480243813ec..4576119e7777
> >> 100644
> >> --- a/drivers/gpu/drm/rcar-du/rcar_du_vsp.c
> >> +++ b/drivers/gpu/drm/rcar-du/rcar_du_vsp.c
> >> @@ -126,7 +126,6 @@ static const u32 formats_kms[] = {
> >>  	DRM_FORMAT_ARGB8888,
> >>  	DRM_FORMAT_XRGB8888,
> >>  	DRM_FORMAT_UYVY,
> >> -	DRM_FORMAT_VYUY,
> >>  	DRM_FORMAT_YUYV,
> >>  	DRM_FORMAT_YVYU,
> >>  	DRM_FORMAT_NV12,
> >> @@ -155,7 +154,6 @@ static const u32 formats_v4l2[] = {
> >>  	V4L2_PIX_FMT_ABGR32,
> >>  	V4L2_PIX_FMT_XBGR32,
> >>  	V4L2_PIX_FMT_UYVY,
> >> -	V4L2_PIX_FMT_VYUY,
> >>  	V4L2_PIX_FMT_YUYV,
> >>  	V4L2_PIX_FMT_YVYU,
> >>  	V4L2_PIX_FMT_NV12M,

-- 
Regards,

Laurent Pinchart



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

  reply	other threads:[~2018-09-14 19:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-14 13:21 [PATCH] drm: rcar-du: Remove packed VYUY support Kieran Bingham
2018-09-14 13:51 ` Laurent Pinchart
2018-09-14 13:51   ` Laurent Pinchart
2018-09-14 13:55   ` Kieran Bingham
2018-09-14 13:55     ` Kieran Bingham
2018-09-14 14:00     ` Laurent Pinchart [this message]
2018-09-14 14:00       ` Laurent Pinchart

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=2071986.YnXjGQr2Jv@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.