On Wed, Dec 08, 2021 at 06:39:55PM +0200, Jani Nikula wrote:
On Wed, 08 Dec 2021, Lucas De Marchi wrote:
On Wed, Dec 08, 2021 at 01:05:17PM +0200, Jani Nikula wrote:
Add display/intel_display_trace.[ch] for defining display
tracepoints. The main goal is to reduce cross-includes between gem and
On Wed, 08 Dec 2021, Jani Nikula wrote:
> On Wed, 08 Dec 2021, Lucas De Marchi wrote:
>> On Wed, Dec 08, 2021 at 01:05:17PM +0200, Jani Nikula wrote:
>>>Add display/intel_display_trace.[ch] for defining display
>>>tracepoints. The main goal is to reduce cross-includes between gem and
>>>display.
On Wed, 08 Dec 2021, Lucas De Marchi wrote:
> On Wed, Dec 08, 2021 at 01:05:17PM +0200, Jani Nikula wrote:
>>Add display/intel_display_trace.[ch] for defining display
>>tracepoints. The main goal is to reduce cross-includes between gem and
>>display. It would be possible split up tracing even furt
On Wed, Dec 08, 2021 at 01:05:17PM +0200, Jani Nikula wrote:
Add display/intel_display_trace.[ch] for defining display
tracepoints. The main goal is to reduce cross-includes between gem and
display. It would be possible split up tracing even further, but that
would lead to more boilerplate.
We e
Add display/intel_display_trace.[ch] for defining display
tracepoints. The main goal is to reduce cross-includes between gem and
display. It would be possible split up tracing even further, but that
would lead to more boilerplate.
We end up having to include intel_crtc.h in a few places because it
