public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Ankit Nautiyal <ankit.k.nautiyal@intel.com>,
	igt-dev@lists.freedesktop.org
Cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Subject: Re: [PATCH i-g-t] tools/intel_vbt_decode: Add decoding for eDP pipe joiner enable flag
Date: Fri, 09 Jan 2026 10:12:01 +0200	[thread overview]
Message-ID: <5abb893bfb01845524a336dc101ecd43e3adf092@intel.com> (raw)
In-Reply-To: <20260108115255.1405329-1-ankit.k.nautiyal@intel.com>

On Thu, 08 Jan 2026, Ankit Nautiyal <ankit.k.nautiyal@intel.com> wrote:
> Extend intel_vbt_decode to parse and display the VBT field that
> controls eDP Pipe Joiner enablement. This field was introduced in VBT
> version 261 and allows OEMs to specify whether the joiner feature should
> be enabled for eDP panels.
>
> Bspec:20142
> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> ---
>  tools/intel_vbt_decode.c | 4 ++++
>  tools/intel_vbt_defs.h   | 1 +
>  2 files changed, 5 insertions(+)
>
> diff --git a/tools/intel_vbt_decode.c b/tools/intel_vbt_decode.c
> index d4aada743e42..a96b936d4b8e 100644
> --- a/tools/intel_vbt_decode.c
> +++ b/tools/intel_vbt_decode.c
> @@ -2483,6 +2483,10 @@ static void dump_edp(struct context *context,
>  		if (context->bdb->version >= 251)
>  			printf("\t\teDP DSC disable: %s\n",
>  			       YESNO(panel_bool(edp->edp_dsc_disable, i)));
> +
> +		if (context->bdb->version >= 261)
> +			printf("\t\teDP Joiner Enable: %s\n",
> +			       YESNO(panel_bool(edp->joiner_enable, i)));
>  	}
>  }
>  
> diff --git a/tools/intel_vbt_defs.h b/tools/intel_vbt_defs.h
> index 6612d3a4ec49..550a9bfba868 100644
> --- a/tools/intel_vbt_defs.h
> +++ b/tools/intel_vbt_defs.h
> @@ -1090,6 +1090,7 @@ struct bdb_edp {
>  	u16 edp_dsc_disable;					/* 251+ */
>  	u16 t6_delay_support;					/* 260+ */
>  	u16 link_idle_time[16];					/* 260+ */
> +	u16 joiner_enable;					/* 261+ */

Changes to intel_vbt_defs.h *must* be just copies from the kernel, with
the commit message referencing the kernel commit. See git log of the
file in igt.

If the field doesn't exist in the kernel version yet, then please get
that merged first.


BR,
Jani.


>  } __packed;
>  
>  /*

-- 
Jani Nikula, Intel

      parent reply	other threads:[~2026-01-09  8:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08 11:52 [PATCH i-g-t] tools/intel_vbt_decode: Add decoding for eDP pipe joiner enable flag Ankit Nautiyal
2026-01-08 12:55 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-01-08 13:16 ` ✓ i915.CI.BAT: " Patchwork
2026-01-08 15:32 ` ✗ i915.CI.Full: failure " Patchwork
2026-01-08 17:01 ` ✗ Xe.CI.Full: " Patchwork
2026-01-09  8:12 ` Jani Nikula [this message]

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=5abb893bfb01845524a336dc101ecd43e3adf092@intel.com \
    --to=jani.nikula@intel.com \
    --cc=ankit.k.nautiyal@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