On Tue, Dec 13, 2016 at 05:32:07PM +0200, Mika Kuoppala wrote:
> For limiting the max frequency of gpu, the max freq tunable
> is not enough to hard limit the max gap. We now have also per
> client boost max freq. When this tunable was introduced,
> it was mistakenly made read only. Allow user to g
On Tue, Dec 13, 2016 at 05:37:42PM +0200, Jani Nikula wrote:
> On Tue, 13 Dec 2016, Mika Kuoppala wrote:
> > For limiting the max frequency of gpu, the max freq tunable
> > is not enough to hard limit the max gap. We now have also per
> > client boost max freq. When this tunable was introduced,
>
On Tue, 13 Dec 2016, Mika Kuoppala wrote:
> For limiting the max frequency of gpu, the max freq tunable
> is not enough to hard limit the max gap. We now have also per
> client boost max freq. When this tunable was introduced,
> it was mistakenly made read only. Allow user to gain control by
> set
For limiting the max frequency of gpu, the max freq tunable
is not enough to hard limit the max gap. We now have also per
client boost max freq. When this tunable was introduced,
it was mistakenly made read only. Allow user to gain control by
setting it writable.
Fixes: 29ecd78d3b79 ("drm/i915: De
