[v2] Documentation: dt-bindings: Explicitly mark Samsung Exynos SoC bindings as unstable

Message ID 20180528191327.23772-1-krzk@kernel.org
State New
Headers show
Series
  • [v2] Documentation: dt-bindings: Explicitly mark Samsung Exynos SoC bindings as unstable
Related show

Commit Message

Krzysztof Kozlowski May 28, 2018, 7:13 p.m.
From: Marek Szyprowski <m.szyprowski@samsung.com>


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@samsung.com>

Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>


---

Changes since v1:
1. Rebase
2. Add specific compatibles to mark unstable.

v1 is here:
https://patchwork.kernel.org/patch/9477963/

Previous tags (not applying due to change in contents):
Reviewed-by: Javier Martinez Canillas <javier@osg.samsung.com>

Acked-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>

Reviewed-by: Pankaj Dubey <pankaj.dubey@samsung.com>

---
 .../devicetree/bindings/arm/samsung/exynos.txt     | 26 ++++++++++++++++++++++
 1 file changed, 26 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/arm/samsung/exynos.txt

-- 
2.14.1

--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Comments

Javier Martinez Canillas May 29, 2018, 7:06 a.m. | #1
On Mon, May 28, 2018 at 9:13 PM, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> From: Marek Szyprowski <m.szyprowski@samsung.com>

>

> 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@samsung.com>

> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>

>


Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>


Best regards,
Javier
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Patch

diff --git a/Documentation/devicetree/bindings/arm/samsung/exynos.txt b/Documentation/devicetree/bindings/arm/samsung/exynos.txt
new file mode 100644
index 000000000000..7410cb79e4b2
--- /dev/null
+++ b/Documentation/devicetree/bindings/arm/samsung/exynos.txt
@@ -0,0 +1,26 @@ 
+Samsung Exynos SoC Family Device Tree Bindings
+---------------------------------------------------------------
+
+Work in progress statement:
+
+Following Device Tree files and bindings applying to Samsung Exynos SoCs and
+boards are considered "unstable":
+
+ - samsung,exynos5433* (all compatibles related to Exynos5433)
+ - samsung,exynos7* (all compatibles related to Exynos7)
+ - samsung,tm2-audio
+ - samsung,mfc-v10
+ - samsung,exynos*-mipi-dsi
+ - samsung,exynos5-dp
+ - samsung,exynos*-hdmi
+ - samsung,exynos*-hdmiddc
+ - samsung,exynos*-hdmiphy
+ - samsung,exynos*-mixer
+ - samsung,exynos*-fimd
+
+Any Samsung Exynos device tree binding mentioned may change at any time. Be
+sure to use a device tree binary and a kernel image generated from the same
+source tree.
+
+Please refer to Documentation/devicetree/bindings/ABI.txt for a definition of a
+stable binding/ABI.