From patchwork Fri Dec 16 14:14:36 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Marek Szyprowski X-Patchwork-Id: 9477957 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id 07FD0601C2 for ; Fri, 16 Dec 2016 14:16:25 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id EEDA8288A3 for ; Fri, 16 Dec 2016 14:16:24 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id E37AA288AC; Fri, 16 Dec 2016 14:16:24 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.9 required=2.0 tests=BAYES_00,RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 0D29628898 for ; Fri, 16 Dec 2016 14:16:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760336AbcLPOQN (ORCPT ); Fri, 16 Dec 2016 09:16:13 -0500 Received: from mailout3.samsung.com ([203.254.224.33]:49062 "EHLO mailout3.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755619AbcLPOQB (ORCPT ); Fri, 16 Dec 2016 09:16:01 -0500 Received: from epcpsbgm1new.samsung.com (epcpsbgm1 [203.254.230.26]) by mailout3.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0OIA02BE57KQQ820@mailout3.samsung.com>; Fri, 16 Dec 2016 23:14:53 +0900 (KST) X-AuditID: cbfee61a-f79916d0000062de-f7-5853f6dd1d7e Received: from epmmp2 ( [203.254.227.17]) by epcpsbgm1new.samsung.com (EPCPMTA) with SMTP id F9.D4.25310.DD6F3585; Fri, 16 Dec 2016 23:14:53 +0900 (KST) Received: from AMDC2765.digital.local ([106.116.147.25]) by mmp2.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTPA id <0OIA008TS7KKSTC0@mmp2.samsung.com>; Fri, 16 Dec 2016 23:14:53 +0900 (KST) From: Marek Szyprowski To: linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org Cc: Marek Szyprowski , Rob Herring , Mark Rutland , Krzysztof Kozlowski , Bartlomiej Zolnierkiewicz , Javier Martinez Canillas , Kukjin Kim , Inki Dae , Seung-Woo Kim , Chanwoo Choi , Sylwester Nawrocki Subject: [PATCH] Documentation: dt: Explicitly mark Samsung Exynos SoC bindings as unstable Date: Fri, 16 Dec 2016 15:14:36 +0100 Message-id: <1481897676-13578-1-git-send-email-m.szyprowski@samsung.com> X-Mailer: git-send-email 1.9.1 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDLMWRmVeSWpSXmKPExsVy+t9jQd2734IjDCbdlLDYOGM9q8X1L89Z LeYfOcdqMen+BBaLN2/XMFn0P37NbHH+/AZ2i02Pr7FazDi/j8li7ZG77BZLr19ksmjde4Td 4vCbdqDE5JdsDnwea+atYfTYtKqTzWPzknqPLf132T36tqxi9Pi8SS6ALcrNJiM1MSW1SCE1 Lzk/JTMv3VYpNMRN10JJIS8xN9VWKULXNyRISaEsMacUyDMyQAMOzgHuwUr6dgluGcvO/GUq 2CNQsfXwPKYGxq+8XYycHBICJhJ/P89nhbDFJC7cW8/WxcjFISQwi1Fi87YOFgjnF6PElCub WUCq2AQMJbredgFVcXCICGRKbNySC1LDLHCeWeLevk9gNcICsRJNHx8zgdgsAqoSC1e+AtvA K+Ah8eTZNDaIbXISJ49NZp3AyL2AkWEVo0RqQXJBcVJ6rmFearlecWJucWleul5yfu4mRnDI P5PawXhwl/shRgEORiUe3gVbgiKEWBPLiitzDzFKcDArifD2fA6OEOJNSaysSi3Kjy8qzUkt PsRoCnTARGYp0eR8YDzmlcQbmpibmBsbWJhbWpoYKYnzNs5+Fi4kkJ5YkpqdmlqQWgTTx8TB KdXA6P6s/dvt5m2XMt6Xsar9jHb+Nnl/936TvX2sP5jTZj+6Gtw3K1UigaWyPK72oOyqu90L qwVfz1USrDOYUf/1dm28whYuzrt2sdWeNy6xMduptU3vUHkpdakjcFXrNuObXqy7M69qhRt9 C6hNvelp2X/bN+1kX+bO1sbZ9yaLZE1jk7mo/v+eEktxRqKhFnNRcSIAIEpJzY8CAAA= X-MTR: 20000000000000000@CPGS Sender: linux-samsung-soc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-samsung-soc@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP 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 Reviewed-by: Javier Martinez Canillas Acked-by: Bartlomiej Zolnierkiewicz Reviewed-by: Pankaj Dubey --- Documentation/devicetree/bindings/arm/samsung/exynos.txt | 12 ++++++++++++ 1 file changed, 12 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..0c606f4c6e85 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/samsung/exynos.txt @@ -0,0 +1,12 @@ +Samsung Exynos SoC Family Device Tree Bindings +--------------------------------------------------------------- + +Work in progress statement: + +Device tree files and bindings applying to Samsung Exynos SoCs and boards are +considered "unstable". Any Samsung Exynos device tree binding 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.