It is needed to control the chip select pin when the st7789 display is wired together with some other SPI device on the same bus, for example if it shares the bus with SPI flash.
This required some refactoring of the code to correctly set the CS pin everywhere. Notably, this removes the public Command, Data, Tx, and Rx methods which poke into private details of the st7789 driver and are therefore best hidden in my opinion.
I've tried to avoid any behavioral changes that might lead to regressions, but considering the size of the diff there is always the possibility of a regression. I tested it on the Gopher Badge and on the PineTime.
It is needed to control the chip select pin when the st7789 display is wired together with some other SPI device on the same bus, for example if it shares the bus with SPI flash.
This required some refactoring of the code to correctly set the CS pin everywhere. Notably, this removes the public Command, Data, Tx, and Rx methods which poke into private details of the st7789 driver and are therefore best hidden in my opinion.
I've tried to avoid any behavioral changes that might lead to regressions, but considering the size of the diff there is always the possibility of a regression. I tested it on the Gopher Badge and on the PineTime.