fw/tuner_e4k: DC offset table gen doc fixes

No we don't need to wait. I checked if the value ever changed after
the first read and it doesn't. Other e4k drivers don't wait either.

Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
This commit is contained in:
Sylvain Munaut 2012-04-01 21:32:24 +02:00 committed by Harald Welte
parent a99f1b530e
commit 20487e8cb3
1 changed files with 1 additions and 1 deletions

View File

@ -810,7 +810,6 @@ int e4k_dc_offset_gen_table(struct e4k_state *e4k)
/* perform actual calibration */
e4k_dc_offset_calibrate(e4k);
/* FIXME: do we have to wait? */
/* extract I/Q offset and range values */
offs_i = e4k_reg_read(e4k, E4K_REG_DC2) & 0x3F;
@ -820,6 +819,7 @@ int e4k_dc_offset_gen_table(struct e4k_state *e4k)
LOGP(DTUN, LOGL_DEBUG, "Table %u I=%u/%u, Q=%u/%u\n",
i, range_i, offs_i, range_q, offs_q);
/* write into the table */
e4k_reg_write(e4k, dc_gain_comb[i].reg,
TO_LUT(offs_q, range_q));