On 22/12/14 12:26, 유재용 wrote:
> Hello intel-gfx,
>
> I'm reading i915 gpu drivers and find myself quite hard to understand
> about forcewake concepts.
>
> I understand that it is something with the energy efficiency so related
> to ACPI. And it looks like forcewake is working as a pair (get and put).
> In the "get" part, what it first does it waiting on FORCEWAKE_ACK_HSW
> register (in case of haswell).
> And then, it writes something to FORCEWAKE_MT register, read from ECOBUS.
> And again, it waits on FORCEWAKE_ACK_HSW again!
> It becomes more confusing when it comes to put.
> In the "put" part, what it does it writing to FORCEWAKE_MT register and
> read from ECOBUS.
>
> I tried to find some good reading materials about this forcewake, but
> what I found was a series of patches in this mailing list. (which are
> quite hard to follow from the begining)
> Could you explain about the concept of FORCEWAKE and possibly the magic
> tricks on these get and put?
>
> Thanks,
> Jaeyong
Hi Jaeyong,
FORCEWAKE details vary a little from one chip to another, so this is
only a general description, but essentially setting one or more bits in
the FORCEWAKE register(s) prevents some or all of the power domains from
going into the deeper idle (sleep) states (and forces them out of the
sleep state if they're already asleep). Clearing the bit(s) allows the
affected parts to go to sleep again.
The FORCEWAKE_ACK register(s) contain one or more bits which reflect the
internal state, and so acknowledge that the most recent write to the
corresponding FORCEWAKE register has been accepted and acted upon. It
can take a while for a portion of the chip to wake up, so after setting
a FORCEWAKE bit we have to spin-wait until it's taken effect.
So, the general algorithm for accessing some part of the chip that may
be asleep is:
1) set the relevant bit of (a) FORCEWAKE register
2) poll (matching) FORCEWAKE_ACK until the write is acknowledged
3) access the chip (this can encompass several reads and writes)
4) clear the FORCEWAKE bit that we set earlier
5) poll FORCEWAKE_ACK again until this write is acknowledged
Now for extra confusion, there are a few more details:
* because reads and writes can in some cases be reordered, we
need to force the write to FORCEWAKE to complete before the
busy-polling of FORCEWAKE_ACK. This is the sole purpose of the
read of the ECOBUS register, which is used just because it
happens to lie in the same cacheline as FORCEWAKE.
* we can choose not to poll for FORCEWAKE_ACK clear in step (5).
Instead, we can just leave the chip to go back to sleep while
we get on with other things. But in that case, we might come
back and try to wake the chip again before it's finished
responding to the write in step (4). So if we don't poll at
the end of the sequence, we have to poll at the beginning
instead; in other words, move step (5) to before step (1).
IIRC, gen6 had a single FORCEWAKE register containing a single effective
bit, gen7 has a single register containing multiple bits (so that they
can be controlled by different agents) which are OR-ed together to
produce a combined wakeup signal (this also applies to HSW, although the
FORCEWAKE_ACK is in a different place from earlier chips); and VLV has
multiple registers for different power domains (e.g. MEDIA vs RENDER).
Hope this helps!
Dave
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
