From: Heiko Stuebner <heiko@sntech.de>
To: Chris Zhong <zyw@rock-chips.com>
Cc: kishon@ti.com, groeck@chromium.org, wulf@rock-chips.com,
briannorris@chromium.org, dianders@chromium.org,
kever.yang@rock-chips.com, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
David Wu <david.wu@rock-chips.com>,
Jianqun Xu <jay.xu@rock-chips.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-kernel@vger.kernel.org, Will Deacon <will.deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [PATCH v2 2/2] arm64: dts: rk3399: add powerdomain for typec
Date: Thu, 08 Sep 2016 17:16:12 +0200 [thread overview]
Message-ID: <1502775.CkB0Rhdvgx@phil> (raw)
In-Reply-To: <1473289577-14101-2-git-send-email-zyw@rock-chips.com>
Am Mittwoch, 7. September 2016, 16:06:17 CEST schrieb Chris Zhong:
> The tcpc power domain will try to power up/down the power of Type-C PHY.
> Hence, we need control it in Type-C PHY driver with the pm_runtime helper.
>
> Signed-off-by: Chris Zhong <zyw@rock-chips.com>
applied to my dts64 branch for 4.9 (or 4.10) after fixing the subject
(rockchip: instead of rk3399:), as even without the advanced logic from patch1
the driver core will already make sure to at least powerup the domain before
probe and power-down after remove.
Heiko
next prev parent reply other threads:[~2016-09-08 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 23:06 [PATCH v2 1/2] phy: rockchip-typec: add pm runtime support Chris Zhong
2016-09-07 23:06 ` [PATCH v2 2/2] arm64: dts: rk3399: add powerdomain for typec Chris Zhong
2016-09-08 15:16 ` Heiko Stuebner [this message]
2016-09-08 5:24 ` [PATCH v2 1/2] phy: rockchip-typec: add pm runtime support Kishon Vijay Abraham I
2016-09-08 5:57 ` [RESEND PATCH v3 " Chris Zhong
2016-09-08 15:31 ` Guenter Roeck
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=1502775.CkB0Rhdvgx@phil \
--to=heiko@sntech.de \
--cc=briannorris@chromium.org \
--cc=catalin.marinas@arm.com \
--cc=david.wu@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=groeck@chromium.org \
--cc=jay.xu@rock-chips.com \
--cc=kever.yang@rock-chips.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 \
--cc=will.deacon@arm.com \
--cc=wulf@rock-chips.com \
--cc=yamada.masahiro@socionext.com \
--cc=zyw@rock-chips.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