Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 6/6] tools/intel_vbt_decode: Decode the backlight control method type
Date: Tue, 30 Sep 2025 11:27:02 +0300	[thread overview]
Message-ID: <9dd263be40ecff813e24240cfe166473c90fac0e@intel.com> (raw)
In-Reply-To: <20250929192127.5865-7-ville.syrjala@linux.intel.com>

On Mon, 29 Sep 2025, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Decode the backlight control method type to a human readable form.
>
> TODO: looks like the we might not be handling some of this
>       correctly on the kernel side...
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>  tools/intel_vbt_decode.c | 14 +++++++++++++-
>  1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/tools/intel_vbt_decode.c b/tools/intel_vbt_decode.c
> index 68d02aee9f5a..e42aed542612 100644
> --- a/tools/intel_vbt_decode.c
> +++ b/tools/intel_vbt_decode.c
> @@ -734,6 +734,17 @@ static const char * const i2c_speed_str[] = {
>  	[3] = "1 MHz",
>  };
>  
> +static const char * const control_type_str[] = {
> +	[0] = "PMIC pin",
> +	[1] = "LPSS PWM",
> +	[2] = "PWM from Display Engine/Aux Default",
> +	[3] = "CABC/PWM From LCD Panel",

The spec says, "CABC method to control brightness/PWM From LCD Panel",
but feels like it's been butchered at some point. It's DSI DCS, right?
And it might or might not have CABC.

*shrug*

> +	[4] = "Panel driver interface",
> +	[5] = "Legacy VESA eDP AUX Interface",
> +	[6] = "PWM from Display Engine/VESA eDP1.5 SCR AUX Interface",
> +	[7] = "PWM from Display Engine/Custom eDP AUX Interface",
> +};
> +
>  static void dump_backlight_info(struct context *context,
>  				const struct bdb_block *block)
>  {
> @@ -782,7 +793,8 @@ static void dump_backlight_info(struct context *context,
>  
>  		control = &backlight->backlight_control[i];
>  
> -		printf("\t\tControl type: %u\n", control->type);
> +		printf("\t\tControl type: %s (%u)\n",
> +		       to_str(control_type_str, control->type), control->type);
>  		printf("\t\tController: %u\n", control->controller);
>  
>  		if (context->bdb->version < 234)

-- 
Jani Nikula, Intel

  reply	other threads:[~2025-09-30  8:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-29 19:21 [PATCH i-g-t 0/6] tools/intel_vbt_decode: Improve decoding to strings Ville Syrjala
2025-09-29 19:21 ` [PATCH i-g-t 1/6] tools/intel_vbt_decode: Introduce to_str() Ville Syrjala
2025-09-30 12:47   ` Kamil Konieczny
2025-09-29 19:21 ` [PATCH i-g-t 2/6] tools/intel_vbt_decode: Use to_str() more Ville Syrjala
2025-09-29 19:21 ` [PATCH i-g-t 3/6] tools/intel_vbt_decode: Convert eDP deocding to use to_str() Ville Syrjala
2025-09-30  8:20   ` Jani Nikula
2025-09-30  8:21   ` Jani Nikula
2025-09-29 19:21 ` [PATCH i-g-t 4/6] tools/intel_vbt_decode: Use panel_bits() Ville Syrjala
2025-09-29 19:21 ` [PATCH i-g-t 5/6] tools/intel_vbt_decode: Decode display refclk mode Ville Syrjala
2025-09-29 19:21 ` [PATCH i-g-t 6/6] tools/intel_vbt_decode: Decode the backlight control method type Ville Syrjala
2025-09-30  8:27   ` Jani Nikula [this message]
2025-09-30 11:56     ` Ville Syrjälä
2025-09-29 19:52 ` ✓ Xe.CI.BAT: success for tools/intel_vbt_decode: Improve decoding to strings (rev2) Patchwork
2025-09-29 20:09 ` ✓ i915.CI.BAT: " Patchwork
2025-09-29 21:49 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-30  1:47 ` ✓ i915.CI.Full: success " Patchwork
2025-09-30  8:27 ` [PATCH i-g-t 0/6] tools/intel_vbt_decode: Improve decoding to strings Jani Nikula
2025-10-02 17:36   ` Ville Syrjälä

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=9dd263be40ecff813e24240cfe166473c90fac0e@intel.com \
    --to=jani.nikula@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --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