devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: balbi@ti.com, linux-usb@vger.kernel.org, robh+dt@kernel.org,
	pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	grant.likely@linaro.org, devicetree@vger.kernel.org,
	gregkh@linuxfoundation.org, linux-sh@vger.kernel.org,
	valentine.barshak@cogentembedded.com, rob@landley.net,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] phy-rcar-gen2-usb: add device tree support
Date: Mon, 3 Mar 2014 10:54:01 -0600	[thread overview]
Message-ID: <20140303165401.GF10987@saruman.home> (raw)
In-Reply-To: <5314C0E9.2020202@cogentembedded.com>

[-- Attachment #1: Type: text/plain, Size: 2722 bytes --]

Hi,

On Mon, Mar 03, 2014 at 08:50:33PM +0300, Sergei Shtylyov wrote:
> Hello.
> 
> On 03/03/2014 07:44 PM, Felipe Balbi wrote:
> 
> >>Add support of the device tree probing for the Renesas R-Car generation 2 SoCs
> >>documenting the device tree binding as necessary.
> 
> >>Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> 
> >Unless someone on devicetree@vger gives me an ACK pretty soon, I'm
> >afraid this patch will miss v3.15.
> 
>    Ugh, the USB acceptance window is getting very short...

well, -rc5 is already out... I want to have at least 2 weeks of
"linux-next soakage" (yes, I just coined a new term heh). Since most
releases go up to -rc7, it's about time to close the tree ;-)

> >>---
> >>This patch is against the 'next' branch of Felipe Balbi's 'usb.git' repo.
> >>
> >>Changes in version 2:
> >>- restored devm_clk_get() call and the error handling logic in the probe()
> >>   method, removed clk_put() call in the remove() method.
> 
> >>  Documentation/devicetree/bindings/usb/rcar-gen2-phy.txt |   29 +++++++++++
> >>  drivers/usb/phy/phy-rcar-gen2-usb.c                     |   42 ++++++++++++++--
> >>  2 files changed, 68 insertions(+), 3 deletions(-)
> 
> >>Index: usb/Documentation/devicetree/bindings/usb/rcar-gen2-phy.txt
> >>===================================================================
> >>--- /dev/null
> >>+++ usb/Documentation/devicetree/bindings/usb/rcar-gen2-phy.txt
> >>@@ -0,0 +1,29 @@
> >>+* Renesas R-Car generation 2 USB PHY
> >>+
> >>+This file provides information on what the device node for the R-Car generation
> >>+2 USB PHY contains.
> >>+
> >>+Required properties:
> >>+- compatible: "renesas,usb-phy-r8a7790" if the device is a part of R8A7790 SoC.
> >>+	      "renesas,usb-phy-r8a7791" if the device is a part of R8A7791 SoC.
> >>+- reg: offset and length of the register block.
> >>+- clocks: clock phandle and specifier pair.
> >>+- clock-names: string, clock input name, must be "usbhs".
> >>+
> >>+Optional properties:
> >>+- renesas,channel0-pci: boolean, specify when USB channel 0 should be connected
> >>+			to PCI EHCI/OHCI; otherwise, it will be connected to the
> >>+			USBHS controller.
> >>+- renesas,channel2-pci: boolean, specify when USB channel 2 should be connected
> >>+			to PCI EHCI/OHCI; otherwise, it will be connected to the
> >>+			USBSS controller (xHCI).
> 
> >I wonder if these two properties should be taken care by pinctrl
> >framework instead.
> 
>    No, the internal port multiplexing is controlled by the PHY
> itself, see the driver source. The same way it was with USB port 1 of
> the generation 1 R-Car SoCs.

ok, fair enough.

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-03-03 16:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-01  1:07 [PATCH v2] phy-rcar-gen2-usb: add device tree support Sergei Shtylyov
2014-03-03 16:44 ` Felipe Balbi
2014-03-03 17:50   ` Sergei Shtylyov
2014-03-03 16:54     ` Felipe Balbi [this message]
2014-03-06 19:39   ` Sergei Shtylyov
2014-03-06 18:52     ` Ben Dooks
2014-03-07  5:46 ` Magnus Damm
2014-03-07 14:27   ` Sergei Shtylyov
2014-03-07 23:57     ` Sergei Shtylyov
2014-03-10 11:00       ` Magnus Damm
2014-03-11 23:32         ` Sergei Shtylyov

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=20140303165401.GF10987@saruman.home \
    --to=balbi@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=grant.likely@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=rob@landley.net \
    --cc=robh+dt@kernel.org \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=valentine.barshak@cogentembedded.com \
    /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).