On 24.11.2012 21:04, Thierry Reding wrote: >>> I would really like this to be phased in in more manageable chunks. For >>> instance syncpoints could be added on top of the existing host1x >>> infrastructure (the display controllers can make use of it for VBLANK >>> reporting, right?), followed by channel support for command submission. I staged nvhost into 4 patches that each add some functionality: * Add driver with API to read and increment sync point values * Add syncpt wait and interrupt infrastructure * Add channel and client support and related infrastructure (jobs, memmgr) * Add debug support I hope that helps in reviews. > I'm all for reusing your code. My concern is that the structure of this > is quite different from what can be found in the L4T downstream kernels > and therefore some rethinking may be required. As long as I can keep nvhost as a separate entity, I can port changes from upstream to downstream and vice versa and there's no architectural reason why we couldn't gradually move in downstream kernel to using tegradrm. If we merge host1x management code to tegradrm, there's no logical way of taking tegradrm into use in downstream. Terje -- 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
