All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Doug Anderson <dianders@chromium.org>
Cc: Elaine Zhang <zhangqing@rock-chips.com>,
	Caesar Wang <wxt@rock-chips.com>,
	Tao Huang <huangtao@rock-chips.com>, xxx <xxx@rock-chips.com>,
	Xu Jianqun <jay.xu@rock-chips.com>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Xing Zheng <zhengxing@rock-chips.com>
Subject: Re: [PATCH] power-domain: rockchip: fix up the PMU_GPU_PWRDW/UP_CNT for RK3399
Date: Mon, 26 Sep 2016 17:25:49 +0200	[thread overview]
Message-ID: <6388447.xfRkPC5TP9@phil> (raw)
In-Reply-To: <CAD=FV=VeZj0u9Phqv4V5s4aJ73R57+tZbKz40rbMkMLPkkArCw@mail.gmail.com>

Am Montag, 26. September 2016, 08:17:54 CEST schrieb Doug Anderson:
> Hi,
> 
> On Mon, Sep 26, 2016 at 12:25 AM, Elaine Zhang <zhangqing@rock-chips.com> 
wrote:
> > According to the advice of the IC,
> > setting the PMU_GPU_PWRDW/PWRUP_CNT regs 6 cycel(250ns) for RK3399 SOC.
> > 
> > Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
> > ---
> > 
> >  drivers/soc/rockchip/pm_domains.c | 8 ++++----
> >  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> This has problems on several levels.  Please see
> <https://patchwork.kernel.org/patch/9288607/> for some context.
> 
> Note that ATF changes have landed, so my patch could probably land at any
> time.

thanks for the heads up. As before I still agree with you that this is better 
done in the ATF, so I guess I can merge your other patch for 4.10 now.


Heiko

      reply	other threads:[~2016-09-26 15:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-26  7:25 [PATCH] power-domain: rockchip: fix up the PMU_GPU_PWRDW/UP_CNT for RK3399 Elaine Zhang
2016-09-26 15:17 ` Doug Anderson
2016-09-26 15:25   ` Heiko Stuebner [this message]

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=6388447.xfRkPC5TP9@phil \
    --to=heiko@sntech.de \
    --cc=dianders@chromium.org \
    --cc=huangtao@rock-chips.com \
    --cc=jay.xu@rock-chips.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=wxt@rock-chips.com \
    --cc=xxx@rock-chips.com \
    --cc=zhangqing@rock-chips.com \
    --cc=zhengxing@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.