On Fri, Mar 9, 2012 at 3:15 AM, Maarten Maathuis wrote:
> On Fri, Mar 9, 2012 at 2:50 AM, Yufeng Shen wrote:
>> So a simple case of disabling a CRTC and then re-enabling it.
>>
>> Disabling:
>>
>> CRTC X is originally connected to output Y
>>
>>
On Fri, Mar 9, 2012 at 3:15 AM, Maarten Maathuis
wrote:
> On Fri, Mar 9, 2012 at 2:50 AM, Yufeng Shen wrote:
>> So a simple case of ?disabling a CRTC and then re-enabling it.
>>
>> Disabling:
>>
>> CRTC X is originally connected to output Y
>>
>>
So a simple case of disabling a CRTC and then re-enabling it.
Disabling:
CRTC X is originally connected to output Y
1. XRRSetCrtcConfig()is called to disable CRTC X
2. drm_helper_connector_dpms() then gets called on the connector
connected to CRTC X,
in the function,
the connec
So a simple case of disabling a CRTC and then re-enabling it.
Disabling:
CRTC X is originally connected to output Y
1. XRRSetCrtcConfig()is called to disable CRTC X
2. drm_helper_connector_dpms() then gets called on the connector
connected to CRTC X,
in the function,
the connec
there is a race condition in using the underlying
GMBUS controller. Fixing this by adding a mutex lock when calling
gmbus_xfer().
Signed-off-by: Yufeng Shen
---
drivers/gpu/drm/i915/i915_drv.h |8
drivers/gpu/drm/i915/intel_i2c.c | 24 +---
2 files change
that
the LVDS port
, or the DDC port. But when there are I2C transactions on both LVDS
and DDC ports,
since they share the same GMBUS registers, there will be race condition.
Does this make sense to you ?
--- Yufeng Shen
On Mon, Feb 13, 2012 at 4:04 AM, Ben Widawsky wrote:
> On Fri, Feb 10, 2
there is a race condition in using the underlying
GMBUS controller. Fixing this by adding a mutex lock when calling
gmbus_xfer().
Signed-off-by: Yufeng Shen
---
drivers/gpu/drm/i915/i915_drv.h |8
drivers/gpu/drm/i915/intel_i2c.c | 24 +---
2 files change
that
the LVDS port
, or the DDC port. But when there are I2C transactions on both LVDS
and DDC ports,
since they share the same GMBUS registers, there will be race condition.
Does this make sense to you ?
--- Yufeng Shen
On Mon, Feb 13, 2012 at 4:04 AM, Ben Widawsky wrote:
> On Fri, Feb 10, 2
GMBUS has several ports and each has it's own corresponding
I2C adpater. When multiple I2C adapters call gmbus_xfer() at
the same time there is a race condition in using the underlying
GMBUS controller. Fixing this by adding a mutex lock when calling
gmbus_xfer().
Signed-off-by: Yufeng
GMBUS has several ports and each has it's own corresponding
I2C adpater. When multiple I2C adapters call gmbus_xfer() at
the same time there is a race condition in using the underlying
GMBUS controller. Fixing this by adding a mutex lock when calling
gmbus_xfer().
Signed-off-by: Yufeng
GMBUS has several ports and each has it's own corresponding
I2C adpater. When multiple I2C adapters call gmbus_xfer() at
the same time there is a race condition in using the underlying
GMBUS controller. Fixing this by adding a mutex lock when calling
gmbus_xfer().
Signed-off-by: Yufeng
GMBUS has several ports and each has it's own corresponding
I2C adpater. When multiple I2C adapters call gmbus_xfer() at
the same time there is a race condition in using the underlying
GMBUS controller. Fixing this by adding a mutex lock when calling
gmbus_xfer().
Signed-off-by: Yufeng
12 matches
Mail list logo