From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] clk: samsung: Add CLKOUT driver support for Exynos3250 SoC.
Date: Wed, 11 Mar 2015 16:34:50 -0700 [thread overview]
Message-ID: <5500D11A.6010200@codeaurora.org> (raw)
In-Reply-To: <1425262500-27456-1-git-send-email-ideal.song@samsung.com>
On 03/01/15 18:15, Inha Song wrote:
> This patch add CLKOUT driver support for Exynos3250 SoC.
>
> Exynos3250 SoC PMU_DEBUG is the same with Exynos4's PMU_DEBUG
> including CLKOUT mux. So, We can use the exynos4's clkout init
> function for Exynos3250 without the need to add new function.
>
> Signed-off-by: Inha Song <ideal.song@samsung.com>
Do you want to take this through some SoC tree? If so:
Acked-by: Stephen Boyd <sboyd@codeaurora.org>
> ---
> drivers/clk/samsung/clk-exynos-clkout.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/clk/samsung/clk-exynos-clkout.c b/drivers/clk/samsung/clk-exynos-clkout.c
> index 3a7cb25..1c02e73 100644
> --- a/drivers/clk/samsung/clk-exynos-clkout.c
> +++ b/drivers/clk/samsung/clk-exynos-clkout.c
> @@ -142,6 +142,8 @@ CLK_OF_DECLARE(exynos4212_clkout, "samsung,exynos4212-pmu",
> exynos4_clkout_init);
> CLK_OF_DECLARE(exynos4412_clkout, "samsung,exynos4412-pmu",
> exynos4_clkout_init);
> +CLK_OF_DECLARE(exynos3250_clkout, "samsung,exynos3250-pmu",
> + exynos4_clkout_init);
>
> static void __init exynos5_clkout_init(struct device_node *node)
> {
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-03-11 23:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 2:15 [PATCH v2] clk: samsung: Add CLKOUT driver support for Exynos3250 SoC Inha Song
2015-03-11 23:34 ` Stephen Boyd [this message]
2015-03-17 10:54 ` Sylwester Nawrocki
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=5500D11A.6010200@codeaurora.org \
--to=sboyd@codeaurora.org \
--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;
as well as URLs for NNTP newsgroup(s).