Re: [Mesa-dev] [PATCH 3/3] clover: Query drivers for max clock frequency

Bruno Jiménez writes: > From: Tom Stellard > > v2: PIPE_COMPUTE_CAP_MAX_CLOCK_FREQUENCY instead of > PIPE_COMPUTE_MAX_CLOCK_FREQUENCY > > Signed-off-by: Igor Gnatenko > > clover: Correct the returned value for max_clock_frequency > > According to OpenCL 1.1 spec, the returned value must be

[Mesa-dev] [PATCH 3/3] clover: Query drivers for max clock frequency

From: Tom Stellard v2: PIPE_COMPUTE_CAP_MAX_CLOCK_FREQUENCY instead of PIPE_COMPUTE_MAX_CLOCK_FREQUENCY Signed-off-by: Igor Gnatenko clover: Correct the returned value for max_clock_frequency According to OpenCL 1.1 spec, the returned value must be in MHz, and we were returning it in kHz

[Mesa-dev] [PATCH 3/3] clover: Query drivers for max clock frequency

From: Tom Stellard v2: PIPE_COMPUTE_CAP_MAX_CLOCK_FREQUENCY instead of PIPE_COMPUTE_MAX_CLOCK_FREQUENCY Signed-off-by: Igor Gnatenko clover: Correct the returned value for max_clock_frequency According to OpenCL 1.1 spec, the returned value must be in MHz, and we were returning it in kHz