Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2341954imu; Tue, 6 Nov 2018 12:58:10 -0800 (PST) X-Google-Smtp-Source: AJdET5feIyijOL43xrUnBut+fivbPGYpjysOyhC8PP4M//aiPet3RIRzPz7z9gobnKSHdiZjCxHV X-Received: by 2002:a63:8549:: with SMTP id u70mr25109201pgd.401.1541537890762; Tue, 06 Nov 2018 12:58:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541537890; cv=none; d=google.com; s=arc-20160816; b=NLS/ZIXP44/H/PXtDkSlTZpYuAkI1RcSzC2o/OG2ko1or0nQpuArRvTp2FCjjBnBEM Q9vboTeV2CikUOnG16nwPp7/9sWGP4EtRpdKVEcn+BlqoNqI50dRrb1on4EFsPS0Vvgb MOu/paMunLkqAu26qwYbNuMesKupb5xqcI9PbFlD099Mfmwsf78EsXEdN3DM5j0Gro3L 8IWYPExDQPFGSLoegpk8EPseLf7uRCQy5qm04Ip5HVvLeRZPDaTEDCmXn1OpyZABX8Cw abD5sY7ZSfsKikRPJyJXZ0oEYhlcyB0BVfo58qdaqTBOZcyGO+9r2biEllBzv39JqYp1 2EIQ== 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=upA8fMygET0KQEQsRnbuiauc/MhZfj1jUX/STvPBWn4=; b=sfg22uLdxDleieF4p/g6EiyefL3f0mlA40meXOPQcJzvPHp2TLrcLMQ9Rkhc5Ax3a7 htAE7CxhwgdMtkx8gHIPPRif2IKhkweifm5Z8a+6jOaNlpYGWPve0lN0Oey4EXV7y77D OTjoxYSOoACeBipMrYAIfWv9mPpEEZONLlPATwR/saClv+8hBCSyuUdi7P+H1CRyV8Bl 7Tm1i1S3B8psmLP4NsfGJvCKSGbI7AWH2hciY5uaTaiC3b9ZINGJq/xe8lMLZ3UR703A kMoriFxQtwB2+ah2YxQt8facOV2fBDqCNbIZhKHeymOCWCm61RgiPyNosVrBzMMNJyxK wjFg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="JWp0Y/Yi"; 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 y10-v6si13020212plt.145.2018.11.06.12.57.55; Tue, 06 Nov 2018 12:58:10 -0800 (PST) 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="JWp0Y/Yi"; 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 S2388778AbeKGGXM (ORCPT + 99 others); Wed, 7 Nov 2018 01:23:12 -0500 Received: from mail.kernel.org ([198.145.29.99]:50802 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388208AbeKGGXM (ORCPT ); Wed, 7 Nov 2018 01:23:12 -0500 Received: from mail-qk1-f178.google.com (mail-qk1-f178.google.com [209.85.222.178]) (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 D802A2083D; Tue, 6 Nov 2018 20:56:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1541537766; bh=aL+CTRK4kbTb1vjOMTK4/s7gQmcIosOQr5Iz1wfEd30=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=JWp0Y/Yia5yjpTl1lK207lMI2+6fBJhcixhEVRBmCj0SX0kI8bqu3f2V99FRjWcWf Ck8igVihuGyv8Nxlc/zOrFOP+78P6BwDtSqFJEBRW4hDTH8X8LQjJt/w2gSKRYs7Zs mwfGATcrLFAQCxO05KFz7HW310lqvJiwknxw0cNE= Received: by mail-qk1-f178.google.com with SMTP id 189so19325946qkj.8; Tue, 06 Nov 2018 12:56:05 -0800 (PST) X-Gm-Message-State: AGRZ1gLVJPUtaQNy64jgef9LopYN1NnJBfJiLXLsDevhIzR5NZPPRkDd 7PGPoBIyToficW1JXdLuUzOvE2thfCM0DEMy9Q== X-Received: by 2002:ae9:ef14:: with SMTP id d20mr26655502qkg.147.1541537765086; Tue, 06 Nov 2018 12:56:05 -0800 (PST) MIME-Version: 1.0 References: <20181102192616.28291-1-faiz_abbas@ti.com> <20181102192616.28291-3-faiz_abbas@ti.com> In-Reply-To: <20181102192616.28291-3-faiz_abbas@ti.com> From: Rob Herring Date: Tue, 6 Nov 2018 14:55:54 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 2/6] dt-bindings: phy: phy-of-simple: Document new binding To: Faiz Abbas Cc: "linux-kernel@vger.kernel.org" , devicetree@vger.kernel.org, netdev , linux-can@vger.kernel.org, Wolfgang Grandegger , Marc Kleine-Budde , Mark Rutland , Kishon Vijay Abraham I 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 Fri, Nov 2, 2018 at 2:23 PM Faiz Abbas wrote: > > Add documentation for the generic simple phy implementation. We don't do 'simple' or 'generic' bindings. > Signed-off-by: Faiz Abbas > --- > .../devicetree/bindings/phy/phy-of-simple.txt | 29 +++++++++++++++++++ > 1 file changed, 29 insertions(+) > create mode 100644 Documentation/devicetree/bindings/phy/phy-of-simple.txt > > diff --git a/Documentation/devicetree/bindings/phy/phy-of-simple.txt b/Documentation/devicetree/bindings/phy/phy-of-simple.txt > new file mode 100644 > index 000000000000..696f2763395c > --- /dev/null > +++ b/Documentation/devicetree/bindings/phy/phy-of-simple.txt > @@ -0,0 +1,29 @@ > +Generic simple phy device tree binding > +-------------------------------------- > + > +A good number of phy implementations merely read dts properties, > +enable clocks, regulators or do resets without having a dedicated register > +map. This binding implements a generic phy driver which can be used for > +such simple implementations and avoid boilerplate code duplication. Sure, but then latter some needs certain timing/ordering of those controls or some other DT additions. 'generic' or 'simple' never work out for bindings. By all means though, write a simple/generic phy driver. Just make it understand an explicit list of compatible strings. Then when a phy turns out to be not so simple, we can write a driver for it with changing the DT. > +Required Properties: > +- compatible : must be "simple-phy" > +- phy-cells : must be 0 #phy-cells > + > +Optional Properties: > +- bus-width : generic bus-width. Must be positive. > +- max-bitrate : generic max-bitrate. Must be positive. > +- pwr : phandle to phy pwr regulator node. That's not the regulator binding. > + > +Example: > + > +The following example is a can transceiver implemented as a generic phy. > +It has a max-bitrate property and a pwr regulator. > + > + > +transceiver1: can-transceiver { > + compatible = "simple-phy"; > + max-bitrate = <5000000>; > + pwr-supply = <&transceiver1_fixed>; > + #phy-cells = <0>; > +}; > -- > 2.18.0 >