From: Michael Turquette <mturquette@baylibre.com>
To: Michael Niewoehner <linux@mniewoehner.de>,
Cc: Heiko Stuebner <heiko@sntech.de>,
linus.walleij@linaro.org, sboyd@codeaurora.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] clk: rockchip: add pclk_cpu to the list of rk3188 critical clocks
Date: Thu, 27 Aug 2015 09:52:44 -0700 [thread overview]
Message-ID: <20150827165244.30921.8929@quantum> (raw)
In-Reply-To: <8804658D-175F-4668-BC12-4AC439438B61@mniewoehner.de>
Quoting Michael Niewoehner (2015-08-25 13:22:07)
> pclk_cpu needs to keep running because it is needed for devices like
> the act8865 regulator but with the recent gpio clock handling this is
> not always the case anymore. So add it to the list of critical clocks.
>
> Signed-off-by: Michael Niewoehner <linux@mniewoehner.de>
> Reviewed-by: Heiko Stuebner <heiko@sntech.de>
Acked-by: Michael Turquette <mturquette@baylibre.com>
This patch applies cleanly to clk-next, so I guess the patch formatting
issues have been resolved ;-)
Note that I did NOT apply this to the clk tree, just locally for
testing.
Regards,
Mike
> ---
> Changes in v3:
> - fix git format-patch problem
>
> Changes in v2:
> - adapt commit message
> - add Linus Walleij to recipients, as the patch is related to the gpio clock
> change in the rockchip pinctrl driver it should go through his tree as well
>
> drivers/clk/rockchip/clk-rk3188.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/clk/rockchip/clk-rk3188.c b/drivers/clk/rockchip/clk-rk3188.c
> index ed02bbc..f63a642 100644
> --- a/drivers/clk/rockchip/clk-rk3188.c
> +++ b/drivers/clk/rockchip/clk-rk3188.c
> @@ -716,6 +716,7 @@ static const char *const rk3188_critical_clocks[] __initconst = {
> "aclk_cpu",
> "aclk_peri",
> "hclk_peri",
> + "pclk_cpu",
> };
>
> static void __init rk3188_common_clk_init(struct device_node *np)
> --
> 2.5.0
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2015-08-27 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 17:38 [PATCH] clk: rockchip: add pclk_cpu to the list of rk3188 critical clocks Michael Niewoehner
2015-08-17 18:01 ` Heiko Stuebner
2015-08-17 18:51 ` Michael Niewoehner
2015-08-17 19:37 ` Heiko Stuebner
2015-08-17 19:50 ` [PATCH v2] " Michael Niewoehner
2015-08-17 19:55 ` Heiko Stuebner
2015-08-25 18:59 ` Michael Turquette
2015-08-25 20:17 ` Heiko Stuebner
2015-08-25 20:22 ` [PATCH v3] " Michael Niewoehner
2015-08-27 16:52 ` Michael Turquette [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=20150827165244.30921.8929@quantum \
--to=mturquette@baylibre.com \
--cc=heiko@sntech.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@mniewoehner.de \
--cc=sboyd@codeaurora.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;
as well as URLs for NNTP newsgroup(s).