[Bug 109267] [GLK DSI] Display not working with i915 driver

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Mar 13 17:02:53 UTC 2019


https://bugs.freedesktop.org/show_bug.cgi?id=109267

--- Comment #30 from Ville Syrjala <ville.syrjala at linux.intel.com> ---
-INT3453:01/pinmux-pins:pin 68 (GPIO_144): (MUX UNCLAIMED) (GPIO UNCLAIMED)
-INT3453:01/pinmux-pins:pin 69 (GPIO_145): (MUX UNCLAIMED) (GPIO UNCLAIMED)
+INT3453:01/pinmux-pins:pin 68 (GPIO_144): (MUX UNCLAIMED) INT3453:01:420
+INT3453:01/pinmux-pins:pin 69 (GPIO_145): (MUX UNCLAIMED) INT3453:01:421
-INT3453:02/pinmux-pins:pin 4 (AVS_I2S0_SDO): (MUX UNCLAIMED) (GPIO UNCLAIMED)
+INT3453:02/pinmux-pins:pin 4 (AVS_I2S0_SDO): (MUX UNCLAIMED) INT3453:02:336

When loading the driver the expected gpio pins seem to have been claimed
correctly. And the state of those is unchanged, until the xrandr off when they
do change state in the expected manner.

-INT3453:01/pins:pin 68 (GPIO_144) GPIO 0x44000201 0x00021267 0x00000100
-INT3453:01/pins:pin 69 (GPIO_145) GPIO 0x44000201 0x00021268 0x00000100
+INT3453:01/pins:pin 68 (GPIO_144) GPIO 0x44000200 0x00021267 0x00000100
+INT3453:01/pins:pin 69 (GPIO_145) GPIO 0x44000200 0x00021268 0x00000100
-INT3453:02/pins:pin 4 (AVS_I2S0_SDO) GPIO 0x44000201 0x0003d200 0x00000000
+INT3453:02/pins:pin 4 (AVS_I2S0_SDO) GPIO 0x44000200 0x0003d200 0x00000000

So unfortunately I'm not seeing anything obvious that would explain the
failure.

The only other change I see is that we manage to change the state of the DDC
pins. The BIOS/GOP has left them low for some reason, and we just pull them
high when the DDC bus is idle (which is the correct thing to do).
-INT3453:01/pins:pin 48 (HV_DDI0_DDC_SDA) mode 1 0x44000400 0x0001c353
0x00000000 [ACPI]
-INT3453:01/pins:pin 49 (HV_DDI0_DDC_SCL) mode 1 0x44000400 0x0001c354
0x00000000 [ACPI]
+INT3453:01/pins:pin 48 (HV_DDI0_DDC_SDA) mode 1 0x44000402 0x0001c353
0x00000000 [ACPI]
+INT3453:01/pins:pin 49 (HV_DDI0_DDC_SCL) mode 1 0x44000402 0x0001c354
0x00000000 [ACPI]

Just to be super sure the DDC pins aren't somehow involved we could test
something like:
diff --git a/drivers/gpu/drm/i915/intel_i2c.c
b/drivers/gpu/drm/i915/intel_i2c.c
index 5a733e711355..1423aa5d2ff7 100644
--- a/drivers/gpu/drm/i915/intel_i2c.c
+++ b/drivers/gpu/drm/i915/intel_i2c.c
@@ -703,6 +703,8 @@ gmbus_xfer(struct i2c_adapter *adapter, struct i2c_msg
*msgs, int num)
        intel_wakeref_t wakeref;
        int ret;

+       return -ENXIO;
+
        wakeref = intel_display_power_get(dev_priv, POWER_DOMAIN_GMBUS);

        if (bus->force_bit) {

Though I don't expect that to help.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190313/f23d67fb/attachment-0001.html>


More information about the intel-gfx-bugs mailing list