diff options
| author | Mauro Carvalho Chehab <mchehab@infradead.org> | 2008-06-14 08:27:34 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@infradead.org> | 2008-06-14 08:27:34 -0300 |
| commit | 983506b534a01a91cadea8fd8369d6f00538cd0c (patch) | |
| tree | 637d557d526e0ecf64ae8cce8b258efb4315cb96 /linux/drivers/media/dvb/frontends/ves1x93.h | |
| parent | c0e05043fb3256374b9e95be3578d2ce055f76f9 (diff) | |
| download | mediapointer-dvb-s2-983506b534a01a91cadea8fd8369d6f00538cd0c.tar.gz mediapointer-dvb-s2-983506b534a01a91cadea8fd8369d6f00538cd0c.tar.bz2 | |
Improve error message at tda1004x_attach
From: Mauro Carvalho Chehab <mchehab@infradead.org>
When an error occurs at firmware loading, sometimes, tda1004x stops answering.
Instead of reporting such error, attach code were assuming that the device were
answering an invalid ID (0xff). This can be seen when enabling debug options:
tda1004x: tda1004x_read_byte: reg=0x0
tda1004x: tda1004x_read_byte: error reg=0x0, ret=-5
Now, instead of reporting an invalid ID, it will report the correct error:
tda10046: chip is not answering. Giving up.
saa7133[0]/dvb: failed to attach tda10046
saa7133[0]/dvb: frontend initialization failed
A possible improvement would be trying to reset the device.
Signed-off-by: Mauro Carvalho Chehab <mchehab@infradead.org>
Diffstat (limited to 'linux/drivers/media/dvb/frontends/ves1x93.h')
0 files changed, 0 insertions, 0 deletions