All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Chiou, Cooper" <cooper.chiou@intel.com>
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Update HDMI max TMDS data rate definition for VBT
Date: Wed, 10 Apr 2019 15:23:56 +0300	[thread overview]
Message-ID: <20190410122356.GI3888@intel.com> (raw)
In-Reply-To: <69CFE73827009D4C9A62632B1763143E4F55D90E@PGSMSX109.gar.corp.intel.com>

On Wed, Apr 10, 2019 at 11:32:47AM +0000, Chiou, Cooper wrote:
> Hi Ville,
> 
> 
> 
> From BSpec define, HDMI max data rate is “Bits 5-7” not Bits 4-7. And the following image is what I captured by latest VBT BMP v2.67 tool to load GLK VBT bin file and changed HDMI_MAX_TMDS_Bit_Rate field in 5.94/2.97/1.65Gbps different bit-rate.
> 
> 
> 
> A. 5.94Gbps(HDMI_MAX_DATA_RATE_PLATFORM) = 0 is correct, the “HDMI max data rate and level shift” value is 0x08 in following highlight block.
> 
> 
> 
> B. 2.97Gbps (HDMI_MAX_DATA_RATE_297) was 1 is wrong, it should be 001x xxxx. In this case, “HDMI max data rate and level shift value” is “0x28” in vbt.bin, so intel_vbt_defs.h HDMI_MAX_DATA_RATE_297=1 is wrong, so it should be 2

No. Read the struct definition:
struct child_device_config {
        u16 handle;
        u16 device_type; /* See DEVICE_TYPE_* above */

        union {
               	u8  device_id[10]; /* ascii string */
                struct {
                        u8 i2c_speed;
                        u8 dp_onboard_redriver;                 /* 158 */
                        u8 dp_ondock_redriver;                  /* 158 */
                        u8 hdmi_level_shifter_value:5;          /* 169 */
                        u8 hdmi_max_data_rate:3;                /* 204 */

That bitfield matches the spec.

-- 
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-04-10 12:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 10:07 [PATCH] drm/i915: Update HDMI max TMDS data rate definition for VBT Chiou, Cooper
2019-04-09 11:19 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-04-09 12:44 ` [PATCH] " Ville Syrjälä
2019-04-09 15:46   ` Chiou, Cooper
2019-04-09 15:57     ` Ville Syrjälä
2019-04-10 10:08       ` Chiou, Cooper
2019-04-10 10:50         ` Ville Syrjälä
2019-04-10 11:32           ` Chiou, Cooper
2019-04-10 12:23             ` Ville Syrjälä [this message]
2019-04-11  3:08               ` Chiou, Cooper
2019-04-09 15:34 ` ✓ Fi.CI.IGT: success for " Patchwork
2019-04-09 17:10 ` ✗ Fi.CI.BAT: failure for drm/i915: Update HDMI max TMDS data rate definition for VBT (rev2) Patchwork

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=20190410122356.GI3888@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=cooper.chiou@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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.