From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ankit Nautiyal <ankit.k.nautiyal@intel.com>,
dri-devel@lists.freedesktop.org
Cc: uma.shankar@intel.com, maarten.lankhorst@intel.com,
swati2.sharma@intel.com
Subject: Re: [PATCH 4/4] drm/edid: Avoid multiple log lines for HFVSDB parsing
Date: Tue, 13 Sep 2022 16:54:53 +0300 [thread overview]
Message-ID: <87k0674bwy.fsf@intel.com> (raw)
In-Reply-To: <20220811054718.2115917-5-ankit.k.nautiyal@intel.com>
On Thu, 11 Aug 2022, Ankit Nautiyal <ankit.k.nautiyal@intel.com> wrote:
> Replace multiple log lines with a single log line at the end of
> parsing HF-VSDB. Also use drm_dbg_kms instead of DRM_DBG_KMS, and
> add log for DSC1.2 support.
>
> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> ---
> drivers/gpu/drm/drm_edid.c | 21 +++++++++++++--------
> 1 file changed, 13 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
> index c9c3a9c8fa26..7a319d570297 100644
> --- a/drivers/gpu/drm/drm_edid.c
> +++ b/drivers/gpu/drm/drm_edid.c
> @@ -5781,6 +5781,9 @@ static void drm_parse_hdmi_forum_scds(struct drm_connector *connector,
> struct drm_display_info *display = &connector->display_info;
> struct drm_hdmi_info *hdmi = &display->hdmi;
> struct drm_hdmi_dsc_cap *hdmi_dsc = &hdmi->dsc_cap;
> + u32 max_tmds_clock = 0;
This should be int because display->max_tmds_clock is int. Yes, it's a
change from the current local var, but logging u32 would require %u
instead of %d in the format string anyway, so better just use the right
type.
> + u8 max_frl_rate = 0;
> + bool dsc_support = false;
>
> display->has_hdmi_infoframe = true;
>
> @@ -5800,14 +5803,13 @@ static void drm_parse_hdmi_forum_scds(struct drm_connector *connector,
> */
>
> if (hf_scds[5]) {
> - /* max clock is 5000 KHz times block value */
> - u32 max_tmds_clock = hf_scds[5] * 5000;
> struct drm_scdc *scdc = &hdmi->scdc;
>
> + /* max clock is 5000 KHz times block value */
> + max_tmds_clock = hf_scds[5] * 5000;
> +
> if (max_tmds_clock > 340000) {
> display->max_tmds_clock = max_tmds_clock;
> - DRM_DEBUG_KMS("HF-VSDB: max TMDS clock %d kHz\n",
> - display->max_tmds_clock);
Hmm, the logic for what is logged gets changed.
> }
>
> if (scdc->supported) {
> @@ -5820,9 +5822,6 @@ static void drm_parse_hdmi_forum_scds(struct drm_connector *connector,
> }
>
> if (hf_scds[7]) {
> - u8 max_frl_rate;
> -
> - DRM_DEBUG_KMS("hdmi_21 sink detected. parsing edid\n");
> max_frl_rate = (hf_scds[7] & DRM_EDID_MAX_FRL_RATE_MASK) >> 4;
> drm_get_max_frl_rate(max_frl_rate, &hdmi->max_lanes,
> &hdmi->max_frl_rate_per_lane);
> @@ -5830,8 +5829,14 @@ static void drm_parse_hdmi_forum_scds(struct drm_connector *connector,
>
> drm_parse_ycbcr420_deep_color_info(connector, hf_scds);
>
> - if (cea_db_payload_len(hf_scds) >= 11 && hf_scds[11])
> + if (cea_db_payload_len(hf_scds) >= 11 && hf_scds[11]) {
> drm_parse_dsc_info(hdmi_dsc, hf_scds);
> + dsc_support = true;
> + }
> +
> + drm_dbg_kms(connector->dev,
> + "HF-VSDB: max TMDS clock:%d Khz, HDMI2.1 support:%s, DSC1.2 support:%s\n",
Nitpicks, %d needs int instead of u32, "kHz" not "Khz", "HDMI 2.1" and
"DSC 1.2" with spaces, would prefer a space after ":".
> + max_tmds_clock, max_frl_rate ? "yes" : "no", dsc_support ? "yes" : "no");
See str_yes_no().
BR,
Jani.
> }
>
> static void drm_parse_hdmi_deep_color_info(struct drm_connector *connector,
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-09-13 13:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 5:47 [PATCH 0/4] Fix HFVSDB parsing Ankit Nautiyal
2022-08-11 5:47 ` [PATCH 1/4] drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink Ankit Nautiyal
2022-08-11 5:47 ` [PATCH 2/4] drm/edid: Split DSC parsing into separate function Ankit Nautiyal
2022-09-13 13:55 ` Jani Nikula
2022-08-11 5:47 ` [PATCH 3/4] drm/edid: Refactor HFVSDB parsing for DSC1.2 Ankit Nautiyal
2022-09-13 13:55 ` Jani Nikula
2022-08-11 5:47 ` [PATCH 4/4] drm/edid: Avoid multiple log lines for HFVSDB parsing Ankit Nautiyal
2022-09-13 13:54 ` Jani Nikula [this message]
2022-09-14 10:09 ` Nautiyal, Ankit K
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=87k0674bwy.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=maarten.lankhorst@intel.com \
--cc=swati2.sharma@intel.com \
--cc=uma.shankar@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 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.