| Who | What | When
|
|---|
| codyps | Hey folks, I'm seeing a failure in the cx231xx driver in linux 4.20.1 (and 4.20.0): https://gist.github.com/38eadb6c62f04e20e8638b826ebaa959 some patching of the kernel to figure out what's going on indicates that it's looking for PAD_SIGNAL_DV but all pads have PAD_SIGNAL_DEFAULT instead https://gist.github.com/aeb5e14e0f80c39842ff0d1ad2bf8d68
I'm not too familiar with the whole media pad stuff, is there a reference I should read to understand what's going wrong here?
| [01:15]
|
| .... (idle for 19mn) |
| There don't appear to be too many uses of PAD_SIGNAL_DV: https://gist.github.com/ff3cefa7704999e8fd576fceb258f911 , but there seems to be a mismatch between those and the drivers using v4l2_mc_create_media_graph : https://gist.github.com/jmesmon/5d78ba437495ff459f4450462c45100a
| [01:34]
|
| based on saa7134, it looks like it needs a definition for a ATV_DECODER pad, which would be marked as PAD_SIGNAL_DV. Not immediately clear why that is now required.
or maybe the CX25840 code needs to mark the pad?
| [01:40]
|
| ....... (idle for 31mn) |
| yep, appears tweaking CX25840 to mark it's pads sig_types fixes this.
| [02:14]
|
| ................................................................................................................. (idle for 9h23mn) |
| mchehab | ezequielg: ping
| [11:37]
|
| ................ (idle for 1h15mn) |
| ezequielg | mchehab: pong
| [12:52]
|
| ........................... (idle for 2h13mn) |
| *** | benjiG has left
| [15:05]
|
| .................... (idle for 1h35mn) |
| prabhakarlad has left
| [16:40]
|