public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: hl@rock-chips.com (hl)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/2] clk: rockchip: add pclk_pd_pmu to the list of rk3288 critical clocks
Date: Fri, 07 Aug 2015 17:41:45 +0800	[thread overview]
Message-ID: <55C47D59.8080403@rock-chips.com> (raw)
In-Reply-To: <1438939872-2116-1-git-send-email-hl@rock-chips.com>

Hi Heiko,
> pclk_pd_pmu needs to keep running and with the upcoming gpio clock
> handling this is not always the case anymore. So add it to the list
> of critical clocks for now.
>
> From: Heiko Stuebner <heiko@sntech.de>
> Signed-off-by: Lin Huang <hl@rock-chips.com>
     is it the right way?  if it still can not meet the requirement, 
please let me know.
> ---
> Changes in v4:
> - Add From: Heiko Stuebner <heiko@sntech.de>
>
>   drivers/clk/rockchip/clk-rk3288.c | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/drivers/clk/rockchip/clk-rk3288.c b/drivers/clk/rockchip/clk-rk3288.c
> index 0df5bae..9040878 100644
> --- a/drivers/clk/rockchip/clk-rk3288.c
> +++ b/drivers/clk/rockchip/clk-rk3288.c
> @@ -780,6 +780,7 @@ static const char *const rk3288_critical_clocks[] __initconst = {
>   	"aclk_cpu",
>   	"aclk_peri",
>   	"hclk_peri",
> +	"pclk_pd_pmu",
>   };
>   
>   #ifdef CONFIG_PM_SLEEP

  parent reply	other threads:[~2015-08-07  9:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07  9:31 [PATCH v4 1/2] clk: rockchip: add pclk_pd_pmu to the list of rk3288 critical clocks Lin Huang
2015-08-07  9:31 ` [PATCH v4 2/2] pinctrl: rockchip: only enable gpio clock when it setting Lin Huang
2015-08-07  9:41 ` hl [this message]
2015-08-07 11:36   ` [PATCH v4 1/2] clk: rockchip: add pclk_pd_pmu to the list of rk3288 critical clocks Heiko Stübner

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=55C47D59.8080403@rock-chips.com \
    --to=hl@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.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