devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Chunfeng Yun <chunfeng.yun@mediatek.com>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	Rob Herring <robh+dt@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Felipe Balbi <balbi@ti.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Roger Quadros <rogerq@ti.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	John Crispin <blogic@openwrt.org>,
	Daniel Kurtz <djkurtz@chromium.org>
Subject: Re: [PATCH v3 2/5] dt-bindings: Add a binding for Mediatek xHCI host controller
Date: Wed, 22 Jul 2015 15:22:08 +0100	[thread overview]
Message-ID: <20150722142208.GC15809@leverpostej> (raw)
In-Reply-To: <1437573945-31586-3-git-send-email-chunfeng.yun@mediatek.com>

On Wed, Jul 22, 2015 at 03:05:42PM +0100, Chunfeng Yun wrote:
> add a DT binding documentation of xHCI host controller for the
> MT8173 SoC from Mediatek.
> 
> Signed-off-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
> ---
>  .../devicetree/bindings/usb/mt8173-xhci.txt        | 50 ++++++++++++++++++++++
>  1 file changed, 50 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/usb/mt8173-xhci.txt
> 
> diff --git a/Documentation/devicetree/bindings/usb/mt8173-xhci.txt b/Documentation/devicetree/bindings/usb/mt8173-xhci.txt
> new file mode 100644
> index 0000000..444494d
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/mt8173-xhci.txt
> @@ -0,0 +1,50 @@
> +MT65XX xhci
> +
> +The device node for Mediatek SOC usb3.0 host controller
> +
> +Required properties:
> + - compatible : supports "mediatek,mt8173-xhci"
> + - reg        : Offset and length of registers

Your example has multiple reg entries.

Please list what each entry is, and the order you expect them in.

> + - interrupts : Interrupt mode, number and trigger mode
> + - power-domains: to enable usb's mtcmos
> + - vusb33-supply:  regulator of usb avdd3.3v
> + - clocks     : must support all clocks that xhci needs
> + - clock-names: should be "sys_mac" for sys and mac clocks, and
> +	"wakeup_deb_p0", "wakeup_deb_p1" for wakeup debounce control
> +	clocks
> + - phys	: the phys that xhci will bind, currently supports up to two
> +	phys, so phy index should not greater than one.
> + - phy-names : should be "phy-X" format, X equals to 0 or 1

This seems somewhat pointless.

> + - usb3-lpm-capable: supports USB3 LPM
> + - mediatek,usb-wakeup: to access usb wakeup control register

What exactly does this property imply?

> + - mediatek,wakeup-src: 1: ip sleep wakeup mode; 2: line state wakeup
> +	mode; others means don't enable wakeup source of usb

This sounds like configuration rather than a hardware property. Why do
you think this needs to be in the DT?

> + - mediatek,u2port-num: the number should not greater than the number
> +	of phys

What exactly does this property imply?

Mark.

> +
> +Optional properties:
> + - vbus-supply : reference to the VBUS regulator;
> +
> +Example:
> +usb: usb30@11270000 {
> +	compatible = "mediatek,mt8173-xhci";
> +	reg = <0 0x11270000 0 0x4000>,
> +	      <0 0x11280000 0 0x0800>;
> +	interrupts = <GIC_SPI 115 IRQ_TYPE_LEVEL_LOW>;
> +	power-domains = <&scpsys MT8173_POWER_DOMAIN_USB>;
> +	clocks = <&topckgen CLK_TOP_USB30_SEL>,
> +		 <&pericfg CLK_PERI_USB0>,
> +		 <&pericfg CLK_PERI_USB1>;
> +	clock-names = "sys_mac",
> +		      "wakeup_deb_p0",
> +		      "wakeup_deb_p1";
> +	phys = <&u3phy 0>, <&u3phy 1>;
> +	phy-names = "phy-0", "phy-1";
> +	vusb33-supply = <&mt6397_vusb_reg>;
> +	vbus-supply = <&usb_p1_vbus>;
> +	usb3-lpm-capable;
> +	mediatek,usb-wakeup = <&pericfg>;
> +	mediatek,wakeup-src = <1>;
> +	mediatek,u2port-num = <2>;
> +	status = "okay";
> +};
> -- 
> 1.8.1.1.dirty
> 

  reply	other threads:[~2015-07-22 14:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22 14:05 (unknown), Chunfeng Yun
2015-07-22 14:05 ` [PATCH v3 1/5] dt-bindings: Add usb3.0 phy binding for MT65xx SoCs Chunfeng Yun
2015-07-22 14:05 ` [PATCH v3 2/5] dt-bindings: Add a binding for Mediatek xHCI host controller Chunfeng Yun
2015-07-22 14:22   ` Mark Rutland [this message]
2015-07-26  3:45     ` chunfeng yun
2015-07-31 13:37       ` Mark Rutland
2015-08-01  3:42         ` chunfeng yun
     [not found] ` <1437573945-31586-1-git-send-email-chunfeng.yun-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-07-22 14:05   ` [PATCH v3 3/5] usb: phy: add usb3.0 phy driver for mt65xx SoCs Chunfeng Yun
     [not found]     ` <1437573945-31586-4-git-send-email-chunfeng.yun-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-07-22 14:21       ` Felipe Balbi
     [not found]         ` <20150722142157.GA10467-HgARHv6XitJaoMGHk7MhZQC/G2K4zDHf@public.gmane.org>
2015-07-26  2:51           ` chunfeng yun
2015-07-28  5:47             ` Kishon Vijay Abraham I
2015-07-31 12:25               ` chunfeng yun
2015-07-31 14:18                 ` Kishon Vijay Abraham I
     [not found]                   ` <55BB83BF.6040105-l0cyMroinI0@public.gmane.org>
2015-08-01  2:42                     ` chunfeng yun
2015-07-27 13:58       ` Ricky Liang
     [not found]         ` <CAAJzSMe0dhg9Su_Lpjiq58ukQhairyasaDEK-tBiuTtNV8hygg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-31 12:32           ` chunfeng yun
2015-07-22 14:05   ` [PATCH v3 4/5] xhci: mediatek: support MTK xHCI host controller Chunfeng Yun
2015-07-22 14:05 ` [PATCH v3 5/5] arm64: dts: mediatek: add xHCI & usb phy for mt8173 Chunfeng Yun
2015-07-22 18:11   ` Sergei Shtylyov
     [not found]     ` <55AFDCE6.2060608-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2015-07-26  2:41       ` chunfeng yun
2015-07-23  1:18 ` [PATCH v3 0/5] Mediatek xHCI support chunfeng yun

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=20150722142208.GC15809@leverpostej \
    --to=mark.rutland@arm.com \
    --cc=balbi@ti.com \
    --cc=blogic@openwrt.org \
    --cc=chunfeng.yun@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=djkurtz@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=rogerq@ti.com \
    --cc=s.hauer@pengutronix.de \
    /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).