From patchwork Mon May 28 19:13:27 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Krzysztof Kozlowski X-Patchwork-Id: 921668 Return-Path: X-Original-To: incoming-dt@patchwork.ozlabs.org Delivered-To: patchwork-incoming-dt@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=devicetree-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: ozlabs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.b="pubF3I+O"; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 40vmkF6sZjz9s1p for ; Tue, 29 May 2018 05:14:12 +1000 (AEST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755718AbeE1TOA (ORCPT ); Mon, 28 May 2018 15:14:00 -0400 Received: from mail.kernel.org ([198.145.29.99]:34850 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755716AbeE1TOA (ORCPT ); Mon, 28 May 2018 15:14:00 -0400 Received: from localhost.localdomain (adsl-84-227-236-43.adslplus.ch [84.227.236.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 3FCDC20843; Mon, 28 May 2018 19:13:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1527534839; bh=NfMz6cGvL0g/TEOmUhS+ZmNtSVZW/415ja64umapqmQ=; h=From:To:Cc:Subject:Date:From; b=pubF3I+OmjreoZVO/Mnu2xzSdKHw+JcA8hDnbrR5jrJaxc1qK1ms6nEh7uH1Ma4qH H86cXddUtD3yQjCa+QOEx9cltErMMCntHtf2hiHwYVGIMo0Gt1PBzaAQhY/lGTMY/N Qlk7fZDDBzJZdCi3AqM7aLE4JrzkJJg0j8gySAk8= From: Krzysztof Kozlowski To: Rob Herring , Mark Rutland , Kukjin Kim , Krzysztof Kozlowski , Pankaj Dubey , Bartlomiej Zolnierkiewicz , Marek Szyprowski , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Chanwoo Choi , Seung-Woo Kim , Inki Dae , Sylwester Nawrocki , Alim Akhtar , Arnd Bergmann , Olof Johansson Subject: [PATCH v2] Documentation: dt-bindings: Explicitly mark Samsung Exynos SoC bindings as unstable Date: Mon, 28 May 2018 21:13:27 +0200 Message-Id: <20180528191327.23772-1-krzk@kernel.org> X-Mailer: git-send-email 2.14.1 Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org From: Marek Szyprowski 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 Signed-off-by: Krzysztof Kozlowski Reviewed-by: Javier Martinez Canillas Acked-by: Bartlomiej Zolnierkiewicz --- 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 Acked-by: Bartlomiej Zolnierkiewicz Reviewed-by: Pankaj Dubey --- .../devicetree/bindings/arm/samsung/exynos.txt | 26 ++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/samsung/exynos.txt 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.