[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180815222604.GB8193@rob-hp-laptop>
Date: Wed, 15 Aug 2018 16:26:04 -0600
From: Rob Herring <robh@...nel.org>
To: Enric Balletbo i Serra <enric.balletbo@...labora.com>
Cc: linux-kernel@...r.kernel.org, amstan@...omium.org,
groeck@...gle.com, kieran.bingham@...asonboard.com,
kernel@...labora.com, bleung@...omium.org, heiko@...ech.de,
devicetree@...r.kernel.org, Frank Wang <frank.wang@...k-chips.com>,
linux-rockchip@...ts.infradead.org,
Kishon Vijay Abraham I <kishon@...com>,
Mark Rutland <mark.rutland@....com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 4/4] dt-bindings: phy-rockchip-inno-usb2: add new
rockchip,force-bvalid property.
On Wed, Aug 15, 2018 at 11:59:34AM +0200, Enric Balletbo i Serra wrote:
> This property is used when the otg-id pin is not connected. When this
> property is set it forces to set the B-Device Session Valid bit when the
> port works as device and clears that bit when the port works as host.
>
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@...labora.com>
> ---
>
> .../devicetree/bindings/phy/phy-rockchip-inno-usb2.txt | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt b/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt
> index 2d4808d3920b..55761f466c41 100644
> --- a/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt
> +++ b/Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt
> @@ -48,6 +48,11 @@ Optional properties:
> See ./phy-bindings.txt for details.
> - rockchip,utmi-avalid : boolean, use the avalid register to get vbus status.
> Otherwise, use the bvalid register.
> + - rockchip,force-bvalid : boolean, set this to force the B-Device Session
> + Valid bit when the usb port is in device mode. This
> + is used when the otg-id pin is not connected.
> + Only supported in case of compatible being:
> + * "rockchip,rk3399-usb2phy"
Shouldn't you describe the property of the h/w that ID pin is not
connected, rather than what you do with that information.
Is the pin not connected because it's a connector without ID pin? If so,
that should be a property of the connector (or inferred from the
connector compatible string).
Rob
Powered by blists - more mailing lists