From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: UHD 620: How to debug a screen resolution that does not work reliably
Date: Mon, 30 Apr 2018 13:37:34 +0300 [thread overview]
Message-ID: <87a7tl9dzl.fsf@intel.com> (raw)
In-Reply-To: <CAPybu_0bLB3cKydBOKgh=1x6e_+EUtjQfvtroQo1yqbNjSE8Pg@mail.gmail.com>
On Mon, 23 Apr 2018, Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com> wrote:
> Hi
>
> I have a secondary monitor connected via USB-C adapter to HDMI. It
> can manage resolutions up to 2560x1440.
>
> Most of the time, when the system is booted the resolution is detected
> ok, but If I suspend the machine, or replug the screen, or alternate
> to the text console, the resolution is "downgraded" to Full HD.
>
> I have added the paramter drm.debug=0x06 to my kernel option and I
> have managed to catch this error when the resolution is not detected
> properly:
>
> [ 4.941022] [drm:drm_mode_debug_printmodeline [drm]] Modeline
> 77:"2560x1440" 60 241500 2560 2608 2640 2720 1440 1443 1448 1481 0x48
> 0x5
> [ 4.941046] [drm:drm_mode_prune_invalid [drm]] Not using 2560x1440
> mode: CLOCK_HIGH
>
>
> On the other hand, when it works fine:
>
> [ 95.361838] [drm:drm_mode_debug_printmodeline [drm]] Modeline
> 85:"2560x1440" 60 241500 2560 2608 2640 2720 1440 1443 1448 1481 0x48
> 0x5
> [ 95.928536] [drm:intel_dump_pipe_config [i915]] crtc timings:
> 241500 2560 2608 2640 2720 1440 1443 1448 1481, type: 0x48 flags: 0x5
> [ 95.928546] [drm:intel_dump_pipe_config [i915]] port clock: 540000,
> pipe src size: 2560x1440, pixel rate 241500
>
>
> The adapter is brand new (Xiaomi) and the cable should be of good
> quality (ethernet capable).
>
>
> Any ideas about how to debug this? The EDID seems fine, it seems
> related to hock clock_high is calculated.
CLOCK_HIGH is just a consequence of the link being downgraded, there's
not enough bandwidth in the link for the mode.
You have a bug open at freedesktop.org [1], please let's keep the
discussion in one place.
BR,
Jani.
[1] https://bugs.freedesktop.org/show_bug.cgi?id=106223
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-04-30 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 21:56 UHD 620: How to debug a screen resolution that does not work reliably Ricardo Ribalda Delgado
2018-04-30 10:37 ` 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=87a7tl9dzl.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ricardo.ribalda@gmail.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