On Thu, Mar 29, 2012 at 2:48 AM, Chris Wilson
wrote:
> On Thu, 29 Mar 2012 02:26:36 +0800, Daniel Kurtz
> wrote:
>> The i915 is only able to generate a STOP cycle (i.e. finalize an i2c
>> transaction) during a DATA or WAIT phase. ?In other words, the
>> controller rejects a STOP requested as pa
On Thu, Mar 29, 2012 at 2:48 AM, Chris Wilson wrote:
> On Thu, 29 Mar 2012 02:26:36 +0800, Daniel Kurtz wrote:
>> The i915 is only able to generate a STOP cycle (i.e. finalize an i2c
>> transaction) during a DATA or WAIT phase. In other words, the
>> controller rejects a STOP requested as part o
The i915 is only able to generate a STOP cycle (i.e. finalize an i2c
transaction) during a DATA or WAIT phase. In other words, the
controller rejects a STOP requested as part of the first transaction in a
sequence.
Thus, for the first transaction we must always use a WAIT cycle, detect
when the d
The i915 is only able to generate a STOP cycle (i.e. finalize an i2c
transaction) during a DATA or WAIT phase. In other words, the
controller rejects a STOP requested as part of the first transaction in a
sequence.
Thus, for the first transaction we must always use a WAIT cycle, detect
when the d
On Thu, 29 Mar 2012 02:26:36 +0800, Daniel Kurtz
wrote:
> The i915 is only able to generate a STOP cycle (i.e. finalize an i2c
> transaction) during a DATA or WAIT phase. In other words, the
> controller rejects a STOP requested as part of the first transaction in a
> sequence.
The original doc
On Thu, 29 Mar 2012 02:26:36 +0800, Daniel Kurtz wrote:
> The i915 is only able to generate a STOP cycle (i.e. finalize an i2c
> transaction) during a DATA or WAIT phase. In other words, the
> controller rejects a STOP requested as part of the first transaction in a
> sequence.
The original docs
