Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t] tools/intel_vbt_decode: Dump mode backlight data
Date: Mon, 20 Feb 2023 18:49:27 +0200	[thread overview]
Message-ID: <20230220164927.27283-1-ville.syrjala@linux.intel.com> (raw)

From: Ville Syrjälä <ville.syrjala@linux.intel.com>

Dump the new stuff from the backlight block:
- brightness_level
- brightness_min_level
- brightness_precision_bits
- hdr_dpcd_refresh_timeout

Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
 tools/intel_vbt_decode.c | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/tools/intel_vbt_decode.c b/tools/intel_vbt_decode.c
index 8f707c1f822a..7caa71dac793 100644
--- a/tools/intel_vbt_decode.c
+++ b/tools/intel_vbt_decode.c
@@ -626,6 +626,21 @@ static void dump_backlight_info(struct context *context,
 
 		printf("\t\tControl type: %u\n", control->type);
 		printf("\t\tController: %u\n", control->controller);
+
+		if (context->bdb->version >= 234) {
+			printf("\t\tBrightness level: %u\n",
+			       backlight->brightness_level[i].level);
+			printf("\t\tBrightness min level: %u\n",
+			       backlight->brightness_min_level[i].level);
+		}
+
+		if (context->bdb->version >= 236)
+			printf("\t\tBrigthness precision bits: %u\n",
+			       backlight->brightness_precision_bits[i]);
+
+		if (context->bdb->version >= 239)
+			printf("\t\tHDR DPCD refresh timeout: %.2f ms\n",
+			       backlight->hdr_dpcd_refresh_timeout[i] / 100.0);
 	}
 }
 
-- 
2.39.2

             reply	other threads:[~2023-02-20 16:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 16:49 Ville Syrjala [this message]
2023-02-20 18:02 ` [igt-dev] ✗ Fi.CI.BAT: failure for tools/intel_vbt_decode: Dump mode backlight data Patchwork
2023-02-28 20:14   ` Kamil Konieczny
2023-03-02  6:04     ` Yedireswarapu, SaiX Nandan
2023-02-27 17:17 ` [igt-dev] [PATCH i-g-t] " Jani Nikula

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=20230220164927.27283-1-ville.syrjala@linux.intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox