From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Shaik Ameer Basha' <shaik.ameer@samsung.com>,
linux-samsung-soc@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org
Cc: sy0816.kang@samsung.com, olofj@google.com, thomas.ab@samsung.com,
sylvester.nawrocki@gmail.com, sachin.kamat@linaro.org,
joshi@samsung.com, shaik.samsung@gmail.com
Subject: RE: [PATCH v3 1/2] ARM: EXYNOS: Add clock support for Gscaler
Date: Wed, 01 Aug 2012 15:24:38 +0900 [thread overview]
Message-ID: <033101cd6fae$53b4c180$fb1e4480$%kim@samsung.com> (raw)
In-Reply-To: <1342789723-3949-2-git-send-email-shaik.ameer@samsung.com>
Shaik Ameer Basha wrote:
>
> Add required clock support for Gscaler for exynos5
>
> Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
> Signed-off-by: Leela Krishna Amudala <l.krishna@samsung.com>
> Signed-off-by: Prathyush K <prathyush.k@samsung.com>
> Signed-off-by: Shaik Ameer Basha <shaik.ameer@samsung.com>
> ---
> arch/arm/mach-exynos/clock-exynos5.c | 100
> ++++++++++++++++++++++++++++++++++
> 1 files changed, 100 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-exynos/clock-exynos5.c b/arch/arm/mach-
> exynos/clock-exynos5.c
> index 774533c..49a76b1 100644
> --- a/arch/arm/mach-exynos/clock-exynos5.c
> +++ b/arch/arm/mach-exynos/clock-exynos5.c
> @@ -552,6 +552,81 @@ static struct clksrc_clk exynos5_clk_aclk_66 = {
> .reg_div = { .reg = EXYNOS5_CLKDIV_TOP0, .shift = 0, .size = 3 },
> };
>
> +/* for aclk_300_gscl_mid */
No need above comment which is certain.
> +static struct clksrc_clk exynos5_clk_mout_aclk_300_gscl_mid = {
> + .clk = {
> + .name = "mout_aclk_300_gscl_mid",
> + },
> + .sources = &exynos5_clkset_aclk,
> + .reg_src = { .reg = EXYNOS5_CLKSRC_TOP0, .shift = 24, .size = 1 },
> +};
> +
> +/* for aclk_300_gscl_mid1 */
Same as above.
> +static struct clk *exynos5_clkset_aclk_300_gscl_mid1_list[] = {
> + [0] = &exynos5_clk_sclk_vpll.clk,
> + [1] = &exynos5_clk_mout_cpll.clk,
> +};
In this case, the above sources can be used for gscl_mid1 and disp1_mid as
well. So how about exynos5_clkset_mid1_list?
> +
> +static struct clksrc_sources exynos5_clkset_aclk_300_gscl_mid1 = {
> + .sources = exynos5_clkset_aclk_300_gscl_mid1_list,
> + .nr_sources =
ARRAY_SIZE(exynos5_clkset_aclk_300_gscl_mid1_list),
> +};
If so, need to update this.
> +
> +
no need double empty lines.
> +static struct clksrc_clk exynos5_clk_mout_aclk_300_gscl_mid1 = {
> + .clk = {
> + .name = "mout_aclk_300_gscl_mid1",
> + },
> + .sources = &exynos5_clkset_aclk_300_gscl_mid1,
> + .reg_src = { .reg = EXYNOS5_CLKSRC_TOP1, .shift = 12, .size = 1 },
> +};
> +
> +/* for aclk_300_gscl */
no need useless comment.
> +static struct clk *exynos5_clkset_aclk_300_gscl_list[] = {
> + [0] = &exynos5_clk_mout_aclk_300_gscl_mid.clk,
> + [1] = &exynos5_clk_mout_aclk_300_gscl_mid1.clk,
> +};
> +
> +static struct clksrc_sources exynos5_clkset_aclk_300_gscl = {
> + .sources = exynos5_clkset_aclk_300_gscl_list,
> + .nr_sources = ARRAY_SIZE(exynos5_clkset_aclk_300_gscl_list),
> +};
> +
> +static struct clksrc_clk exynos5_clk_mout_aclk_300_gscl = {
> + .clk = {
^^^^
Tap please.
> + .name = "mout_aclk_300_gscl",
> + },
> + .sources = &exynos5_clkset_aclk_300_gscl,
> + .reg_src = { .reg = EXYNOS5_CLKSRC_TOP0, .shift = 25, .size = 1 },
> +};
> +
> +static struct clksrc_clk exynos5_clk_dout_aclk_300_gscl = {
> + .clk = {
^^^^
Same as above.
> + .name = "dout_aclk_300_gscl",
> + .parent = &exynos5_clk_mout_aclk_300_gscl.clk,
> + },
> + .reg_div = { .reg = EXYNOS5_CLKDIV_TOP1, .shift = 12, .size = 3 },
> +};
And I think, we don't need to define above 'clksrc_clk's?
+static struct clksrc_clk exynos5_clk_mdout_aclk_300_gscl = {
+ .clk = {
+ .name = "mdout_aclk_300_gscl",
+ },
+ .sources = &exynos5_clkset_aclk_300_gscl,
+ .reg_src = { .reg = EXYNOS5_CLKSRC_TOP0, .shift = 25, .size = 1 },
> + .reg_div = { .reg = EXYNOS5_CLKDIV_TOP1, .shift = 12, .size = 3 },
+};
[...]
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
next prev parent reply other threads:[~2012-08-01 6:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 13:08 [PATCH v3 0/2] Add device tree and clock support for Gscaler Shaik Ameer Basha
2012-07-20 13:08 ` [PATCH v3 1/2] ARM: EXYNOS: Add " Shaik Ameer Basha
2012-08-01 6:24 ` Kukjin Kim [this message]
2012-08-01 7:07 ` Shaik Ameer Basha
2012-07-20 13:08 ` [PATCH v3 2/2] ARM: EXYNOS: Add Gscaler device from DT Shaik Ameer Basha
2012-08-01 6:40 ` Kukjin Kim
2012-08-01 7:10 ` Shaik Ameer Basha
2012-08-01 7:48 ` Thomas Abraham
2012-08-01 8:15 ` Kukjin Kim
2012-08-01 8:18 ` Sylwester Nawrocki
2012-08-01 9:00 ` Kukjin Kim
2012-08-01 19:03 ` Sylwester Nawrocki
[not found] ` <50197D66.1050108-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-08-02 16:33 ` Olof Johansson
2012-08-02 23:40 ` Sylwester Nawrocki
2012-08-06 6:27 ` Shaik Ameer Basha
2012-08-06 19:09 ` Sylwester Nawrocki
2012-08-07 10:01 ` Kukjin Kim
2012-08-11 4:08 ` Kukjin Kim
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='033101cd6fae$53b4c180$fb1e4480$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=joshi@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olofj@google.com \
--cc=sachin.kamat@linaro.org \
--cc=shaik.ameer@samsung.com \
--cc=shaik.samsung@gmail.com \
--cc=sy0816.kang@samsung.com \
--cc=sylvester.nawrocki@gmail.com \
--cc=thomas.ab@samsung.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 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).