linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Franklin S Cooper Jr <fcooper@ti.com>
Cc: gregkh@linuxfoundation.org, ssantosh@kernel.org,
	linux@armlinux.org.uk, balbi@kernel.org,
	linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] dt-bindings: usb: keystone-usb: Update bindings pm and clocks properties
Date: Thu, 10 Aug 2017 11:33:51 -0500	[thread overview]
Message-ID: <20170810163351.ykqkf353uk5ehjdn@rob-hp-laptop> (raw)
In-Reply-To: <20170802201724.11439-3-fcooper@ti.com>

On Wed, Aug 02, 2017 at 03:17:23PM -0500, Franklin S Cooper Jr wrote:
> Update varous properties to properly indicate their requirement depending
> on the SoC.
> 
> Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
> ---
>  Documentation/devicetree/bindings/usb/keystone-usb.txt | 18 ++++++++++++++++--
>  1 file changed, 16 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/usb/keystone-usb.txt b/Documentation/devicetree/bindings/usb/keystone-usb.txt
> index 60527d3..307531b 100644
> --- a/Documentation/devicetree/bindings/usb/keystone-usb.txt
> +++ b/Documentation/devicetree/bindings/usb/keystone-usb.txt
> @@ -12,8 +12,22 @@ Required properties:
>     MPU.
>   - ranges: allows valid 1:1 translation between child's address space and
>     parent's address space.
> - - clocks: Clock IDs array as required by the controller.
> - - clock-names: names of clocks correseponding to IDs in the clock property.
> +
> +SoC-specific Required Properties:
> +The following are mandatory properties for Keystone 2 66AK2HK, 66AK2L and 66AK2E
> +SoCs only:
> +
> +- clocks:		Clock IDs array as required by the controller.
> +- clock-names:		names of clocks correseponding to IDs in the clock
> +			property.

This needs to be specific as to how many clocks and their names.

> +
> +
> +The following are mandatory properties for Keystone 2 66AK2G SoCs only:
> +
> +- power-domains:	Should contain a phandle to a PM domain provider node
> +			and an args specifier containing the USB device id
> +			value. This property is as per the binding,
> +			Documentation/devicetree/bindings/soc/ti/sci-pm-domain.txt
>  
>  Sub-nodes:
>  The dwc3 core should be added as subnode to Keystone DWC3 glue.
> -- 
> 2.9.4.dirty
> 

  reply	other threads:[~2017-08-10 16:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 20:17 [PATCH 0/3] ARM: dts: k2g: Add support for USB instances on 66AK2G Franklin S Cooper Jr
2017-08-02 20:17 ` [PATCH 1/3] usb: dwc3: keystone: Add PM_RUNTIME Support to DWC3 Keystone USB driver Franklin S Cooper Jr
2017-08-02 20:17 ` [PATCH 2/3] dt-bindings: usb: keystone-usb: Update bindings pm and clocks properties Franklin S Cooper Jr
2017-08-10 16:33   ` Rob Herring [this message]
2017-08-02 20:17 ` [PATCH 3/3] ARM: dts: k2g: Add USB instances Franklin S Cooper Jr
2017-08-07 13:41 ` [PATCH 0/3] ARM: dts: k2g: Add support for USB instances on 66AK2G santosh.shilimkar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170810163351.ykqkf353uk5ehjdn@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=balbi@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fcooper@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=ssantosh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).