Received: by 10.223.176.46 with SMTP id f43csp3012470wra; Mon, 22 Jan 2018 07:06:04 -0800 (PST) X-Google-Smtp-Source: AH8x225fDaOPltT/BC2vDoPHy6viUrJa8pTud09Q5R0+JgXGxIKe591ChfA/Y8OEBsiHDOSEBDhy X-Received: by 10.107.88.7 with SMTP id m7mr8029406iob.162.1516633563930; Mon, 22 Jan 2018 07:06:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516633563; cv=none; d=google.com; s=arc-20160816; b=ZqOc/ZHZZe7tLQSUhMKrsdtXXIEA3ccVZYDmNfKxc/rHytCzxy0bD5RosiuMVz6OiM vZILwr1tUy08vfjhwjIdPmBZ4+/0Jlt5JNMmArGidPoI1JpMKB3+OktQI/ySqPVK/1H3 lCOy5xkbs2eNtjYI6FnixM5BQxoMldtkkckHde0xylq37TOgYUjGw54zjQsLBlQV9wrH 9r2A0+Geid0dE24xFi5rwqmGTQdeAs0MCmIZfePS9wf2eJqrEAlDrt9j1pqaKjHTAcEJ lB7lRNrYqZXJRMS3hG7eorbJG6TkbG2/UsrpkJBHHHVgPhCIliXmd2qPGjQ6hRdtRcSg xVRw== 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:arc-authentication-results; bh=pDgTpXUfxIPVQsFVOXJR1pEqRPhVe5cz2avngX4glE4=; b=EHhuZRKcE4l3kFbkfHHYgCt51EWSzOxe9qVfvta0s+bNqxkq100Irf49T+eDGJePzW iBUJB0o08S89eRDFAuBwcB5RHzw5MRBlWaboQbalraXfNt3yPzy48Jhy4Fo4BehrC1PG fYk76E57+MICtCNVNDlbNuXIVFtSckIsduZLIKvs0ZgU/9ZBt1p7mKNbGhy7A289lhWX Yim6XDqH881hoIXRUZSY1MzbBgTdHtBRs6gKq9xgWCnKYnThkz8b8JdFctJh8jr9CzkI UlPX7a0UShLcvAq8QtJeyWOlJlDoHD7Fa2PmlPQqCPbPG8rZ8vYDcOs5RSyJLRYVCdFw v5Bw== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v10si12779037iod.248.2018.01.22.07.05.50; Mon, 22 Jan 2018 07:06:03 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751265AbeAVPFK (ORCPT + 99 others); Mon, 22 Jan 2018 10:05:10 -0500 Received: from mail-oi0-f66.google.com ([209.85.218.66]:42838 "EHLO mail-oi0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751167AbeAVPFG (ORCPT ); Mon, 22 Jan 2018 10:05:06 -0500 Received: by mail-oi0-f66.google.com with SMTP id c8so5649981oiy.9; Mon, 22 Jan 2018 07:05:06 -0800 (PST) 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=pDgTpXUfxIPVQsFVOXJR1pEqRPhVe5cz2avngX4glE4=; b=L9UajypGgztCJcWTTGRk6jZE5Z73JhCYuFaetA80gVI/QyiNgoRo4j5Vz11+A19Y12 d32ocVM14nY9tAaTPor4ezm9FcboyXJV91v6iDOrAvWS5gZUX42lgTAOljcqmGKRaBiq aHSWhnM5kR9uaxqUH/hLLY3EtLglaeNp7oShIHI66lpQHR80s06tRG7u95l5leaxHt8Y jQWwQzNQJwBc9e/NTh6YECFsekoPH5E3QEABz12oTr7ZMLfGJNdAwRwBqxqxpLVP1EGX fH/mLUMRsQCuyla0GLgA+RwfJa/d4+/j7qhaQiYqZsJTxImIfmdE7Z6jSJUCqPpPJ+bG vZ9Q== X-Gm-Message-State: AKwxyte/XFv/xyn3UvcL2Ttwt4sVuIwYw10CLeeP6E/VmRmusJllZAE2 6V+H1WbVj4+2M7wXoDnvUw== X-Received: by 10.202.50.130 with SMTP id y124mr3608024oiy.155.1516633505832; Mon, 22 Jan 2018 07:05:05 -0800 (PST) Received: from localhost (216-188-254-6.dyn.grandenetworks.net. [216.188.254.6]) by smtp.gmail.com with ESMTPSA id d21sm7997992oti.66.2018.01.22.07.05.03 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 22 Jan 2018 07:05:04 -0800 (PST) Date: Mon, 22 Jan 2018 09:05:03 -0600 From: Rob Herring To: David Lechner Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Michael Turquette , Stephen Boyd , Mark Rutland , Sekhar Nori , Kevin Hilman , Bartosz Golaszewski , Adam Ford , linux-kernel@vger.kernel.org Subject: Re: [PATCH v6 09/41] dt-bindings: clock: New bindings for TI Davinci PSC Message-ID: <20180122150503.ciavehj5dd22535n@rob-hp-laptop> References: <1516468460-4908-1-git-send-email-david@lechnology.com> <1516468460-4908-10-git-send-email-david@lechnology.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1516468460-4908-10-git-send-email-david@lechnology.com> 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 Sat, Jan 20, 2018 at 11:13:48AM -0600, David Lechner wrote: > This adds a new binding for the Power Sleep Controller (PSC) for the > mach-davinci family of processors. > > Note: Although TI Keystone has a very similar PSC, we are not using the > existing bindings. Keystone is using a legacy one-node-per-clock binding > (actually two nodes if you count the separate reset binding for the same > IP block). Also, some davinci LPSCs have quirks that aren't handled by > the keystone bindings, so we would be adding one compatible string per > clock with quirks instead of just a new compatible string for each > controller. > > Signed-off-by: David Lechner > --- > > v6 changes: > - added clocks and clock-names properties > - expanded examples > > .../devicetree/bindings/clock/ti/davinci/psc.txt | 66 ++++++++++++++++++++++ > 1 file changed, 66 insertions(+) > create mode 100644 Documentation/devicetree/bindings/clock/ti/davinci/psc.txt > > diff --git a/Documentation/devicetree/bindings/clock/ti/davinci/psc.txt b/Documentation/devicetree/bindings/clock/ti/davinci/psc.txt > new file mode 100644 > index 0000000..0c2d2bd > --- /dev/null > +++ b/Documentation/devicetree/bindings/clock/ti/davinci/psc.txt > @@ -0,0 +1,66 @@ > +Binding for TI DaVinci Power Sleep Controller (PSC) > + > +The PSC provides power management, clock gating and reset functionality. It is > +primarily used for clocking. > + > +Required properties: > +- compatible: shall be one of: > + - "ti,da850-psc0" for PSC0 on DA850/OMAP-L138/AM18XX > + - "ti,da850-psc1" for PSC1 on DA850/OMAP-L138/AM18XX > +- reg: physical base address and size of the controller's register area > +- #clock-cells: from common clock binding; shall be set to 1 > +- clocks: phandles to clocks corresponding to the clock-names property > +- clock-names: list of parent clock names - depends on compatible value > + - for "ti,da850-psc0", shall be "pll0_sysclk1", "pll0_sysclk2", > + "pll0_sysclk4", "pll0_sysclk6", "async1" > + - for "ti,da850-psc1", shall be "pll0_sysclk2", "pll0_sysclk4", "async3" > + > +Optional properties: > +- #reset-cells: from reset binding; shall be set to 1 - only applicable when > + at least one local domain provides a local reset. > + > +Consumers: > + > + Clock and reset consumers shall use the local power domain module ID > + (LPSC) as the index corresponding to the clock cell. Refer to the > + device-specific datasheet to find these numbers. NB: Most local domains > + only provide a clock and not a reset. > + > +Examples: > + > + psc0: clock-controller@10000 { > + compatible = "ti,da850-psc0"; > + reg = <0x10000 0x1000>; > + #clock-cells = <1>; > + #reset-cells = <1>; > + clocks = <&pll0_sysclk 1>, <&pll0_sysclk 2>, > + <&pll0_sysclk 4>, <&pll0_sysclk 6>, <&async1_clk>; > + clock_names = "pll0_sysclk1", "pll0_sysclk2", Should be clock-names > + "pll0_sysclk4", "pll0_sysclk6", "async1"; > + }; > + psc1: clock-controller@227000 { > + compatible = "ti,da850-psc1"; > + reg = <0x227000 0x1000>; > + #clock-cells = <1>; > + clocks = <&pll0_sysclk 2>, <&pll0_sysclk 4>, <&async3_clk>; > + clock_names = "pll0_sysclk2", "pll0_sysclk4", "async3"; ditto With that, Reviewed-by: Rob Herring