[Intel-gfx] [PATCH 2/2] Check if the bus is valid prior to discovering edid.

This adds a new function intel_drm_get_valid_edid, which attempts to detect EDID values from available devices and returns quickly in case no connection is present. We detect non-existing devices by checking the i2c_transfer status, and if it fails with the -ENXIO result, we know that the

Re: [Intel-gfx] [PATCH 2/2] Check if the bus is valid prior to discovering edid.

On Sat, Oct 8, 2011 at 19:13, Ben Widawsky b...@bwidawsk.net wrote: I think you may as well optimistically try to get the edid_data here. The problem is, in the success case you add ~10 i2c clocks because you next call drm_get_edid. If you optimistacally try to do both you should receive the

Re: [Intel-gfx] [PATCH 2/2] Check if the bus is valid prior to discovering edid.

On Fri, Oct 07, 2011 at 07:00:42PM -0300, Eugeni Dodonov wrote: This adds a new function intel_drm_get_valid_edid, which is used instead of drm_get_edid within the i915 driver. It does a similar check to the one in previous patch, but it is limited to i915 driver. The check is similar to

[Intel-gfx] [PATCH 2/2] Check if the bus is valid prior to discovering edid.

This adds a new function intel_drm_get_valid_edid, which is used instead of drm_get_edid within the i915 driver. It does a similar check to the one in previous patch, but it is limited to i915 driver. The check is similar to the first part of EDID discovery performed by the

[Intel-gfx] [PATCH 2/2] Check if the bus is valid prior to discovering edid.

From: Eugeni Dodonov eugeni.dodo...@intel.com This adds a new function intel_drm_get_valid_edid, which is used instead of drm_get_edid within the i915 driver. It does a similar check to the one in previous patch, but it is limited to i915 driver. The check is similar to the first part of EDID