From: Mike Turquette <mturquette@linaro.org>
To: Tushar Behera <tushar.behera@linaro.org>,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Cc: kgene.kim@samsung.com, tomasz.figa@gmail.com, patches@linaro.org
Subject: Re: [PATCH v2 0/2] Clock update for EXYNOS4210-CPUFREQ driver
Date: Fri, 21 Jun 2013 10:44:53 -0700 [thread overview]
Message-ID: <20130621174453.20448.59791@quantum> (raw)
In-Reply-To: <1371725238-25437-1-git-send-email-tushar.behera@linaro.org>
Quoting Tushar Behera (2013-06-20 03:47:16)
> cpufreq driver for EXYNOS4 based SoCs are not platform drivers, hence
> we cannot currently pass the clock names through a device tree node.
> Instead, we need to make them available through global alias.
>
> The patches are based on next-20130618.
>
> Patch 1 has not been modified.
> Patch 2 has been updated to include EXYNOS4X12 releated clocks.
Patch and changelogs look good to me now. Tomasz, any comments? I am
happy to take these into clk-next with your review.
Regards,
Mike
>
> Tushar Behera (2):
> clk: samsung: Add MUX_FA macro to pass flag and alias
> clk: exynos4: Fix clock aliases for cpufreq related clocks
>
> drivers/clk/samsung/clk-exynos4.c | 21 +++++++++++----------
> drivers/clk/samsung/clk.h | 3 +++
> 2 files changed, 14 insertions(+), 10 deletions(-)
>
> --
> 1.7.9.5
next prev parent reply other threads:[~2013-06-21 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 10:47 [PATCH v2 0/2] Clock update for EXYNOS4210-CPUFREQ driver Tushar Behera
2013-06-20 10:47 ` [PATCH RESEND 1/2] clk: samsung: Add MUX_FA macro to pass flag and alias Tushar Behera
2013-06-20 10:47 ` [PATCH v2 2/2] clk: exynos4: Fix clock aliases for cpufreq related clocks Tushar Behera
2013-06-21 17:44 ` Mike Turquette [this message]
2013-06-22 11:30 ` [PATCH v2 0/2] Clock update for EXYNOS4210-CPUFREQ driver Tomasz Figa
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=20130621174453.20448.59791@quantum \
--to=mturquette@linaro.org \
--cc=kgene.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=patches@linaro.org \
--cc=tomasz.figa@gmail.com \
--cc=tushar.behera@linaro.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 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.