On Thu, Aug 30, 2018 at 08:02:05PM +0200, Krzysztof Kozlowski 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, make development of new platforms easier and allow to make > cleanup of the existing code and device tree files, lets mark some > 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> > [krzk: Explicitly list unstable bindings instead of marking entire > Exynos] > Signed-off-by: Krzysztof Kozlowski <krzk@xxxxxxxxxx> > Reviewed-by: Javier Martinez Canillas <javier@xxxxxxxxxxxxxxx> > Acked-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@xxxxxxxxxxx> > Applied. Best regards, Krzysztof
