Hello Marek, On 12/16/2016 11:14 AM, Marek Szyprowski wrote: > Samsung Exynos SoCs and boards related bindings evolved since the initial > introduction, but initially the bindings were minimal and a bit incomplete > (they never described all the hardware modules available in the SoCs). > Since then some significant (not fully compatible) changes have been > already committed a few times (like gpio replaced by pinctrl, display ddc, > mfc reserved memory, some core clocks added to various hardware modules, > added more required nodes). > > On the other side there are no boards which have device tree embedded in > the bootloader. Device tree blob is always compiled from the kernel tree > and updated together with the kernel image. > > Thus to avoid further adding a bunch of workarounds for old/missing > bindings and allow to make cleanup of the existing code and device tree > files, lets mark Samsung Exynos SoC platform bindings as unstable. This > means that bindings can may change at any time and users should use the > dtb file compiled from the same kernel source tree as the kernel image. > > Signed-off-by: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx> > --- I completely agree with you on this. Reviewed-by: Javier Martinez Canillas <javier@xxxxxxxxxxxxxxx> -- Javier Martinez Canillas Open Source Group Samsung Research America -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
