Hans Verkuil wrote: > Hi Mauro, > > Currently drivers/media/video is a mix of subdev drivers and bridge/platform > drivers. I think it would be good to create a drivers/media/subdev directory > where subdev drivers can go. > > We discussed in the past whether we should have categories for audio subdevs, > video subdevs, etc. but I think that will cause problems, especially with > future multifunction devices. Due to the discussions we had on the last time, I'm not so sure that such move would be good: There are some cases where the division of a subdev is more a matter of a logical organization than a physical device division. for example, cx231xx is just one chip, but, as it has internally the same functionalities as a cx2584x, the cx2584x is a subdev used by the driver. There are other similar examples on other IC's and SoC. I remember that Oliver argued on that time that the better would be to reduce the number of subdirs, instead of increasing. On that discussions, I got convinced that he was right, but maybe we have some new reasons to create a subdev dir. So, let's get some feedback from developers about this again. Whatever decided, we should clearly document the used criteria, to avoid having drivers misplaced. Ah, as we're talking about drivers directory, I'm intending to move the Remote Controller common code to another place, likely drivers/input/rc or drivers/rc. The idea is to use this subsystem for pure input devices as well. By keeping it at drivers/media, it will be missplaced. > What is your opinion on this, and what would be a good time to start moving > drivers? If we're doing this change, I prefer to generate the patch by the end of a merge window, after merging from everybody else and being sure that trivial patches also got merged. Comments? -- Cheers, Mauro -- 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
