On Tue, 6 Apr 2010, Hans Verkuil wrote: [...] > > One thing that might be useful is to prefix the name with the control class > name. E.g. hue becomes user_hue and audio_crc becomes mpeg_audio_crc. It would > groups them better. Or one could make a controls/user and controls/mpeg > directory. That might not be such a bad idea actually. I agree with grouping in concept, and using subdirectories is not a bad thing. Probably however you'd want to ensure that in the end all the controls end up logically at the same depth in the tree. [...] > > An in between solution would be to add _type files. So you would have > 'hue' and 'hue_type'. 'cat hue_type' would give something like: > > int 0 255 1 128 0x0000 Hue > > In other words 'type min max step flags name'. There was I thought at some point in the past a kernel policy that sysfs controls were supposed to limit themselves to one value per node. > > And for menu controls like stream_type (hmm, that would become > stream_type_type...) you would get: > > menu 0 5 1 0 Stream Type > MPEG-2 Program Stream > > MPEG-1 System Stream > MPEG-2 DVD-compatible Stream > MPEG-1 VCD-compatible Stream > MPEG-2 SVCD-compatible Stream > > Note the empty line to denote the unsupported menu item (transport stream). > > This would give the same information with just a single extra file. Still not > sure whether it is worth it though. Just remember that the more complex / subtle you make the node contents, then the more parsing will be required for any program that tries to use it. I also think it's probably a bad idea for example to define a format where the whitespace conveys additional information. The case where I've seen whitespace as part of the syntax actually work cleanly is in Python. -- Mike Isely isely @ isely (dot) net PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8 -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
