Em Mon, 21 Sep 2015 11:59:27 +0200 Andrzej Pietrasiewicz <andrzej.p@xxxxxxxxxxx> escreveu: > Hi Hans, > > W dniu 21.09.2015 o 11:50, Hans Verkuil pisze: > > On 18-09-15 16:21, Andrzej Pietrasiewicz wrote: > >> From: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx> > >> > >> Add Exynos 5433 jpeg h/w codec node. > >> > >> Signed-off-by: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx> > >> Signed-off-by: Andrzej Pietrasiewicz <andrzej.p@xxxxxxxxxxx> > >> --- > >> arch/arm64/boot/dts/exynos/exynos5433.dtsi | 21 +++++++++++++++++++++ > >> 1 file changed, 21 insertions(+) > >> > >> diff --git a/arch/arm64/boot/dts/exynos/exynos5433.dtsi b/arch/arm64/boot/dts/exynos/exynos5433.dtsi > > > > This dtsi file doesn't exist in the media-git tree. What is the story here? > > > > Should this go through a different subsystem? > > > > I think the media subsystem can take patches 1-3 and whoever does DT patches can > > take this patch, right? > > > > The cover letter explains that the series is rebased onto Mauro's > master with Kukjin's branch merged. The latter does contain > the exynos5433.dtsi. That said, yes, taking patches 1-3 in > media subsystem and leaving DT patch to someone else is the > way to go. I'm ok with such strategy, provided that the new driver builds fine with COMPILE_TEST without the need of the dtsi patch. Please also notice that, if the driver uses MC, it has to wait for the MC next gen support to be merged, and may need to be rebased, due to a few changes at the MC internal APIs: one function got renamed (the function that create links between two pads) and we're now using lists for links (that will only affect the driver if it has its own graph traversal routines). Btw, I just got a Samsung TM1 device, with seems to be using an arm64 SoC. Is this driver providing support for its camera? Regards, 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
