From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.0 required=3.0 tests=MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_PASS,URIBL_BLOCKED,USER_AGENT_NEOMUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9E4F8ECE560 for ; Mon, 17 Sep 2018 15:57:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4376B2088F for ; Mon, 17 Sep 2018 15:57:58 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4376B2088F Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728186AbeIQVZy (ORCPT ); Mon, 17 Sep 2018 17:25:54 -0400 Received: from mail-ed1-f68.google.com ([209.85.208.68]:44081 "EHLO mail-ed1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727063AbeIQVZy (ORCPT ); Mon, 17 Sep 2018 17:25:54 -0400 Received: by mail-ed1-f68.google.com with SMTP id s10-v6so13324663edb.11; Mon, 17 Sep 2018 08:57:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=daFVwhPYBGLcjCqqVG2rfioaWFKkqTf3dToL7Iu9tyU=; b=JChuBEWACm1tAKuJQW7pgiiWNtmCfI7CEL//3w/1To1yKt9VYFZ3SZ7VbDOzZGe053 eFMNnS3YYtDhP8qJBA9ME6dppZT3/WmiT9vahqaYMHa7ZAtecbNyEAk8tU9ZwZ34KVh2 ViFDOAEqPgIaS0EqnGcct2JOOzW7AVw7o1y3o2lviE0WFd8cGb0wJetJ+BG2jO8TvhjH bG6FjDlFJ/oUaCwH/vJlX/n9FxEIsB2u4xpGx+wnPNl/NaJ3pOg1QV+9Ovqqwfkt5P14 0rCABnG4tEHYQrUiceyFusmwyVIRNlTeo7pZgNWos6LCewokiXG3Jeqz3nDQF5AVA3PO Bx8w== X-Gm-Message-State: APzg51C3rVzHafJFdace8qZTAgPwAAz1StIHyvxsOjL60SuLoI/+t9nU mbpu6HtxwGmDT6SscgHXKdc= X-Google-Smtp-Source: ANB0VdbWlyh2nEPKkWqGYBgn+bNVSijsZJX+PlZwZBP1ye+6d71wsKMwGvFBOwNuX2rEQXDcidfU8Q== X-Received: by 2002:a50:ca83:: with SMTP id x3-v6mr41884140edh.287.1537199874436; Mon, 17 Sep 2018 08:57:54 -0700 (PDT) Received: from kozik-lap ([178.38.103.27]) by smtp.googlemail.com with ESMTPSA id o22-v6sm14466271edc.90.2018.09.17.08.57.51 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 17 Sep 2018 08:57:53 -0700 (PDT) Date: Mon, 17 Sep 2018 17:57:49 +0200 From: Krzysztof Kozlowski To: Rob Herring , Mark Rutland , Kukjin Kim , 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: Re: [PATCH v3] dt-bindings: arm: Explicitly mark Samsung Exynos SoC as unstable Message-ID: <20180917155749.i6jx7k4vo32y56kd@kozik-lap> References: <20180830180205.18121-1-krzk@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20180830180205.18121-1-krzk@kernel.org> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > [krzk: Explicitly list unstable bindings instead of marking entire > Exynos] > Signed-off-by: Krzysztof Kozlowski > Reviewed-by: Javier Martinez Canillas > Acked-by: Bartlomiej Zolnierkiewicz > Applied. Best regards, Krzysztof