That actually makes sense.  It came up because mmPA_SC_RASTER_CONFIG (and _1) 
are read by libdrm with a selection of 0/*/* for se/sh/instance so I wanted to 
be able to reproduce that via the debugfs interface for testing.

But ya, if you use the broadcast bit who are you reading from then ... hmm..


From: amd-gfx <> on behalf of Michel 
Dänzer <>
Sent: Monday, October 10, 2016 23:52
To: Tom St Denis
Subject: Re: [PATCH] drm/amd/amdgpu: Allow broadcast on debugfs read (v2)

On 09/10/16 08:58 PM, Tom St Denis wrote:
> Allow any of the se/sh/instance fields to be
> specified as a broadcast by submitting 0x3FF.
> (v2) Fix broadcast range checking
> Signed-off-by: Tom St Denis <>

I'm not sure how a "broadcast read" is supposed to work? I can only see
the register specs talking about broadcast in connection with writes.

Earthling Michel Dänzer               |     
Graphics, Processors and Immersive VR Solutions | AMD <>
Explore a wide range of innovative next generation computing processors, 
graphics, and Immersive VR solutions by Advanced Micro Devices (AMD). Visit now!

Libre software enthusiast             |             Mesa and X developer
amd-gfx mailing list
amd-gfx Info Page -<>
To see the collection of prior postings to the list, visit the amd-gfx 
Archives. Using amd-gfx: To post a message to all the list members, send email 

amd-gfx mailing list

Reply via email to