From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932567AbcFTQ07 (ORCPT ); Mon, 20 Jun 2016 12:26:59 -0400 Received: from mail-io0-f194.google.com ([209.85.223.194]:36424 "EHLO mail-io0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932250AbcFTQ0a (ORCPT ); Mon, 20 Jun 2016 12:26:30 -0400 Date: Mon, 20 Jun 2016 11:26:22 -0500 From: Rob Herring To: Neil Armstrong Cc: balbi@kernel.org, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [PATCH 2/2] dt-bindings: phy: Add qcom,usb-hsic-phy bindings Message-ID: <20160620162622.GA21783@rob-hp-laptop> References: <1466159119-20310-1-git-send-email-narmstrong@baylibre.com> <1466159119-20310-3-git-send-email-narmstrong@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1466159119-20310-3-git-send-email-narmstrong@baylibre.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 17, 2016 at 12:25:19PM +0200, Neil Armstrong wrote: > Signed-off-by: Neil Armstrong > --- > .../devicetree/bindings/phy/qcom,usb-hsic-phy.txt | 95 ++++++++++++++++++++++ > 1 file changed, 95 insertions(+) > create mode 100644 Documentation/devicetree/bindings/phy/qcom,usb-hsic-phy.txt > > diff --git a/Documentation/devicetree/bindings/phy/qcom,usb-hsic-phy.txt b/Documentation/devicetree/bindings/phy/qcom,usb-hsic-phy.txt > new file mode 100644 > index 0000000..79259a4 > --- /dev/null > +++ b/Documentation/devicetree/bindings/phy/qcom,usb-hsic-phy.txt > @@ -0,0 +1,95 @@ > +Qualcomm's MDM9615 USB HISC transceiver controller > + > +- compatible: > + Usage: required > + Value type: > + Definition: Should contain "qcom,usb-hsic-phy". SoC specific compatible string please. > + > +- reg: > + Usage: required > + Value type: > + Definition: USB PHY base address and length of the register map > + > +- clocks: > + Usage: required > + Value type: > + Definition: See clock-bindings.txt section "consumers". List of > + 5 clock specifiers for interface and core controller > + clocks. > + > +- clock-names: > + Usage: required > + Value type: > + Definition: Must contain "core", "alt-core", "phy", "cal" and "iface" strings. > + > +- vddcx-supply: > + Usage: required > + Value type: > + Definition: phandle to the regulator VDCCX supply node. > + > +- resets: > + Usage: required > + Value type: > + Definition: See reset.txt section "consumers". PHY reset specifier. > + > +- reset-names: > + Usage: required > + Value type: > + Definition: Must contain "link" string. > + > +- interrupts: > + Usage: required > + Value type: > + Definition: Interrupt line definition for the PHY > + > +- dr_mode: > + Usage: required > + Value type: > + Definition: Setup the PHY mode, either "host", "gadget" or "dual" > + > +- qcom,vdd-levels: > + Usage: required for MDM9615 > + Value type: > + Definition: Setup the valid vdd levers for the vddx-supply s/levers/levels/ There's not a common regulator property for this? > + > +- phy_type: > + Usage: required > + Value type: > + Definition: Shall be "hisc" typo > + > +- qcom,tlmm: > + Usage: required for MDM961 s/MDM961/MDM9615/ or drop because this binding is only for MDM9615. > + Value type: > + Definition: TLMM syscon phandle to setup the HSIC lines > + > +- qcom,tlmm-cfg: > + Usage: required for MDM961 s/MDM961/MDM9615/ > + Value type: > + Definition: Shall be two entries of offset, data of the HSIC lines setup This property is somewhat questionable with just magic register address and value to write...