Age | Commit message (Collapse) | Author |
|
Otherwise the expression will be promoted to a floating point
multiplication
Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
|
|
Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
|
|
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>
|
|
Assume that the budget for those frequencies were tuned after the
reference table was created.
Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
|
|
The 5 was lost when stored in KHz.
Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
|
|
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>
|
|
Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
|