mn88472: reduce firmware download chunk size
Subsystems (2)
RFC PATCH 1/1 mn88472: reduce firmware download chunk size
It seems that currently the firmware download on the mn88472 is somehow wrong for my Astrometa HD-901T2.
Reducing the download chunk size (mn88472_config.i2c_wr_max) to 2 makes the firmware download consistently succeed.
Any larger value causes the download to always fail:
[ 7.671482] mn88472 7-0018: downloading firmware from file 'dvb-demod-mn88472-02.fw' [ 8.206960] mn88472 7-0018: firmware download failed=-32 [ 8.208610] rtl2832 7-0010: i2c reg write failed -32 [ 8.208620] r820t 8-003a: r820t_write: i2c wr failed=-32 reg=05 len=1: 83 [ 8.210459] rtl2832 7-0010: i2c reg write failed -32 [ 8.212038] rtl2832 7-0010: i2c reg write failed -32
I'm obviously not too happy about this patch as it slows down the firmware download but I have not found a way to keep larger chunks in place and have a working firmware download at the same time.
--- drivers/media/usb/dvb-usb-v2/rtl28xxu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/media/usb/dvb-usb-v2/rtl28xxu.c +1 -1
@@ -865,7 +865,7 @@ static int rtl2832u_frontend_attach(struct dvb_usb_adapter *adap)struct mn88472_config mn88472_config = {}; mn88472_config.fe = &adap->fe[1 ]; - mn88472_config.i2c_wr_max =22 , + mn88472_config.i2c_wr_max =2 ,strlcpy (info.type,"mn88472" ,I2C_NAME_SIZE ); mn88472_config.xtal =20500000 ; info.addr =0x18 ;
Signature · 1 line
2.0.5
Quoted 6 lines · Antti Seppälä
It seems that currently the firmware download on the mn88472 is somehow wrong for my Astrometa HD-901T2.
Reducing the download chunk size (mn88472_config.i2c_wr_max) to 2 makes the firmware download consistently succeed.
Hi, try adding the workaround patch I sent for this.
[PATCH 1/3] rtl28xxu: lower the rc poll time to mitigate i2c transfer errors
I now see that it hasn't been merged. But I have been running with this patch for a few months now without any major issues.
MvH
Benjamin Larsson
Quoted 10 lines · Benjamin Larsson
Quoted 7 lines · Antti Seppälä
It seems that currently the firmware download on the mn88472 is somehow wrong for my Astrometa HD-901T2.
Reducing the download chunk size (mn88472_config.i2c_wr_max) to 2 makes the firmware download consistently succeed.
Quoted 7 lines
Hi, try adding the workaround patch I sent for this.
[PATCH 1/3] rtl28xxu: lower the rc poll time to mitigate i2c transfer errors
I now see that it hasn't been merged. But I have been running with this patch for a few months now without any major issues.
The patch really did improve firmware loading. Weird...
Even with it I still get occasional i2c errors from r820t:
[ 15.874402] r820t 8-003a: r820t_write: i2c wr failed=-32 reg=0a len=1: da [ 81.455517] r820t 8-003a: r820t_read: i2c rd failed=-32 reg=00 len=4: 69 74 e6 df [ 99.949702] r820t 8-003a: r820t_read: i2c rd failed=-32 reg=00
len=4: 69 74 e6 df
These errors seem to appear more often if I'm reading the signal strength values using e.g. femon.
Br,
-Antti
Quoted 27 lines · Antti Seppälä
Quoted 10 lines · Benjamin Larsson
Quoted 7 lines · Antti Seppälä
It seems that currently the firmware download on the mn88472 is somehow wrong for my Astrometa HD-901T2.
Reducing the download chunk size (mn88472_config.i2c_wr_max) to 2 makes the firmware download consistently succeed.
Quoted 7 lines
Hi, try adding the workaround patch I sent for this.
[PATCH 1/3] rtl28xxu: lower the rc poll time to mitigate i2c transfer errors
I now see that it hasn't been merged. But I have been running with this patch for a few months now without any major issues.
The patch really did improve firmware loading. Weird...
Even with it I still get occasional i2c errors from r820t:
[ 15.874402] r820t 8-003a: r820t_write: i2c wr failed=-32 reg=0a len=1: da [ 81.455517] r820t 8-003a: r820t_read: i2c rd failed=-32 reg=00 len=4: 69 74 e6 df [ 99.949702] r820t 8-003a: r820t_read: i2c rd failed=-32 reg=00
Quoted 8 lines
len=4: 69 74 e6 df
These errors seem to appear more often if I'm reading the signal strength values using e.g. femon.
Br,
-Antti
This patch implements a retry logic. If a transfer fails it will convert it to 1 byte transfers. This will not work when loading the nm88472 firmware as everything is loaded through the 0xf6 register.
I think we might need something like this to get the Astrometa working reliably.
Based on usb logs from the windows driver one can see that they only send 1 byte at a time so they can retry all transfers. So this issue seems to be related to the rtl2832p bridge chip and how much i2c traffic is generated.
MvH
Benjamin Larsson
Quoted 1 line
From
5962cf8fafdfe98138fd69beb4d0b5d2a7af5732Mon Sep 17 00:00:00 2001
From: Benjamin Larsson <[email protected]>
Date: Thu, 20 Nov 2014 00:50:02 +0100
Subject: [PATCH] rtl28xxu: implement i2c transfer retry logic
Cc: Linux Media Mailing List <[email protected]>
This is needed for Astrometa hardware. Retry counts up to 6 has been observered before the i2c transfer succeded.
--- drivers/media/usb/dvb-usb-v2/rtl28xxu.c | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+)
drivers/media/usb/dvb-usb-v2/rtl28xxu.c +29 -0
@@ -185,6 +185,8 @@ static int rtl28xxu_i2c_xfer(struct i2c_adapter *adap, struct i2c_msg msg[],struct dvb_usb_device *d =i2c_get_adapdata (adap);struct rtl28xxu_priv *priv = d->priv;struct rtl28xxu_req req; +u8 rb_buf[2 ]; +int i, retry_cnt;/* * It is not known which are real I2C bus xfer limits, but testing
@@ -273,6 +275,33 @@ static int rtl28xxu_i2c_xfer(struct i2c_adapter *adap, struct i2c_msg msg[], req.size = msg[0 ].len-1 ; req.data = &msg[0 ].buf[1 ]; ret =rtl28xxu_ctrl_msg (d, &req); + +/* Astrometa hardware needs a retry for some failed transfers. +* Just send one byte at the time. +* Retry max 10 times for each transfer. +*/ +if (ret) { + req.size =1 ; + req.data = rb_buf; + +dev_dbg (&d->udev->dev,"%s: transfer of %d bytes failed\n" , __func__, msg[0 ].len-1 ); + rb_buf[0 ] = msg[0 ].buf[0 ]; + +for (i=0 ; i<msg[0 ].len-1 ; i++) { + retry_cnt =0 ; + req.value = ((msg[0 ].buf[0 ]+i) <<8 ) | (msg[0 ].addr <<1 ); + rb_buf[0 ] = msg[0 ].buf[i+1 ]; + +do { +dev_dbg (&d->udev->dev,"%s: byte: %d retry: %d\n" , __func__, i, retry_cnt); + ret =rtl28xxu_ctrl_msg (d, &req); + retry_cnt++; +if (retry_cnt >10 ) + goto err_mutex_unlock; + + }while (ret); + } + } }else {/* method 3 - new I2C */ req.value = (msg[0 ].addr <<1 );
Signature · 1 line
1.9.1
Quoted 23 lines · Antti Seppälä
Quoted 10 lines · Benjamin Larsson
Quoted 7 lines · Antti Seppälä
It seems that currently the firmware download on the mn88472 is somehow wrong for my Astrometa HD-901T2.
Reducing the download chunk size (mn88472_config.i2c_wr_max) to 2 makes the firmware download consistently succeed.
Quoted 7 lines
Hi, try adding the workaround patch I sent for this.
[PATCH 1/3] rtl28xxu: lower the rc poll time to mitigate i2c transfer errors
I now see that it hasn't been merged. But I have been running with this patch for a few months now without any major issues.
The patch really did improve firmware loading. Weird...
Even with it I still get occasional i2c errors from r820t:
Quoted 8 lines
[ 15.874402] r820t 8-003a: r820t_write: i2c wr failed=-32 reg=0a len=1: da [ 81.455517] r820t 8-003a: r820t_read: i2c rd failed=-32 reg=00 len=4: 69 74 e6 df [ 99.949702] r820t 8-003a: r820t_read: i2c rd failed=-32 reg=00len=4: 69 74 e6 df
These errors seem to appear more often if I'm reading the signal strength values using e.g. femon.
Could you disable whole IR polling and test
modprobe dvb_usb_v2 disable_rc_polling=1
It is funny that *increasing* RC polling makes things better, though...
regards
Antti
Signature · 1 line
http://palosaari.fi/
Quoted 38 lines · Antti Palosaari
Quoted 35 lines · Antti Seppälä
Quoted 12 lines · Benjamin Larsson
Quoted 8 lines · Antti Seppälä
It seems that currently the firmware download on the mn88472 is somehow wrong for my Astrometa HD-901T2.
Reducing the download chunk size (mn88472_config.i2c_wr_max) to 2 makes the firmware download consistently succeed.
Quoted 8 lines
Hi, try adding the workaround patch I sent for this.
[PATCH 1/3] rtl28xxu: lower the rc poll time to mitigate i2c transfer errors
I now see that it hasn't been merged. But I have been running with this patch for a few months now without any major issues.
The patch really did improve firmware loading. Weird...
Even with it I still get occasional i2c errors from r820t:
[ 15.874402] r820t 8-003a: r820t_write: i2c wr failed=-32 reg=0a len=1: da [ 81.455517] r820t 8-003a: r820t_read: i2c rd failed=-32 reg=00 len=4: 69 74 e6 df [ 99.949702] r820t 8-003a: r820t_read: i2c rd failed=-32 reg=00len=4: 69 74 e6 df
Quoted 9 lines
Quoted 2 lines
These errors seem to appear more often if I'm reading the signal strength values using e.g. femon.
Could you disable whole IR polling and test
modprobedvb_usb_v2disable_rc_polling=1It is funny that *increasing* RC polling makes things better, though...
Hi.
I tried loading the driver with polling disabled and it fails completely:
[ 5526.693563] mn88472 7-0018: downloading firmware from file 'dvb-demod-mn88472-02.fw' [ 5527.032209] mn88472 7-0018: firmware download failed=-32 [ 5527.033864] rtl2832 7-0010: i2c reg write failed -32 [ 5527.033874] r820t 8-003a: r820t_write: i2c wr failed=-32 reg=05 len=1: 83 [ 5527.036014] rtl2832 7-0010: i2c reg write failed -32
I have no idea why the device behaves so counter-intuitively. Is there maybe some sorf of internal power-save mode the device enters when there is no i2c traffic for a while or something?
-Antti
Quoted 57 lines · Antti Seppälä
Quoted 35 lines · Antti Palosaari
Quoted 34 lines · Antti Seppälä
Quoted 12 lines · Benjamin Larsson
Quoted 8 lines · Antti Seppälä
It seems that currently the firmware download on the mn88472 is somehow wrong for my Astrometa HD-901T2.
Reducing the download chunk size (mn88472_config.i2c_wr_max) to 2 makes the firmware download consistently succeed.
Quoted 8 lines
Hi, try adding the workaround patch I sent for this.
[PATCH 1/3] rtl28xxu: lower the rc poll time to mitigate i2c transfer errors
I now see that it hasn't been merged. But I have been running with this patch for a few months now without any major issues.
The patch really did improve firmware loading. Weird...
Even with it I still get occasional i2c errors from r820t:
[ 15.874402] r820t 8-003a: r820t_write: i2c wr failed=-32 reg=0a len=1: da [ 81.455517] r820t 8-003a: r820t_read: i2c rd failed=-32 reg=00 len=4: 69 74 e6 df [ 99.949702] r820t 8-003a: r820t_read: i2c rd failed=-32 reg=00len=4: 69 74 e6 df
Quoted 9 lines
Quoted 2 lines
These errors seem to appear more often if I'm reading the signal strength values using e.g. femon.
Could you disable whole IR polling and test
modprobedvb_usb_v2disable_rc_polling=1It is funny that *increasing* RC polling makes things better, though...
Hi.
I tried loading the driver with polling disabled and it fails completely:
[ 5526.693563] mn88472 7-0018: downloading firmware from file 'dvb-demod-mn88472-02.fw' [ 5527.032209] mn88472 7-0018: firmware download failed=-32 [ 5527.033864] rtl2832 7-0010: i2c reg write failed -32 [ 5527.033874] r820t 8-003a: r820t_write: i2c wr failed=-32 reg=05 len=1: 83 [ 5527.036014] rtl2832 7-0010: i2c reg write failed -32
Quoted 3 lines
I have no idea why the device behaves so counter-intuitively. Is there maybe some sorf of internal power-save mode the device enters when there is no i2c traffic for a while or something?
IR polling does not use I2C but some own commands. Could you make more tests. Use rtl28xxu module parameter to disable IR and test. It will disable both IR interrupts and polling. Then make some tests with different IR polling intervals to see how it behaves.
I have 3 mn88472 and 1 mn88473 device and all those seems to work fine for me. I don't care to buy anymore devices to find out one which does not work. Somehow root of cause should be find - it is not proper fix to repeat or break I2C messages to multiple smaller ones.
Antti
Signature · 1 line
http://palosaari.fi/
Quoted 20 lines
Quoted 10 lines
I tried loading the driver with polling disabled and it fails completely:
[ 5526.693563] mn88472 7-0018: downloading firmware from file 'dvb-demod-mn88472-02.fw' [ 5527.032209] mn88472 7-0018: firmware download failed=-32 [ 5527.033864] rtl2832 7-0010: i2c reg write failed -32 [ 5527.033874] r820t 8-003a: r820t_write: i2c wr failed=-32 reg=05 len=1: 83 [ 5527.036014] rtl2832 7-0010: i2c reg write failed -32Quoted 3 lines
I have no idea why the device behaves so counter-intuitively. Is there maybe some sorf of internal power-save mode the device enters when there is no i2c traffic for a while or something?
IR polling does not use I2C but some own commands. Could you make more tests. Use rtl28xxu module parameter to disable IR and test. It will disable both IR interrupts and polling. Then make some tests with different IR polling intervals to see how it behaves.
Quoted 4 lines
I have 3 mn88472 and 1 mn88473 device and all those seems to work fine for me. I don't care to buy anymore devices to find out one which does not work. Somehow root of cause should be find - it is not proper fix to repeat or break I2C messages to multiple smaller ones.
Ack.
Its the job of the I2C controller to manage the I2C bus implementation, including any fragmentation needs, not the tuner/demod/other driver.
Find and fix the resource contention bug in the bridge and the mn88472 will work as is. I suspect something is broken with I2C locking.
Signature · 2 lines
Steven Toth - Kernel Labs http://www.kernellabs.com
Quoted 25 lines · Steven Toth
Quoted 20 lines
Quoted 10 lines
I tried loading the driver with polling disabled and it fails completely:
[ 5526.693563] mn88472 7-0018: downloading firmware from file 'dvb-demod-mn88472-02.fw' [ 5527.032209] mn88472 7-0018: firmware download failed=-32 [ 5527.033864] rtl2832 7-0010: i2c reg write failed -32 [ 5527.033874] r820t 8-003a: r820t_write: i2c wr failed=-32 reg=05 len=1: 83 [ 5527.036014] rtl2832 7-0010: i2c reg write failed -32Quoted 3 lines
I have no idea why the device behaves so counter-intuitively. Is there maybe some sorf of internal power-save mode the device enters when there is no i2c traffic for a while or something?
IR polling does not use I2C but some own commands. Could you make more tests. Use rtl28xxu module parameter to disable IR and test. It will disable both IR interrupts and polling. Then make some tests with different IR polling intervals to see how it behaves.
Quoted 4 lines
I have 3 mn88472 and 1 mn88473 device and all those seems to work fine for me. I don't care to buy anymore devices to find out one which does not work. Somehow root of cause should be find - it is not proper fix to repeat or break I2C messages to multiple smaller ones.
Quoted 8 lines
Ack.
Its the job of the I2C controller to manage the I2C bus implementation, including any fragmentation needs, not the tuner/demod/other driver.
Find and fix the resource contention bug in the bridge and the mn88472 will work as is. I suspect something is broken with I2C locking.
It uses i2c control messages - single message per single operation.
You will need lock "control message" when it is done using multiple messages, very typically two bulk message one for request and one for reply - but that's not the case. Anyhow, it is possible firmware rtl2832u firmware does not like some "large (larger than single message)" operation is interrupted...
regards
Antti
Signature · 1 line
http://palosaari.fi/
Quoted 71 lines · Antti Palosaari
Quoted 65 lines · Antti Seppälä
Quoted 45 lines · Antti Palosaari
Quoted 36 lines · Antti Seppälä
Quoted 14 lines · Benjamin Larsson
Quoted 9 lines · Antti Seppälä
It seems that currently the firmware download on the mn88472 is somehow wrong for my Astrometa HD-901T2.
Reducing the download chunk size (mn88472_config.i2c_wr_max) to 2 makes the firmware download consistently succeed.
Quoted 8 lines
Hi, try adding the workaround patch I sent for this.
[PATCH 1/3] rtl28xxu: lower the rc poll time to mitigate i2c transfer errors
I now see that it hasn't been merged. But I have been running with this patch for a few months now without any major issues.
The patch really did improve firmware loading. Weird...
Even with it I still get occasional i2c errors from r820t:
[ 15.874402] r820t 8-003a: r820t_write: i2c wr failed=-32 reg=0a len=1: da [ 81.455517] r820t 8-003a: r820t_read: i2c rd failed=-32 reg=00 len=4: 69 74 e6 df [ 99.949702] r820t 8-003a: r820t_read: i2c rd failed=-32 reg=00Quoted 4 lines
len=4: 69 74 e6 df
These errors seem to appear more often if I'm reading the signal strength values using e.g. femon.
Quoted 5 lines
Could you disable whole IR polling and test
modprobedvb_usb_v2disable_rc_polling=1It is funny that *increasing* RC polling makes things better, though...
Hi.
I tried loading the driver with polling disabled and it fails completely:
[ 5526.693563] mn88472 7-0018: downloading firmware from file 'dvb-demod-mn88472-02.fw' [ 5527.032209] mn88472 7-0018: firmware download failed=-32 [ 5527.033864] rtl2832 7-0010: i2c reg write failed -32 [ 5527.033874] r820t 8-003a: r820t_write: i2c wr failed=-32 reg=05 len=1: 83 [ 5527.036014] rtl2832 7-0010: i2c reg write failed -32Quoted 3 lines
I have no idea why the device behaves so counter-intuitively. Is there maybe some sorf of internal power-save mode the device enters when there is no i2c traffic for a while or something?
Quoted 5 lines
IR polling does not use I2C but some own commands. Could you make more tests. Use rtl28xxu module parameter to disable IR and test. It will disable both IR interrupts and polling. Then make some tests with different IR polling intervals to see how it behaves.
Hi Antti.
I made some further tests for you. Here are the results:
dvb_usb_v2 disable_rc_polling=1: firmware download FAILED
dvb_usb_rtl28xxu disable_rc=1: firmware download FAILED
Then I restored the module parameters to default values and tested with various rc->interval values:
interval = 800: firmware download FAILED
interval = 600: firmware download FAILED
interval = 400: firmware download FAILED
interval = 300: firmware download SUCCESS but I2C errors from tuner could be sometimes observed
interval = 200: firmware download SUCCESS
interval = 100: firmware download SUCCESS
So somehow higher rc polling rate makes the firmware download succeed. This could indeed be some locking/timing related bug.
Please let me know if there is something else I can test.
-Antti
Quoted 97 lines · Antti Seppälä
Quoted 71 lines · Antti Palosaari
Quoted 65 lines · Antti Seppälä
Quoted 45 lines · Antti Palosaari
Quoted 36 lines · Antti Seppälä
Quoted 14 lines · Benjamin Larsson
Quoted 9 lines · Antti Seppälä
It seems that currently the firmware download on the mn88472 is somehow wrong for my Astrometa HD-901T2.
Reducing the download chunk size (mn88472_config.i2c_wr_max) to 2 makes the firmware download consistently succeed.
Quoted 8 lines
Hi, try adding the workaround patch I sent for this.
[PATCH 1/3] rtl28xxu: lower the rc poll time to mitigate i2c transfer errors
I now see that it hasn't been merged. But I have been running with this patch for a few months now without any major issues.
The patch really did improve firmware loading. Weird...
Even with it I still get occasional i2c errors from r820t:
[ 15.874402] r820t 8-003a: r820t_write: i2c wr failed=-32 reg=0a len=1: da [ 81.455517] r820t 8-003a: r820t_read: i2c rd failed=-32 reg=00 len=4: 69 74 e6 df [ 99.949702] r820t 8-003a: r820t_read: i2c rd failed=-32 reg=00Quoted 4 lines
len=4: 69 74 e6 df
These errors seem to appear more often if I'm reading the signal strength values using e.g. femon.
Quoted 5 lines
Could you disable whole IR polling and test
modprobedvb_usb_v2disable_rc_polling=1It is funny that *increasing* RC polling makes things better, though...
Hi.
I tried loading the driver with polling disabled and it fails completely:
[ 5526.693563] mn88472 7-0018: downloading firmware from file 'dvb-demod-mn88472-02.fw' [ 5527.032209] mn88472 7-0018: firmware download failed=-32 [ 5527.033864] rtl2832 7-0010: i2c reg write failed -32 [ 5527.033874] r820t 8-003a: r820t_write: i2c wr failed=-32 reg=05 len=1: 83 [ 5527.036014] rtl2832 7-0010: i2c reg write failed -32Quoted 3 lines
I have no idea why the device behaves so counter-intuitively. Is there maybe some sorf of internal power-save mode the device enters when there is no i2c traffic for a while or something?
Quoted 5 lines
IR polling does not use I2C but some own commands. Could you make more tests. Use rtl28xxu module parameter to disable IR and test. It will disable both IR interrupts and polling. Then make some tests with different IR polling intervals to see how it behaves.
Hi Antti.
I made some further tests for you. Here are the results:
dvb_usb_v2disable_rc_polling=1: firmware download FAILED
dvb_usb_rtl28xxudisable_rc=1: firmware download FAILEDThen I restored the module parameters to default values and tested with various
rc->intervalvalues:interval = 800: firmware download FAILED
interval = 600: firmware download FAILED
interval = 400: firmware download FAILED
interval = 300: firmware download SUCCESS but I2C errors from tuner could be sometimes observed
interval = 200: firmware download SUCCESS
interval = 100: firmware download SUCCESS
Quoted 4 lines
So somehow higher rc polling rate makes the firmware download succeed. This could indeed be some locking/timing related bug.
Please let me know if there is something else I can test.
Sure you could do. Play with I2C settings. Test few values to I2C bus speed / clock is good start. Put oscilloscope to I2C bus and look what there happens on error cases. There is also 2 different I2C commands, test if there is any difference. And so. Increasing polling interval to something between 250-300 does not sound very bad, though.
regards
Antti
Signature · 1 line
http://palosaari.fi/