LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sean Paul <seanpaul@chromium.org>
To: Lin Huang <hl@rock-chips.com>
Cc: seanpaul@chromium.org, airlied@linux.ie, zyw@rock-chips.com,
dianders@chromium.org, briannorris@chromium.org,
linux-rockchip@lists.infradead.org, heiko@sntech.de,
daniel.vetter@intel.com, jani.nikula@linux.intel.com,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, eballetbo@gmail.com,
robh+dt@kernel.org
Subject: Re: [PATCH v2 3/4] Documentation: bindings: add phy_config for Rockchip USB Type-C PHY
Date: Fri, 11 May 2018 10:43:05 -0400 [thread overview]
Message-ID: <20180511144305.GP33053@art_vandelay> (raw)
In-Reply-To: <1525861364-26323-3-git-send-email-hl@rock-chips.com>
On Wed, May 09, 2018 at 06:22:43PM +0800, Lin Huang wrote:
> If want to do training outside DP Firmware, need phy voltage swing
> and pre_emphasis value.
>
> Signed-off-by: Lin Huang <hl@rock-chips.com>
Adding Rob Herring so he has a hope of seeing this.
> ---
> Changes in v2:
> - rebase
>
> Documentation/devicetree/bindings/phy/phy-rockchip-typec.txt | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/phy/phy-rockchip-typec.txt b/Documentation/devicetree/bindings/phy/phy-rockchip-typec.txt
> index 960da7f..eda26dd 100644
> --- a/Documentation/devicetree/bindings/phy/phy-rockchip-typec.txt
> +++ b/Documentation/devicetree/bindings/phy/phy-rockchip-typec.txt
> @@ -17,7 +17,9 @@ Required properties:
>
> Optional properties:
> - extcon : extcon specifier for the Power Delivery
> -
> + - rockchip,phy_config : That's phy voltage swing and pre_emphasis
> + setting, if want to do dp training outside
> + dp firmware, need to add these value.
What are the units?
Sean
> Required nodes : a sub-node is required for each port the phy provides.
> The sub-node name is used to identify dp or usb3 port,
> and shall be the following entries:
> --
> 2.7.4
>
--
Sean Paul, Software Engineer, Google / Chromium OS
next prev parent reply other threads:[~2018-05-11 14:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 10:22 [PATCH v2 1/4] drm/rockchip: add transfer function for cdn-dp Lin Huang
2018-05-09 10:22 ` [PATCH v2 2/4] phy: rockchip-typec: support variable phy config value Lin Huang
2018-05-11 14:41 ` Sean Paul
2018-05-09 10:22 ` [PATCH v2 3/4] Documentation: bindings: add phy_config for Rockchip USB Type-C PHY Lin Huang
2018-05-11 14:43 ` Sean Paul [this message]
2018-05-11 16:09 ` Enric Balletbo Serra
2018-05-09 10:22 ` [PATCH v2 4/4] drm/rockchip: support dp training outside dp firmware Lin Huang
2018-05-11 15:01 ` Sean Paul
2018-05-11 14:35 ` [PATCH v2 1/4] drm/rockchip: add transfer function for cdn-dp Sean Paul
2018-05-11 16:40 ` Enric Balletbo Serra
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=20180511144305.GP33053@art_vandelay \
--to=seanpaul@chromium.org \
--cc=airlied@linux.ie \
--cc=briannorris@chromium.org \
--cc=daniel.vetter@intel.com \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eballetbo@gmail.com \
--cc=heiko@sntech.de \
--cc=hl@rock-chips.com \
--cc=jani.nikula@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=zyw@rock-chips.com \
--subject='Re: [PATCH v2 3/4] Documentation: bindings: add phy_config for Rockchip USB Type-C PHY' \
/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
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).