On Wed, Mar 28, 2012 at 3:02 AM, Chris Wilson
wrote:
> On Wed, 28 Mar 2012 02:36:22 +0800, Daniel Kurtz
> wrote:
>> Save the GMBUS2 value read while polling for state changes, and then
>> reuse this value when determining for which reason the loops were exited.
>> This is a small optimization w
On Wed, 28 Mar 2012 19:39:17 +0800, Daniel Kurtz
wrote:
> On Wed, Mar 28, 2012 at 3:02 AM, Chris Wilson
> wrote:
> > Might as well shave this read as well.
>
> Do you know why POSTING_READ() was there in the first place?
> As far as I can tell, these are used to ensure memory barriers are
> in
On Wed, Mar 28, 2012 at 3:02 AM, Chris Wilson wrote:
> On Wed, 28 Mar 2012 02:36:22 +0800, Daniel Kurtz wrote:
>> Save the GMBUS2 value read while polling for state changes, and then
>> reuse this value when determining for which reason the loops were exited.
>> This is a small optimization which
On Wed, 28 Mar 2012 19:39:17 +0800, Daniel Kurtz wrote:
> On Wed, Mar 28, 2012 at 3:02 AM, Chris Wilson
> wrote:
> > Might as well shave this read as well.
>
> Do you know why POSTING_READ() was there in the first place?
> As far as I can tell, these are used to ensure memory barriers are
> ins
Save the GMBUS2 value read while polling for state changes, and then
reuse this value when determining for which reason the loops were exited.
This is a small optimization which saves a couple of bus accesses for
memory mapped IO registers.
To avoid "assigning in if clause" checkpatch errors", use
Save the GMBUS2 value read while polling for state changes, and then
reuse this value when determining for which reason the loops were exited.
This is a small optimization which saves a couple of bus accesses for
memory mapped IO registers.
To avoid "assigning in if clause" checkpatch errors", use
On Wed, 28 Mar 2012 02:36:22 +0800, Daniel Kurtz
wrote:
> Save the GMBUS2 value read while polling for state changes, and then
> reuse this value when determining for which reason the loops were exited.
> This is a small optimization which saves a couple of bus accesses for
> memory mapped IO reg
On Wed, 28 Mar 2012 02:36:22 +0800, Daniel Kurtz wrote:
> Save the GMBUS2 value read while polling for state changes, and then
> reuse this value when determining for which reason the loops were exited.
> This is a small optimization which saves a couple of bus accesses for
> memory mapped IO regi
