On 1/25/19 3:13 AM, Koenig, Christian wrote:
> Am 24.01.19 um 18:56 schrieb Wentland, Harry:
>>
>> On 2019-01-24 12:41 p.m., Christian König wrote:
>>> Am 24.01.19 um 18:06 schrieb Nicholas Kazlauskas:
[Why]
It's useful to know the min and max vrr range for IGT testing.
[How]
>>
Am 24.01.19 um 18:56 schrieb Wentland, Harry:
>
> On 2019-01-24 12:41 p.m., Christian König wrote:
>> Am 24.01.19 um 18:06 schrieb Nicholas Kazlauskas:
>>> [Why]
>>> It's useful to know the min and max vrr range for IGT testing.
>>>
>>> [How]
>>> Expose the min and max vfreq for the connector via a
On 2019-01-24 12:41 p.m., Christian König wrote:
> Am 24.01.19 um 18:06 schrieb Nicholas Kazlauskas:
>> [Why]
>> It's useful to know the min and max vrr range for IGT testing.
>>
>> [How]
>> Expose the min and max vfreq for the connector via a debugfs file
>> on the connector, "vrr_range".
>>
>>
Am 24.01.19 um 18:06 schrieb Nicholas Kazlauskas:
[Why]
It's useful to know the min and max vrr range for IGT testing.
[How]
Expose the min and max vfreq for the connector via a debugfs file
on the connector, "vrr_range".
Example usage: cat /sys/kernel/debug/dri/0/DP-1/vrr_range
Cc: Harry Went
[Why]
It's useful to know the min and max vrr range for IGT testing.
[How]
Expose the min and max vfreq for the connector via a debugfs file
on the connector, "vrr_range".
Example usage: cat /sys/kernel/debug/dri/0/DP-1/vrr_range
Cc: Harry Wentland
Cc: Leo Li
Signed-off-by: Nicholas Kazlauskas