Hi Mauro, Thank you for the review. On Thu, Nov 05, 2020 at 08:19:50AM +0100, Mauro Carvalho Chehab wrote: > Hi, > > Em Wed, 7 Oct 2020 11:44:21 +0300 > Sakari Ailus <sakari.ailus@xxxxxxxxxxxxxxx> escreveu: > > > Add register definitions of the MIPI CCS 1.1 standard. > > > > The CCS driver makes extended use of device's capability registers that > > are dependent on CCS version. This involves having an in-memory data > > structure for limit and capability information, creating that data > > structure and accessing it. > > > > The register definitions as well as the definitions of this data structure > > are generated from a text file using a Perl script. Do the generation here > > and so avoid making manual, error-prone changes to the several generated > > files. > > I understand the reason behind using a perl script to parse some > text file in order to generate register's definition files, > but I can't see what's the sense of storing the perl script and > such texts together with the Kernel building system, re-generating them > every time. > > I mean: register definitions is something that it is supposed to be > stable, and nothing something that will change on every Kernel > compilation. > > How often are you expecting changes at ccs-regs.txt? When there's a new version of the standard, or a bug is found. At least. So not very often. After pushing the set to a branch in my linuxtv.org tree, I also noticed that some architectures are built by kbuild bot without Perl interpreter being present. This suggests that Perl is not currently universally required for building the kernel albeit there seems to be some PowerPC hardware (?) related driver needing it to be built. I was thinking of putting the files produced by the script into a new patch and leaving the script and the text file in the directory. The files would be rebuilt when a specific environment variable is set. This would in line with what crypto drivers are doing. -- Kind regards, Sakari Ailus
