On Wed, 2019-04-03 at 18:17 +0200, Thierry Reding wrote: > On Mon, Apr 01, 2019 at 12:35:32PM +0200, Guido Günther wrote: > > v4 fixes up the DT binding example and uses a wider cc list since I > > failed to extend that when touching more files. [] > Applied, thanks. > > checkpatch does complain about the dsi_generic_write_seq() macro > definition, because it uses flow control statements, but there are > already similar macros in other drivers, so I let this slide. We may > want to eventually come up with something better and then replace these > macros for the other drivers as well. Dunno about the other drivers, but the mechanism isn't particularly nice as it separates the init identifier from the data being written. It might be better to use something like a struct for each command and a for loop for each block of commands. Also the 0xBF value used in one of the init sequence writes does not have an identifier #define in the 'Manufacturer specific Commands send via DSI' block which is odd.
