From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [REGRESSION] i915: No HDMI output with 4.4
Date: Fri, 12 Feb 2016 09:52:03 +0200 [thread overview]
Message-ID: <1059a4b341fb208959a262f8706fae87@natalenko.name> (raw)
In-Reply-To: <20160211140117.GC23290@intel.com>
Ville,
I've applied patch you've provided and did couple of replugging with
intel_reg in between. Here are the results.
I used additional VGA cable to see what actually I type in console :).
Both HDMI and VGA cables plugged: [1]
Both HDMI and VGA cables unplugged: [2]
Only HDMI cable plugged: [3]
Only VGA cable plugged: [4]
And here goes dmesg with all the stuff logged: [5]
Hope this helps.
[1] https://gist.github.com/58a0eb50dcf84e104555
[2] https://gist.github.com/7e8749a3e2cc58ea8aac
[3] https://gist.github.com/9d76930da7380634b845
[4] https://gist.github.com/c0d2e2f64242ad4f01f2
[5] https://gist.github.com/fda3b9fed3ca4d31cd20
11.02.2016 16:01, Ville Syrjälä wrote:
> OK, so the hpd interrupt does happen, and yet the live status
> supposedly
> claims that nothing is there. Port C live status definitely works here
> on my IVB, so not sure what the deal is.
>
> Can you grab intel-gpu-tools and run
> intel_reg read 0xc4000 0xc4004 0xc4008 0xc400c 0xc4030
> a couple of times after plugging the monitor in, and also run it when
> nothing is plugged in.
>
> Also you could try something like the following patch so we might
> observe the live status with a bit more detail. Though the fact that it
> doesn't seem to work for you even when the monitor was already plugged
> in is somewhat troubling:
>
> --- a/drivers/gpu/drm/i915/intel_hdmi.c
> +++ b/drivers/gpu/drm/i915/intel_hdmi.c
> @@ -1392,12 +1392,17 @@ intel_hdmi_detect(struct drm_connector
> *connector, bool force)
>
> intel_display_power_get(dev_priv, POWER_DOMAIN_GMBUS);
>
> - for (try = 0; !live_status && try < 9; try++) {
> - if (try)
> - msleep(10);
> - live_status = intel_digital_port_connected(dev_priv,
> + printk("port %c live status\n ",
> port_name(hdmi_to_dig_port(intel_hdmi)->port));
> + for (try = 0; try < 250; try++) {
> + bool status = intel_digital_port_connected(dev_priv,
> hdmi_to_dig_port(intel_hdmi));
> + live_status |= status;
> + printk("%c", status ? '#' : '_');
> + if (try % 50 == 49)
> + printk("\n ");
> + usleep_range(1000, 1000);
> }
> + printk("\n");
>
> if (!live_status)
> DRM_DEBUG_KMS("Live status not up!");
> --
> 2.4.10
>
> Oh, and if you have another cable you can try, might be a good idea to
> see if it behaves any better.
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [REGRESSION] i915: No HDMI output with 4.4
Date: Fri, 12 Feb 2016 09:52:03 +0200 [thread overview]
Message-ID: <1059a4b341fb208959a262f8706fae87@natalenko.name> (raw)
In-Reply-To: <20160211140117.GC23290@intel.com>
Ville,
I've applied patch you've provided and did couple of replugging with
intel_reg in between. Here are the results.
I used additional VGA cable to see what actually I type in console :).
Both HDMI and VGA cables plugged: [1]
Both HDMI and VGA cables unplugged: [2]
Only HDMI cable plugged: [3]
Only VGA cable plugged: [4]
And here goes dmesg with all the stuff logged: [5]
Hope this helps.
[1] https://gist.github.com/58a0eb50dcf84e104555
[2] https://gist.github.com/7e8749a3e2cc58ea8aac
[3] https://gist.github.com/9d76930da7380634b845
[4] https://gist.github.com/c0d2e2f64242ad4f01f2
[5] https://gist.github.com/fda3b9fed3ca4d31cd20
11.02.2016 16:01, Ville Syrjälä wrote:
> OK, so the hpd interrupt does happen, and yet the live status
> supposedly
> claims that nothing is there. Port C live status definitely works here
> on my IVB, so not sure what the deal is.
>
> Can you grab intel-gpu-tools and run
> intel_reg read 0xc4000 0xc4004 0xc4008 0xc400c 0xc4030
> a couple of times after plugging the monitor in, and also run it when
> nothing is plugged in.
>
> Also you could try something like the following patch so we might
> observe the live status with a bit more detail. Though the fact that it
> doesn't seem to work for you even when the monitor was already plugged
> in is somewhat troubling:
>
> --- a/drivers/gpu/drm/i915/intel_hdmi.c
> +++ b/drivers/gpu/drm/i915/intel_hdmi.c
> @@ -1392,12 +1392,17 @@ intel_hdmi_detect(struct drm_connector
> *connector, bool force)
>
> intel_display_power_get(dev_priv, POWER_DOMAIN_GMBUS);
>
> - for (try = 0; !live_status && try < 9; try++) {
> - if (try)
> - msleep(10);
> - live_status = intel_digital_port_connected(dev_priv,
> + printk("port %c live status\n ",
> port_name(hdmi_to_dig_port(intel_hdmi)->port));
> + for (try = 0; try < 250; try++) {
> + bool status = intel_digital_port_connected(dev_priv,
> hdmi_to_dig_port(intel_hdmi));
> + live_status |= status;
> + printk("%c", status ? '#' : '_');
> + if (try % 50 == 49)
> + printk("\n ");
> + usleep_range(1000, 1000);
> }
> + printk("\n");
>
> if (!live_status)
> DRM_DEBUG_KMS("Live status not up!");
> --
> 2.4.10
>
> Oh, and if you have another cable you can try, might be a good idea to
> see if it behaves any better.
>
next prev parent reply other threads:[~2016-02-12 7:52 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 10:17 [REGRESSION] i915: No HDMI output with 4.4 Oleksandr Natalenko
2016-02-09 10:11 ` Daniel Vetter
2016-02-09 10:11 ` Daniel Vetter
2016-02-09 15:56 ` Oleksandr Natalenko
2016-02-11 7:45 ` Oleksandr Natalenko
2016-02-11 7:45 ` Oleksandr Natalenko
2016-02-11 8:21 ` Daniel Vetter
2016-02-11 8:21 ` Daniel Vetter
2016-02-11 8:54 ` Oleksandr Natalenko
2016-02-11 8:54 ` Oleksandr Natalenko
2016-02-11 9:26 ` Ville Syrjälä
2016-02-11 9:26 ` Ville Syrjälä
2016-02-11 11:16 ` Oleksandr Natalenko
2016-02-11 11:16 ` Oleksandr Natalenko
2016-02-11 14:01 ` Ville Syrjälä
2016-02-12 7:52 ` Oleksandr Natalenko [this message]
2016-02-12 7:52 ` Oleksandr Natalenko
2016-02-12 23:23 ` Ville Syrjälä
2016-02-15 7:57 ` Oleksandr Natalenko
2016-02-15 7:57 ` Oleksandr Natalenko
2016-02-15 8:55 ` Oleksandr Natalenko
2016-02-15 8:55 ` Oleksandr Natalenko
2016-02-15 14:42 ` Ville Syrjälä
2016-02-15 14:42 ` Ville Syrjälä
2016-02-15 15:42 ` Daniel Vetter
2016-02-15 15:42 ` Daniel Vetter
2016-02-16 10:58 ` Oleksandr Natalenko
2016-02-16 10:58 ` Oleksandr Natalenko
2016-02-16 12:54 ` Daniel Vetter
2016-02-16 12:54 ` Daniel Vetter
2016-02-16 13:21 ` Oleksandr Natalenko
2016-02-16 13:21 ` Oleksandr Natalenko
2016-02-16 15:51 ` Oleksandr Natalenko
2016-02-16 15:51 ` Oleksandr Natalenko
2016-02-22 12:32 ` Oleksandr Natalenko
2016-02-22 12:32 ` Oleksandr Natalenko
2016-02-23 15:08 ` Ville Syrjälä
2016-02-23 15:08 ` Ville Syrjälä
2016-02-24 4:40 ` Jindal, Sonika
2016-02-24 4:40 ` Jindal, Sonika
2016-02-24 14:12 ` Oleksandr Natalenko
2016-02-24 14:12 ` Oleksandr Natalenko
2016-02-24 6:07 ` Sharma, Shashank
2016-02-29 15:13 ` Daniel Vetter
2016-02-29 15:13 ` Daniel Vetter
2016-02-29 15:16 ` Sharma, Shashank
2016-02-29 15:16 ` Sharma, Shashank
2016-02-29 15:41 ` Daniel Vetter
2016-02-29 15:41 ` Daniel Vetter
2016-02-29 15:41 ` Sharma, Shashank
2016-02-29 17:01 ` Daniel Vetter
2016-02-29 17:01 ` Daniel Vetter
2016-02-24 14:09 ` Oleksandr Natalenko
2016-02-24 14:09 ` Oleksandr Natalenko
-- strict thread matches above, loose matches on Subject: below --
2016-05-01 10:42 Alessandro Capogna
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=1059a4b341fb208959a262f8706fae87@natalenko.name \
--to=oleksandr@natalenko.name \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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 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.