drm/asahi: initdata: Fudge t3 calculation a bit

This gives exact numbers for G14D on the test machine. It looks like
a rounding thing, but it's not clear exactly what the original logic
would be here... I'm guessing the macOS driver uses floats and a
different order of operations and that's why it comes up with a
different result sometimes.

Also fix an incorrectly named variable.

Signed-off-by: Asahi Lina <[email protected]>

Author: hoshinolina

drivers/gpu/drm/asahi/initdata.rs

@@ -124,18 +124,18 @@ impl<'a> InitDataBuilder::ver<'a> {
                         continue;
                     }
 
-                    let f_mhz = (ps.freq_hz / 1000) as u64;
+                    let f_khz = (ps.freq_hz / 1000) as u64;
                     let v_max = ps.max_volt_mv() as u64;
 
                     t1.try_push(
-                        (1000000000 * (curve_cfg.t1_coef as u64) / (f_mhz * v_max))
+                        (1000000000 * (curve_cfg.t1_coef as u64) / (f_khz * v_max))
                             .try_into()
                             .unwrap(),
                     )?;
 
                     for (j, scale) in curve_cfg.t3_scales.iter().enumerate() {
                         t3[j].try_push(
-                            (t3_coef as u64 * 1000000000 * *scale as u64 / (f_mhz * v_max * 6))
+                            (t3_coef as u64 * 1000000100 * *scale as u64 / (f_khz * v_max * 6))
                                 .try_into()
                                 .unwrap(),
                         )?;