From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756171AbeEAQeh (ORCPT ); Tue, 1 May 2018 12:34:37 -0400 Received: from mail.kernel.org ([198.145.29.99]:59606 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755942AbeEAQef (ORCPT ); Tue, 1 May 2018 12:34:35 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 49894236F3 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=robh@kernel.org X-Google-Smtp-Source: AB8JxZoSok3m+zsedGxNbZYEzJCjDmE6S0Aiq2Nnm9MGl8mutMqHwDcYyg2esX6FSqLHZKS/JdpTKtMJbexilLMGPmo= MIME-Version: 1.0 In-Reply-To: References: <20180430114058.5061-1-jagan@amarulasolutions.com> <20180430114058.5061-2-jagan@amarulasolutions.com> <20180501161618.GA32350@rob-hp-laptop> From: Rob Herring Date: Tue, 1 May 2018 11:34:14 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 01/21] dt-bindings: clock: Add compatible for A64 DE2 CCU To: Chen-Yu Tsai Cc: Jagan Teki , Maxime Ripard , Icenowy Zheng , Jernej Skrabec , Mark Rutland , Catalin Marinas , Will Deacon , David Airlie , dri-devel , Michael Turquette , Stephen Boyd , linux-clk , Michael Trimarchi , linux-arm-kernel , devicetree , linux-kernel , linux-sunxi Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 1, 2018 at 11:19 AM, Chen-Yu Tsai wrote: > On Wed, May 2, 2018 at 12:16 AM, Rob Herring wrote: >> On Mon, Apr 30, 2018 at 05:10:38PM +0530, Jagan Teki wrote: >>> Allwinner A64 has DE2 CCU which is similar to H3/H5 SoC. >>> >>> Signed-off-by: Jagan Teki >>> --- >>> Documentation/devicetree/bindings/clock/sun8i-de2.txt | 1 + >>> 1 file changed, 1 insertion(+) >> >> Reviewed-by: Rob Herring > > Hi Rob, > > Do we need to add this if it's just a soc-specific compatible > we add in the device tree to future proof things in case we > discover quirks later on? Yes, but the fallbacks should be documented too as I found in the rest of the series. > AFAIK we haven't been doing this, and this is likely to create > some confusion, because they aren't actually mentioned anywhere > in the driver. The binding doc needs to written such that compatible can be validated to contain the correct set of strings. We can't do that now with free form text, but when we move to a schema we will. Rob