diff options
| author | Sylvain Munaut <tnt@246tNt.com> | 2012-04-01 21:32:24 +0200 |
|---|---|---|
| committer | Harald Welte <laforge@gnumonks.org> | 2012-04-02 09:05:55 +0200 |
| commit | 20487e8cb3dddcf517a570d72c57441e287bf427 (patch) | |
| tree | 8967b13482ecb9787f97005c35aecae624109a0f | |
| parent | a99f1b530e6def99c7aa1fc2880561766434325c (diff) | |
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>
| -rw-r--r-- | firmware/src/tuner_e4k.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/firmware/src/tuner_e4k.c b/firmware/src/tuner_e4k.c index 9691f9b..79e955c 100644 --- a/firmware/src/tuner_e4k.c +++ b/firmware/src/tuner_e4k.c @@ -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)); |