diff options
| author | Daniel Scheller <d.scheller@gmx.net> | 2017-06-25 07:02:22 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@s-opensource.com> | 2017-06-25 09:05:26 -0300 |
| commit | 8982735f8dd02096b75255e3c0a0df28aeaa9955 (patch) | |
| tree | e31270bfb9e69471dcd5e4d6a0a67edfddd6126b /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | media: ddbridge: dev_* logging fixup (diff) | |
| download | linux-8982735f8dd02096b75255e3c0a0df28aeaa9955.tar.gz linux-8982735f8dd02096b75255e3c0a0df28aeaa9955.zip | |
media: dvb-frontends/cxd2841er: require STATE_ACTIVE_* for agc readout
When the demod driver puts the demod into sleep or shutdown state and it's
status is then polled e.g. via "dvb-fe-tool -m", i2c errors are printed
to the kernel log. If the last delsys was DVB-T/T2:
cxd2841er: i2c wr failed=-5 addr=6c reg=00 len=1
cxd2841er: i2c rd failed=-5 addr=6c reg=26
and if it was DVB-C:
cxd2841er: i2c wr failed=-5 addr=6c reg=00 len=1
cxd2841er: i2c rd failed=-5 addr=6c reg=49
This happens when read_status unconditionally calls into the
read_signal_strength() function which triggers the read_agc_gain_*()
functions, where these registered are polled.
This isn't a critical thing since when the demod is active again, no more
such errors are logged, however this might make users suspecting defects.
Fix this by requiring STATE_ACTIVE_* in priv->state. If it isn't in any
active state, additionally set the strength scale to NOT_AVAILABLE.
Signed-off-by: Daniel Scheller <d.scheller@gmx.net>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions