From: Heiko Stuebner <heiko@sntech.de>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: linux-kernel@vger.kernel.org, amstan@chromium.org,
groeck@google.com, kieran.bingham@ideasonboard.com,
kernel@collabora.com, bleung@chromium.org,
devicetree@vger.kernel.org,
Frank Wang <frank.wang@rock-chips.com>,
linux-rockchip@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 4/4] dt-bindings: phy-rockchip-inno-usb2: add new rockchip,force-bvalid property.
Date: Wed, 15 Aug 2018 12:34:34 +0200 [thread overview]
Message-ID: <6944969.kWmPjI4VuS@phil> (raw)
In-Reply-To: <20180815095934.11205-5-enric.balletbo@collabora.com>
Am Mittwoch, 15. August 2018, 11:59:34 CEST schrieb Enric Balletbo i Serra:
> 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@collabora.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"
I guess you could drop that rk3399 mention instead make the
driver complain? Trying to keep that list up to date will get hard
and I guess the other socs may very well hide that setting somewhere
in their undocumented phy registers as well.
I guess a bit of alphabetical ordering might also be nice,
rockchip,force-bvalid above rockchip,utmi-avalid
Makes it easier to read ;-)
Heiko
next prev parent reply other threads:[~2018-08-15 10:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 9:59 [PATCH 0/4] phy: rockchip-inno-usb2: document improvements and allow to force B-device valid session bit Enric Balletbo i Serra
2018-08-15 9:59 ` [PATCH 1/4] phy: rockchip-inno-usb2: fix misspelling and kernel-doc documentation Enric Balletbo i Serra
2018-08-15 10:31 ` Heiko Stuebner
2019-01-08 17:35 ` Enric Balletbo Serra
2019-01-08 17:38 ` Heiko Stübner
2018-08-15 9:59 ` [PATCH 2/4] dt-bindings: phy-rockchip-inno-usb2: add documentation for extcon and utmi-avalid properties Enric Balletbo i Serra
2018-08-15 10:29 ` Heiko Stuebner
2018-08-15 11:08 ` Enric Balletbo i Serra
2018-08-15 11:22 ` Heiko Stuebner
2018-08-15 22:21 ` Rob Herring
2018-08-16 8:38 ` Enric Balletbo i Serra
2018-08-15 9:59 ` [PATCH 3/4] phy: rockchip-inno-usb2: allow to force the B-Device Session Valid bit Enric Balletbo i Serra
2018-08-15 10:18 ` Heiko Stuebner
2018-08-15 10:34 ` Enric Balletbo i Serra
2018-08-15 10:36 ` Heiko Stuebner
2018-08-15 9:59 ` [PATCH 4/4] dt-bindings: phy-rockchip-inno-usb2: add new rockchip,force-bvalid property Enric Balletbo i Serra
2018-08-15 10:34 ` Heiko Stuebner [this message]
2018-08-15 22:26 ` Rob Herring
2019-01-10 9:06 ` Enric Balletbo Serra
2019-01-10 12:31 ` Heiko Stuebner
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=6944969.kWmPjI4VuS@phil \
--to=heiko@sntech.de \
--cc=amstan@chromium.org \
--cc=bleung@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=frank.wang@rock-chips.com \
--cc=groeck@google.com \
--cc=kernel@collabora.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).