Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Neil Armstrong <neil.armstrong@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Andrzej Hajda <andrzej.hajda@intel.com>,
	Robert Foss <rfoss@kernel.org>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	Jonas Karlman <jonas@kwiboo.se>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Rob Clark <robdclark@gmail.com>,
	Abhinav Kumar <quic_abhinavk@quicinc.com>,
	Sean Paul <sean@poorly.run>,
	Marijn Suijten <marijn.suijten@somainline.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org
Subject: Re: [PATCH 2/6] drm/atomic: add interlaced and ycbcr_420 flags to connector's state dump
Date: Mon, 21 Oct 2024 11:56:12 +0200	[thread overview]
Message-ID: <f9c2a209-1234-4663-b37a-9e0dabc448da@linaro.org> (raw)
In-Reply-To: <20241019-bridge-yuv420-v1-2-d74efac9e4e6@linaro.org>

On 18/10/2024 23:49, Dmitry Baryshkov wrote:
> Although the interlace_allowed and ycbcr_420_allowed flags are a part of
> the struct drm_connector rather than struct drm_connector_state, still
> include them into state dump in order to ease debugging of the setup
> issues.
> 
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
>   drivers/gpu/drm/drm_atomic.c | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/gpu/drm/drm_atomic.c b/drivers/gpu/drm/drm_atomic.c
> index 0fc99da93afe..9ea2611770f4 100644
> --- a/drivers/gpu/drm/drm_atomic.c
> +++ b/drivers/gpu/drm/drm_atomic.c
> @@ -1132,6 +1132,8 @@ static void drm_atomic_connector_print_state(struct drm_printer *p,
>   	drm_printf(p, "connector[%u]: %s\n", connector->base.id, connector->name);
>   	drm_printf(p, "\tcrtc=%s\n", state->crtc ? state->crtc->name : "(null)");
>   	drm_printf(p, "\tself_refresh_aware=%d\n", state->self_refresh_aware);
> +	drm_printf(p, "\tinterlace_allowed=%d\n", connector->interlace_allowed);
> +	drm_printf(p, "\tycbcr_420_allowed=%d\n", connector->ycbcr_420_allowed);
>   	drm_printf(p, "\tmax_requested_bpc=%d\n", state->max_requested_bpc);
>   	drm_printf(p, "\tcolorspace=%s\n", drm_get_colorspace_name(state->colorspace));
>   
> 

Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>

  reply	other threads:[~2024-10-21  9:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 21:49 [PATCH 0/6] drm/bridge: add ycbcr_420_allowed support Dmitry Baryshkov
2024-10-18 21:49 ` [PATCH 1/6] drm/display: bridge_connector: handle ycbcr_420_allowed Dmitry Baryshkov
2024-10-21  9:55   ` Neil Armstrong
2024-10-18 21:49 ` [PATCH 2/6] drm/atomic: add interlaced and ycbcr_420 flags to connector's state dump Dmitry Baryshkov
2024-10-21  9:56   ` Neil Armstrong [this message]
2024-10-18 21:49 ` [PATCH 3/6] drm/bridge: display-connector: allow YCbCr 420 for HDMI and DP Dmitry Baryshkov
2024-10-21  7:29   ` Neil Armstrong
2024-10-21  9:06     ` Dmitry Baryshkov
2024-10-21  9:54       ` neil.armstrong
2024-10-18 21:49 ` [PATCH 4/6] drm/bridge: aux: allow interlaced and YCbCr 420 output Dmitry Baryshkov
2024-10-21  9:54   ` Neil Armstrong
2024-10-18 21:49 ` [PATCH 5/6] drm/msm/dp: migrate the ycbcr_420_allowed to drm_bridge Dmitry Baryshkov
2024-10-21  9:57   ` Neil Armstrong
2024-10-21  9:57   ` Neil Armstrong
2024-10-21 18:55   ` Abhinav Kumar
2024-10-18 21:49 ` [PATCH 6/6] drm/bridge: dw-hdmi: set bridge's ycbcr_420_allowed flag Dmitry Baryshkov
2024-10-21  7:30   ` Neil Armstrong
2024-10-21  7:17 ` [PATCH 0/6] drm/bridge: add ycbcr_420_allowed support Maxime Ripard
2024-10-21 12:32 ` Neil Armstrong
2024-10-21 18:22   ` Dmitry Baryshkov
2024-10-22 12:15     ` neil.armstrong
2024-10-24 19:54 ` Dmitry Baryshkov

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=f9c2a209-1234-4663-b37a-9e0dabc448da@linaro.org \
    --to=neil.armstrong@linaro.org \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=marijn.suijten@somainline.org \
    --cc=mripard@kernel.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=rfoss@kernel.org \
    --cc=robdclark@gmail.com \
    --cc=sean@poorly.run \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /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