On 30 Jun 03:25 PM, Russell King - ARM Linux wrote: [..] > > Right, so what I have against mainline right now in my tree is: > > * two SPI patches, which have been taken by Mark > * one long term core ARM patch adding optimised memset/memcpy IO operations > * the PMU stuff > * BMM (already published in git form) > * Vmeta (already published in git form) > * ASoC cleanup patches, which Mark took last week. > > What isn't visible is the stuff which converts Armada DRM to component > support, along with the TDA998x driver (and it sounds like the TI LCDC > people may end up blocking that effort). This is necessary to convert > it to DT support. However, this depends on the component helper, and > that's where there's a blocking problem. > > I sent out a bunch of patches last week, with a request for help from > the Exynos people. So far, that has only attracted one relatively minor > comment from the iMX people. I can't move forwards with the Armada > DRM until this is sorted. Neither can I move forward with the TDA998x > driver. > I'm not sure I understand why tilcdc people are an obstacle for the component stuff, other than the lack of responsiveness. In any case, if you have some tilcdc or tda998x patches and you need help with the mainline process, feel free to ask. I've been doing some tilcdc work lately, and I'd be happy to help you with that. Do you plan to change the devicetree binding? While the current one works fine, it has several deficiencies, and it would be great to sort them out before the whole platform becomes obsolete. Really, if you need help and if you think I can handle it, just drop me a line and I'll see what I can do. -- Ezequiel García, Free Electrons Embedded Linux, Kernel and Android Engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
