amd-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Harry Wentland <harry.wentland@amd.com>
To: <amd-gfx@lists.freedesktop.org>, <dri-devel@lists.freedesktop.org>
Cc: "Sebastian Wick" <sebastian.wick@redhat.com>,
	"Jani Nikula" <jani.nikula@linux.intel.com>,
	"Pekka Paalanen" <ppaalanen@gmail.com>,
	"Uma Shankar" <uma.shankar@intel.com>,
	Vitaly.Prosyak@amd.com, "Joshua Ashton" <joshua@froggi.es>,
	"Harry Wentland" <harry.wentland@amd.com>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Subject: [PATCH v2 02/21] drm/connector: print max_requested_bpc in state debugfs
Date: Fri, 13 Jan 2023 11:24:09 -0500	[thread overview]
Message-ID: <20230113162428.33874-3-harry.wentland@amd.com> (raw)
In-Reply-To: <20230113162428.33874-1-harry.wentland@amd.com>

This is useful to understand the bpc defaults and
support of a driver.

Signed-off-by: Harry Wentland <harry.wentland@amd.com>
Cc: Pekka Paalanen <ppaalanen@gmail.com>
Cc: Sebastian Wick <sebastian.wick@redhat.com>
Cc: Vitaly.Prosyak@amd.com
Cc: Uma Shankar <uma.shankar@intel.com>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Joshua Ashton <joshua@froggi.es>
Cc: Jani Nikula <jani.nikula@linux.intel.com>
Cc: dri-devel@lists.freedesktop.org
Cc: amd-gfx@lists.freedesktop.org
Reviewed-By: Joshua Ashton <joshua@froggi.es>
---
 drivers/gpu/drm/drm_atomic.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/gpu/drm/drm_atomic.c b/drivers/gpu/drm/drm_atomic.c
index f197f59f6d99..c0dc5858a723 100644
--- a/drivers/gpu/drm/drm_atomic.c
+++ b/drivers/gpu/drm/drm_atomic.c
@@ -1070,6 +1070,7 @@ 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, "\tmax_requested_bpc=%d\n", state->max_requested_bpc);
 
 	if (connector->connector_type == DRM_MODE_CONNECTOR_WRITEBACK)
 		if (state->writeback_job && state->writeback_job->fb)
-- 
2.39.0


  parent reply	other threads:[~2023-01-13 16:25 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13 16:24 [PATCH v2 00/21] Enable Colorspace connector property in amdgpu Harry Wentland
2023-01-13 16:24 ` [PATCH v2 01/21] drm/display: Don't block HDR_OUTPUT_METADATA on unknown EOTF Harry Wentland
2023-01-13 16:24 ` Harry Wentland [this message]
2023-01-13 16:24 ` [PATCH v2 03/21] drm/connector: Drop COLORIMETRY_NO_DATA Harry Wentland
2023-01-13 16:24 ` [PATCH v2 04/21] drm/connector: Convert DRM_MODE_COLORIMETRY to enum Harry Wentland
2023-01-13 19:31   ` Simon Ser
2023-01-13 16:24 ` [PATCH v2 05/21] drm/connector: Pull out common create_colorspace_property code Harry Wentland
2023-01-13 16:24 ` [PATCH v2 06/21] drm/connector: Allow drivers to pass list of supported colorspaces Harry Wentland
2023-01-13 16:24 ` [PATCH v2 07/21] drm/connector: Print connector colorspace in state debugfs Harry Wentland
2023-01-13 16:24 ` [PATCH v2 08/21] drm/amd/display: Always pass connector_state to stream validation Harry Wentland
2023-01-13 16:24 ` [PATCH v2 09/21] drm/amd/display: Register Colorspace property for DP and HDMI Harry Wentland
2023-01-13 16:24 ` [PATCH v2 10/21] drm/amd/display: Signal mode_changed if colorspace changed Harry Wentland
2023-01-24 15:26   ` Leo Li
2023-01-13 16:24 ` [PATCH v2 11/21] drm/amd/display: Send correct DP colorspace infopacket Harry Wentland
2023-01-13 16:24 ` [PATCH v2 12/21] drm/amd/display: Always set crtcinfo from create_stream_for_sink Harry Wentland
2023-01-13 16:24 ` [PATCH v2 13/21] drm/amd/display: Add support for explicit BT601_YCC Harry Wentland
2023-01-13 16:24 ` [PATCH v2 14/21] drm/amd/display: Add debugfs for testing output colorspace Harry Wentland
2023-01-13 16:24 ` [PATCH v2 15/21] drm/amd/display: Add default case for output_color_space switch Harry Wentland
2023-01-13 16:24 ` [PATCH v2 16/21] drm/amd/display: Don't restrict bpc to 8 bpc Harry Wentland
2023-01-13 16:24 ` [PATCH v2 17/21] drm/amd/display: Format input and output CSC matrix Harry Wentland
2023-01-24 15:12   ` Leo Li
2023-01-13 16:24 ` [PATCH v2 18/21] drm/amd/display: Fallback to 2020_YCBCR if the pixel encoding is not RGB Harry Wentland
2023-01-23 20:30   ` Sebastian Wick
2023-01-24 15:37     ` Harry Wentland
2023-01-24 18:57       ` Harry Wentland
2023-01-26  1:48         ` Sebastian Wick
2023-01-25 12:59     ` Joshua Ashton
2023-01-26  1:38       ` Sebastian Wick
2023-02-07 12:42       ` Pekka Paalanen
2023-01-13 16:24 ` [PATCH v2 19/21] drm/amd/display: Refactor avi_info_frame colorimetry determination Harry Wentland
2023-01-13 16:24 ` [PATCH v2 20/21] drm/amd/display: Calculate output_color_space after pixel encoding adjustment Harry Wentland
2023-01-13 16:24 ` [PATCH v2 21/21] drm/amd/display: Fix COLOR_SPACE_YCBCR2020_TYPE matrix Harry Wentland
2023-02-07 12:47 ` [PATCH v2 00/21] Enable Colorspace connector property in amdgpu Pekka Paalanen
2023-02-18 10:33   ` Hans Verkuil
2023-03-21 13:12 ` Sebastian Wick

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=20230113162428.33874-3-harry.wentland@amd.com \
    --to=harry.wentland@amd.com \
    --cc=Vitaly.Prosyak@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joshua@froggi.es \
    --cc=ppaalanen@gmail.com \
    --cc=sebastian.wick@redhat.com \
    --cc=uma.shankar@intel.com \
    --cc=ville.syrjala@linux.intel.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;
as well as URLs for NNTP newsgroup(s).