Mxconfig driver settings HUB75_I2S_CFG::DP3246_SM5368 need to be changed #815
Description
Hi @mrcodetastic
Recently I have encountered twice that HUB75_I2S_CFG::DP3246_SM5368 option did not configured correctly.
First, in #806, despite all my advice, user (@kalyan-m25) could not get a stable picture on the panel. We contacted to him by mail and he sent me a panel for tests. I found that the pixel mapping on this panel is configured and the picture is displayed correctly, but the image shakes very much and sometimes disappears completely. I assumed that the reason is that the HUB75_I2S_CFG::DP3246_SM5368 config contains not only settings for the shift-register multiplex type, but also for the DP3246 driver, which are not applicable to this panel and can interfere with the image output. I edited the code from the library and commented out all the lines related to the DP3246 driver settings - and after that I got a stable picture.
The second case is #805. The user (@tolik2025) has a panel with MBI5124 drivers and a ICN2018 multiplexer. However, with the option, his panel remained completely dark. Let's assume that the problem may be the same as in the previous case - I sent him a edited version of the library, where all the changes concerning DP3246 were commented out. After that, he was able to launch his matrix, although not quite stably yet.
My conclusions
The option HUB75_I2S_CFG::DP3246_SM5368 should be split into two - one for the DP3246 driver, and the other for the shift register type multiplexors like SM5368 chip.
It would be better if the option for the multiplexers is allocated to a separate variable inside the MXCONFIG structure, so that the properties of the matrix driver and the multiplexer could be configured independently and set one option for the drivers, and another for the multiplexer. For example, in the case of the #805, I believe it is necessary to select the HUB75_I2S_CFG::MBI5124 driver option and separately set the settings for the multiplexer of the SM5368 type.