igt-gpu-tools.git - DRM IGT GPU Tools

Age	Commit message (Collapse)	Author
2013-05-10	ddi_compute_wrpll: Do not use a double constant	Damien Lespiau
	Otherwise the expression will be promoted to a floating point multiplication Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
2013-05-10	ddi_compute_wrpll: Factor out a common expression	Damien Lespiau
	Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
2013-05-10	ddi_compute_wrpll: Rework the logic around r2 and n2 a bit	Damien Lespiau
	Let's not use the 2K variants of the frequencies it does not help in anything here and the explanations are hopefuly more understandable this way. On top of that, I noticed that we can just compute the desired min/max boundaries for r2 and n2, so use that instead of the two tests to discard out of range values. Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
2013-05-10	ddi_compute_wrpll: Fix the reference for 222525Khz and 296703Khz	Damien Lespiau
	Assume that the budget for those frequencies were tuned after the reference table was created. Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
2013-05-10	ddi_compute_wrpll: Fix the reference table for 37762500Hz	Damien Lespiau
	The 5 was lost when stored in KHz. Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
2013-05-10	ddi_compute_wrpll: Code the reference frequencies in Hz	Damien Lespiau
	Because the reference frequencies were stored in KHz, we've lost precision for 37762500Hz and the test is failing. Let's express the reference frequencies in Hz then. Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
2013-05-10	tools: Add a standalone tool to test the computation of r,n,p for WRPLLs	Damien Lespiau
	Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>