Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp5630917ybe; Tue, 17 Sep 2019 10:59:58 -0700 (PDT) X-Google-Smtp-Source: APXvYqwT5byThoj/oFqwIpJXQF8QGalCmSo7E3EmotbfY1vxmS9WTpjX0C5ExxRyGeRj0sJ4p5IS X-Received: by 2002:aa7:d9d2:: with SMTP id v18mr6035092eds.177.1568743197940; Tue, 17 Sep 2019 10:59:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568743197; cv=none; d=google.com; s=arc-20160816; b=BIN2LRj6WAy0pGqV5TDyTVEvTgkaKyKwuo0guZjBfWhw69aEjg99xwVHBUf7pKnkZ8 aEHXjHM877yCWGp4VMzJoDMG3ieESrKsOv+gfiJ4HR+5zlyK+RMfHio/U9OyjCvVyf+R BqR3SBiN0SWcQmD0l7+CmQdkT0SsCHr6P01P9uIa8AFBYJiLBiBX2xe4jKsT6Hug8okn Sn5IBHISZUvM1JQS8YQGFjU20SIcZLhig1XqZxxw/gGx9E2HQpSe1q43muUizXZXL3bD M3ENLR3fhje4lrlScl1KRfx3AifeoFryKSd56smMIiEd8U3YYmFCHY6P44tqAAF07X5r G/fA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=X9xy3wm83YouZRo1BB7hVE9u2ONh+tQ6r8bXgR1pEJk=; b=PrijK02hxPkMJIf5BHY3ev/7igWwuWnPhc9peBvUsWUkfWnvQg5gxfrmNpgQ2XWthP mhASrKJXWp6qCNSBTg1Tdx1fGx8XKXN/MV0DPk58tafKbf7heUh5ZpoJkXN42vN2vqyE ecld/8IITDA7LP26AhMLIRpBBjP7AFREzL5C6y1laULyKOMu6MQ6560Qq9+JSgCTRrBt ZtI/P8Ha2kessiMZI4mzpUwa43fKU/xE7z03LFh5wNKm2JQQLWQZY7T7u8ebfewMLh1G 8CK3ztX7iDJM32zVG122oPRVoBWqRUyFX7eiVb+vo6uSkvG35TX6w9Cuxi0/N3Q/dejq A1Yw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b4si2019552edk.331.2019.09.17.10.59.32; Tue, 17 Sep 2019 10:59:57 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727794AbfIQOXk (ORCPT + 99 others); Tue, 17 Sep 2019 10:23:40 -0400 Received: from mail-ot1-f68.google.com ([209.85.210.68]:45522 "EHLO mail-ot1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725922AbfIQOXk (ORCPT ); Tue, 17 Sep 2019 10:23:40 -0400 Received: by mail-ot1-f68.google.com with SMTP id 41so3155690oti.12; Tue, 17 Sep 2019 07:23:39 -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=X9xy3wm83YouZRo1BB7hVE9u2ONh+tQ6r8bXgR1pEJk=; b=gKH9iJf9xqQ5oW+X3Es9rQXVr32RejsamqbpWodwTw1YzFNsvZAc3imilPsbWRUIvn QLzmwMdJhfhakczrS1wxJdGRPRY1L37FGfkfQXWDUWs59HxnfmzLGcje8NiNGKuevVyx iWK2S10/2+A1VaLQYo82lf7Hfp0kbGidxcshr03kokyuJP1cEkvLOi/zKrqEofNVmRl7 iBg7e7nnDPuY++xFH9mlM5hglXLfiER1ifarzRM0TEAq7V6L567UhKi5yJAFhmIuHLNj FDvF1F8TOQrkpfwin99x5L4PoWLF7G2rUvLiDpN+bGFXlSJbV2mFVYxqv0jH+mHzxhfr JLCw== X-Gm-Message-State: APjAAAUPOsEKebZFzCjbMjjRtupN7Dq3x8/WiyjRmysKVpv9RJ8e9Zti +rWdGtO5EFjDe7k6WLYO7+iNu+Y= X-Received: by 2002:a05:6830:1357:: with SMTP id r23mr2940766otq.91.1568730218619; Tue, 17 Sep 2019 07:23:38 -0700 (PDT) Received: from localhost (24-155-109-49.dyn.grandenetworks.net. [24.155.109.49]) by smtp.gmail.com with ESMTPSA id b5sm757007otp.36.2019.09.17.07.23.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 17 Sep 2019 07:23:38 -0700 (PDT) Date: Tue, 17 Sep 2019 09:23:37 -0500 From: Rob Herring To: "Ramuthevar,Vadivel MuruganX" Cc: kishon@ti.com, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, andriy.shevchenko@intel.com, cheol.yong.kim@intel.com, qi-ming.wu@intel.com, peter.harliman.liem@intel.com Subject: Re: [PATCH v5 1/2] dt-bindings: phy: intel-emmc-phy: Add YAML schema for LGM eMMC PHY Message-ID: <20190917142337.GA27151@bogus> References: <20190904055344.25512-1-vadivel.muruganx.ramuthevar@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190904055344.25512-1-vadivel.muruganx.ramuthevar@linux.intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 04, 2019 at 01:53:43PM +0800, Ramuthevar,Vadivel MuruganX wrote: > From: Ramuthevar Vadivel Murugan > > Add a YAML schema to use the host controller driver with the > eMMC PHY on Intel's Lightning Mountain SoC. > > Signed-off-by: Ramuthevar Vadivel Murugan > --- > changes in v5: > - earlier Review-by tag given by Rob > - rework done with syscon parent node. > > changes in v4: > - As per Rob's review: validate 5.2 and 5.3 > - drop unrelated items. > > changes in v3: > - resolve 'make dt_binding_check' warnings > > changes in v2: > As per Rob Herring review comments, the following updates > - change GPL-2.0 -> (GPL-2.0-only OR BSD-2-Clause) > - filename is the compatible string plus .yaml > - LGM: Lightning Mountain > - update maintainer > - add intel,syscon under property list > - keep one example instead of two > --- > .../bindings/phy/intel,lgm-emmc-phy.yaml | 69 ++++++++++++++++++++++ > 1 file changed, 69 insertions(+) > create mode 100644 Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml > > diff --git a/Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml b/Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml > new file mode 100644 > index 000000000000..8f6ac8b3da42 > --- /dev/null > +++ b/Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml > @@ -0,0 +1,69 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/phy/intel,lgm-emmc-phy.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Intel Lightning Mountain(LGM) eMMC PHY Device Tree Bindings > + > +maintainers: > + - Ramuthevar Vadivel Murugan > + > +description: Bindings for eMMC PHY on Intel's Lightning Mountain SoC, syscon > + node is used to reference the base address of eMMC phy registers. > + > +select: > + properties: > + compatible: > + contains: > + const: intel,lgm-syscon This, plus... > + > + reg: > + maxItems: 1 > + > + required: > + - compatible > + - reg > + > +properties: > + "#phy-cells": > + const: 0 > + > + compatible: > + contains: > + const: intel,lgm-emmc-phy ...this should not pass validation as they contradict each other. > + > + reg: > + maxItems: 1 > + > + clocks: > + maxItems: 1 > + > + clock-names: > + maxItems: 1 > + > +required: > + - "#phy-cells" > + - compatible > + - reg > + - clocks > + - clock-names > + > +examples: > + - | > + sysconf: chiptop@e0200000 { > + compatible = "intel,lgm-syscon"; > + reg = <0xe0200000 0x100>; I'm still waiting for a complete description of what all is in this block. > + > + emmc-phy: emmc-phy { > + compatible = "intel,lgm-emmc-phy"; > + reg = <0x00a8 0x4>, > + <0x00ac 0x4>, > + <0x00b0 0x4>, > + <0x00b4 0x4>; Looks contiguous and can be a single entry: <0xa8 0x10> > + clocks = <&emmc>; > + clock-names = "emmcclk"; > + #phy-cells = <0>; > + }; > + }; > +... > -- > 2.11.0 >