Guys I think you guys might be overthniking things here. I know you have some sort of upstream/downstream split, but really in the upstream kernel, we don't care about that, so don't make it our problem. There is no need for any sort of stable API between host1x and the sub drivers, we change APIs in the kernel the whole time it isn't a problem. If you need to change the API, submit a single patch changing it across all the drivers in the tree, collecting Acks or not as needed. We do this the whole time, I've never had or seen a problem with it. We don't do separate subsystems APIs set in stone bullshit, and all subsystem maintainers are used to dealing with these sort of issues. You get an ack from one maintainer and the other one sticks it in his tree with a note to Linus. You can put the code where you want, maybe just under drivers/gpu instead of drivers/video or drivers/gpu/drm, just make sure you have a path for it into the kernel. And I have an non-upstream precedent for v4l sitting on drm, some radeon GPUs have capture tuners, and the only way to implement that would be to stick a v4l driver in the radeon drm driver. Not a problem, just never finished writing the code. Dave. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
