From: Doug Anderson <dianders@chromium.org>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Caesar Wang <wxt@rock-chips.com>,
Heiko Stuebner <heiko@sntech.de>, Lin Huang <hl@rock-chips.com>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Derek Basehore <dbasehore@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>,
Ryan Case <ryandcase@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Elaine Zhang <zhangqing@rock-chips.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"nickey.yang (nickey.yang@rock-chips.com)"
<nickey.yang@rock-chips.com>, wzz <wzz@rock-chips.com>,
Huang Jiachai <hjc@rock-chips.com>
Subject: Re: [PATCH] phy: rockchip-dp: Avoid power leak by leaving the PHY power on
Date: Mon, 3 Jun 2019 08:23:35 -0700 [thread overview]
Message-ID: <CAD=FV=XfxT+GB=WvuGm68SaUWhSg7vS5AjQ-sv9e5wdKN7sFjQ@mail.gmail.com> (raw)
In-Reply-To: <CAD=FV=Us1WyEqYDqVSuA+QPCDU7ceMEwwaWKtLz9ZNBFD0E7NQ@mail.gmail.com>
Hi,
On Mon, Jun 3, 2019 at 8:22 AM Doug Anderson <dianders@chromium.org> wrote:
> > Can someone in Rockchip try to find the root-cause of the issue? Keeping the
> > PHY off shouldn't increase power draw.
>
> It sounded like Chris already answered this, though? Basically things
Doh! Don't know why I said Chris when it was clearly Caesar that
answered. Sorry Caesar!
-Doug
next prev parent reply other threads:[~2019-06-03 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 23:48 [PATCH] phy: rockchip-dp: Avoid power leak by leaving the PHY power on Douglas Anderson
2019-05-17 23:57 ` Doug Anderson
2019-05-18 7:51 ` Heiko Stuebner
2019-05-18 13:42 ` Doug Anderson
2019-05-20 8:04 ` Caesar Wang
2019-06-03 11:20 ` Kishon Vijay Abraham I
2019-06-03 15:22 ` Doug Anderson
2019-06-03 15:23 ` Doug Anderson [this message]
2019-07-22 21:52 ` Doug Anderson
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='CAD=FV=XfxT+GB=WvuGm68SaUWhSg7vS5AjQ-sv9e5wdKN7sFjQ@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=dbasehore@chromium.org \
--cc=groeck@chromium.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=hl@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=mka@chromium.org \
--cc=nickey.yang@rock-chips.com \
--cc=ryandcase@chromium.org \
--cc=wxt@rock-chips.com \
--cc=wzz@rock-chips.com \
--cc=zhangqing@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;
as well as URLs for NNTP newsgroup(s).