Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp4236440ybl; Tue, 20 Aug 2019 08:55:35 -0700 (PDT) X-Google-Smtp-Source: APXvYqwMGdkEaTOx6xUI5xCr/Qwe8OrqNcZth7ELY12YSs1Hxwr6DjJPHrtR5/PB6b8cly1/Oa5R X-Received: by 2002:a62:7503:: with SMTP id q3mr31820666pfc.151.1566316535909; Tue, 20 Aug 2019 08:55:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566316535; cv=none; d=google.com; s=arc-20160816; b=Yc/MGKAUHfNP79w4AwXGibmaSWStR5pGdghgQ20evpK1TIU2vz0SNAb+Xs5wSxJHvP enVQqvRenLMLijo1PhBoa8hTCW3gLEYWXX3Sas/ZXkrXFG7oBjq0XpsTc8ao74xAMtPu P8Q9cguaXAuaSBFBs6oNVqGVxrsoK5lOPFlrEr2XQc3aGvE8IF0FAtQkni07kzbeF+dr diK9HxOurv7yoCMaV+20E64rfDVk3Y6MM0kCKcCt+xCMYt3hk1XKT7HLoLXlf6eoG2RO hRE1z1HA6PxPkc3uQeI6G8TvfGtYbgtPDcDC0mwUThW2P3dwISpKX4XR8w2S7K4v51hj 1NSw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=i02aVAqzQgCnVhbN+7J7Fz8Ot3UHPAAZ5TVNy4yokCI=; b=bneDbHNSuVf6VoazFLHz0IagP6QnPA6NTe96ZGsunvkOw35gpjYm80a4dfRH2ZCC7i bwh3jHHehcj/f/8O9defrqnX6EKK7nEZ4SYdmv0IAU3YUTVdueE0j4PCny1XBD+aAWfe 1COKNIDV4y9TO0yYycpae9x24A5LS4mpi3ojqD/PaTsyghptMYuZ8CssaMYn3dI9sINF fZN+glPMZdpjfVlcnO+dMra/BEAZQaA9u2BFZveo6Gd9OwhgWMNQvZ44787aN7sxpVYG UI8PQ/tF30vR0t1Bukj4rI58z456G6dThNZJO2UqU1UVDQYqi+YZBD4qvRI6yWpoWcEy HV3w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=YcK07Xtg; 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=pass (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 v184si12448030pgb.2.2019.08.20.08.55.20; Tue, 20 Aug 2019 08:55:35 -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; dkim=pass header.i=@kernel.org header.s=default header.b=YcK07Xtg; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730497AbfHTPyb (ORCPT + 99 others); Tue, 20 Aug 2019 11:54:31 -0400 Received: from mail.kernel.org ([198.145.29.99]:60386 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727246AbfHTPyb (ORCPT ); Tue, 20 Aug 2019 11:54:31 -0400 Received: from mail-qt1-f182.google.com (mail-qt1-f182.google.com [209.85.160.182]) (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 87B7D205ED; Tue, 20 Aug 2019 15:54:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1566316470; bh=K8yW+xYCQIIvZaPUVrPLDL0/nQ7cDz12rR0ZSD9Uut8=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=YcK07XtglPgBpab3DgEUMK4mVuNiEoKFYliG/e4zwRHBAjxqCQ040vr+ge8R2r3Xw duRuCLIzw49sFiVVufmfsbSCLAFBEQoGsuC9a3ytIGqXAbvE77POrI6/mm7Mu0tVnn XgjUgTjOo8T9bgvgr54iqtR3P2CSfFT7UOZm+1c8= Received: by mail-qt1-f182.google.com with SMTP id l9so6577764qtu.6; Tue, 20 Aug 2019 08:54:30 -0700 (PDT) X-Gm-Message-State: APjAAAWVgL1F1OSt/cHkHoIK3vtn8UniW7yWU0Tl+tVZYIdDQeYs8NPg M/iW6bACJ+tl/k3/W4SI0iKZYICPXXTQe+Lhaw== X-Received: by 2002:ac8:44c4:: with SMTP id b4mr26574552qto.224.1566316469752; Tue, 20 Aug 2019 08:54:29 -0700 (PDT) MIME-Version: 1.0 References: <20190820103133.53776-1-vadivel.muruganx.ramuthevar@linux.intel.com> In-Reply-To: <20190820103133.53776-1-vadivel.muruganx.ramuthevar@linux.intel.com> From: Rob Herring Date: Tue, 20 Aug 2019 10:54:18 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 1/2] dt-bindings: phy: intel-emmc-phy: Add YAML schema for LGM eMMC PHY To: "Ramuthevar,Vadivel MuruganX" Cc: Kishon Vijay Abraham I , "linux-kernel@vger.kernel.org" , devicetree@vger.kernel.org, Andy Shevchenko , cheol.yong.kim@intel.com, qi-ming.wu@intel.com, peter.harliman.liem@intel.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 20, 2019 at 5:31 AM 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 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 | 72 ++++++++++++++++++++++ > 1 file changed, 72 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..ec177573aca6 > --- /dev/null > +++ b/Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml > @@ -0,0 +1,72 @@ > +# 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: > + - Add a new compatible to use the host controller driver with the > + eMMC PHY on Intel's Lightning Mountain SoC. > + > +$ref: /schemas/types.yaml#definitions/phandle > + description: > + - It also requires a "syscon" node with compatible = "intel,lgm-chiptop", > + "syscon" to access the eMMC PHY register. Not valid schema. Please build 'make dt_binding_check' and fix any warnings. > + > +properties: > + "#phy-cells": > + const: 0 > + > + compatible: > + const: intel,lgm-emmc-phy > + > + reg: > + maxItems: 1 > + > + intel,syscon: > + items: > + - description: > + - | > + e-MMC phy module should include the following properties > + * reg, Access the e-MMC, get the base address from syscon. > + * reset, reset the e-MMC module. > + > + clocks: > + items: > + - description: e-MMC phy module clock > + > + clock-names: > + items: > + - const: emmcclk > + > + resets: > + maxItems: 1 > + > +required: > + - "#phy-cells" > + - compatible > + - reg > + - clocks > + - clock-names > + - resets > + > +additionalProperties: false > + > +examples: > + - | > + emmc_phy: emmc_phy { > + compatible = "intel,lgm-emmc-phy"; > + reg = <0xe0020000 0x100>; > + intel,syscon = <&sysconf>; > + clocks = <&emmc>; > + clock-names = "emmcclk"; > + #phy-cells = <0>; > + }; > + > +... > -- > 2.11.0 >