Linux Power Management development
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: Lukasz Luba <l.luba@partner.samsung.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Cc: b.zolnierkie@samsung.com, krzk@kernel.org, kgene@kernel.org,
	kyungmin.park@samsung.com, m.szyprowski@samsung.com,
	s.nawrocki@samsung.com, myungjoo.ham@samsung.com,
	keescook@chromium.org, tony@atomide.com, jroedel@suse.de,
	treding@nvidia.com, digetx@gmail.com,
	willy.mh.wolff.ml@gmail.com
Subject: Re: [PATCH v6 03/10] clk: samsung: add BPLL rate table for Exynos 5422 SoC
Date: Thu, 2 May 2019 14:15:57 +0900	[thread overview]
Message-ID: <62f85c18-d3ac-3425-8ee3-538f8c677603@samsung.com> (raw)
In-Reply-To: <1555683568-20882-4-git-send-email-l.luba@partner.samsung.com>

Hi Lukasz,

On 19. 4. 19. 오후 11:19, Lukasz Luba wrote:
> Add new table rate for BPLL for Exynos5422 SoC supporting Dynamic Memory
> Controller frequencies for driver's DRAM timings.
> 
> Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
> ---
>  drivers/clk/samsung/clk-exynos5420.c | 13 ++++++++++++-
>  1 file changed, 12 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/clk/samsung/clk-exynos5420.c b/drivers/clk/samsung/clk-exynos5420.c
> index d9e6653..ddee8bd 100644
> --- a/drivers/clk/samsung/clk-exynos5420.c
> +++ b/drivers/clk/samsung/clk-exynos5420.c
> @@ -1323,6 +1323,17 @@ static const struct samsung_pll_rate_table exynos5420_pll2550x_24mhz_tbl[] __ini
>  	PLL_35XX_RATE(24 * MHZ, 200000000,  200, 3, 3),
>  };
>  
> +static const struct samsung_pll_rate_table exynos5422_bpll_rate_table[] = {
> +	PLL_35XX_RATE(24 * MHZ, 825000000, 275, 4, 1),
> +	PLL_35XX_RATE(24 * MHZ, 728000000, 182, 3, 1),
> +	PLL_35XX_RATE(24 * MHZ, 633000000, 211, 4, 1),
> +	PLL_35XX_RATE(24 * MHZ, 543000000, 181, 2, 2),
> +	PLL_35XX_RATE(24 * MHZ, 413000000, 413, 6, 2),
> +	PLL_35XX_RATE(24 * MHZ, 275000000, 275, 3, 3),
> +	PLL_35XX_RATE(24 * MHZ, 206000000, 206, 3, 3),
> +	PLL_35XX_RATE(24 * MHZ, 165000000, 110, 2, 3),
> +};
> +
>  static const struct samsung_pll_rate_table exynos5420_epll_24mhz_tbl[] = {
>  	PLL_36XX_RATE(24 * MHZ, 600000000U, 100, 2, 1, 0),
>  	PLL_36XX_RATE(24 * MHZ, 400000000U, 200, 3, 2, 0),
> @@ -1465,7 +1476,7 @@ static void __init exynos5x_clk_init(struct device_node *np,
>  		exynos5x_plls[apll].rate_table = exynos5420_pll2550x_24mhz_tbl;
>  		exynos5x_plls[epll].rate_table = exynos5420_epll_24mhz_tbl;
>  		exynos5x_plls[kpll].rate_table = exynos5420_pll2550x_24mhz_tbl;
> -		exynos5x_plls[bpll].rate_table = exynos5420_pll2550x_24mhz_tbl;
> +		exynos5x_plls[bpll].rate_table = exynos5422_bpll_rate_table;

According to your previous reply, the released odroid-xu3 board by hardkernel
might be only CONFIG_SOC_EXYNOS5422_REV_0. Because the kernel configurattion
from hardkernel has 'CONFIG_SOC_EXYNOS5422_REV_0=y'. I'm ok about adding bpll rate_table.

But, just I have one question. I think that this bpll rate_table is for
only Exynos5422 series. Because the kernel of hardkernel used
driver/clk/samsung/clk-exynos5422.c instead of clk-exynos5420.c commonn driver.
It means that the clk-exynos5422.c of hardkernel's kernel support only Exynos5422
without any considering the Exynos5420 series. 

I think that it might need to check the soc version to use
bpll rate_table as following:

--- a/drivers/clk/samsung/clk-exynos5420.c
+++ b/drivers/clk/samsung/clk-exynos5420.c
@@ -1438,7 +1438,10 @@ static void __init exynos5x_clk_init(struct device_node *np,
                exynos5x_plls[apll].rate_table = exynos5420_pll2550x_24mhz_tbl;
                exynos5x_plls[epll].rate_table = exynos5420_epll_24mhz_tbl;
                exynos5x_plls[kpll].rate_table = exynos5420_pll2550x_24mhz_tbl;
-               exynos5x_plls[bpll].rate_table = exynos5422_bpll_rate_table;
+
+               if (soc == EXYNOS5800)
+                       exynos5x_plls[bpll].rate_table
+                               = exynos5422_bpll_rate_table;
        }


>  	}
>  
>  	samsung_clk_register_pll(ctx, exynos5x_plls, ARRAY_SIZE(exynos5x_plls),
> 


-- 
Best Regards,
Chanwoo Choi
Samsung Electronics

  parent reply	other threads:[~2019-05-02  5:15 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20190419141938eucas1p16ee6cdf897184df33cf67b55c5f3c449@eucas1p1.samsung.com>
2019-04-19 14:19 ` [PATCH v6 0/10] Exynos5 Dynamic Memory Controller driver Lukasz Luba
2019-04-19 14:19   ` Lukasz Luba
2019-04-19 14:19   ` [PATCH v6 01/10] clk: samsung: add needed IDs for DMC clocks in Exynos5420 Lukasz Luba
2019-04-19 14:19     ` Lukasz Luba
2019-04-30  4:47     ` Chanwoo Choi
2019-04-30  4:47       ` Chanwoo Choi
2019-04-30 12:36       ` Lukasz Luba
2019-04-30 12:36         ` Lukasz Luba
2019-04-19 14:19   ` [PATCH v6 02/10] clk: samsung: add new clocks for DMC for Exynos5422 SoC Lukasz Luba
2019-04-19 14:19     ` Lukasz Luba
2019-04-30  1:31     ` Chanwoo Choi
2019-04-30  1:31       ` Chanwoo Choi
2019-04-30 13:12       ` Lukasz Luba
2019-04-30 13:12         ` Lukasz Luba
2019-04-19 14:19   ` [PATCH v6 03/10] clk: samsung: add BPLL rate table for Exynos 5422 SoC Lukasz Luba
2019-04-19 14:19     ` Lukasz Luba
2019-05-02  5:15     ` Chanwoo Choi [this message]
2019-05-02  5:15       ` Chanwoo Choi
2019-05-02 14:23       ` Lukasz Luba
2019-05-02 14:23         ` Lukasz Luba
2019-04-19 14:19   ` [PATCH v6 04/10] Documentation: dt: device tree bindings for LPDDR3 memories Lukasz Luba
2019-04-19 14:19     ` Lukasz Luba
2019-04-25 19:51     ` Rob Herring
2019-04-25 19:51       ` Rob Herring
2019-04-29 12:04       ` Lukasz Luba
2019-04-29 12:04         ` Lukasz Luba
2019-04-29 16:36         ` Rob Herring
2019-04-29 16:36           ` Rob Herring
2019-04-30 20:04           ` Lukasz Luba
2019-04-30 20:04             ` Lukasz Luba
2019-04-25 19:53     ` Rob Herring
2019-04-25 19:53       ` Rob Herring
2019-04-29 12:05       ` Lukasz Luba
2019-04-29 12:05         ` Lukasz Luba
2019-04-19 14:19   ` [PATCH v6 05/10] drivers: memory: extend of_memory by LPDDR3 support Lukasz Luba
2019-04-19 14:19     ` Lukasz Luba
2019-04-19 14:19   ` [PATCH v6 06/10] dt-bindings: memory-controllers: add Exynos5422 DMC device description Lukasz Luba
2019-04-19 14:19     ` Lukasz Luba
2019-04-25 19:57     ` Rob Herring
2019-04-25 19:57       ` Rob Herring
2019-04-29 12:14       ` Lukasz Luba
2019-04-29 12:14         ` Lukasz Luba
2019-04-29 16:43         ` Rob Herring
2019-04-29 16:43           ` Rob Herring
2019-04-30 20:15           ` Lukasz Luba
2019-04-30 20:15             ` Lukasz Luba
2019-04-30  4:46     ` Chanwoo Choi
2019-04-30  4:46       ` Chanwoo Choi
2019-04-30 20:30       ` Lukasz Luba
2019-04-30 20:30         ` Lukasz Luba
2019-05-02  1:35         ` Chanwoo Choi
2019-05-02  1:35           ` Chanwoo Choi
2019-05-02 18:56           ` Lukasz Luba
2019-05-02 18:56             ` Lukasz Luba
2019-04-19 14:19   ` [PATCH v6 07/10] drivers: memory: add DMC driver for Exynos5422 Lukasz Luba
2019-04-19 14:19     ` Lukasz Luba
2019-04-23 11:27     ` Krzysztof Kozlowski
2019-04-23 11:27       ` Krzysztof Kozlowski
2019-04-29 14:51       ` Lukasz Luba
2019-04-29 14:51         ` Lukasz Luba
2019-04-19 14:19   ` [PATCH v6 08/10] drivers: devfreq: events: add Exynos PPMU new events Lukasz Luba
2019-04-19 14:19     ` Lukasz Luba
2019-04-19 14:19   ` [PATCH v6 09/10] ARM: dts: exynos: add DMC device for exynos5422 Lukasz Luba
2019-04-19 14:19     ` Lukasz Luba
2019-04-23 11:03     ` Krzysztof Kozlowski
2019-04-23 11:03       ` Krzysztof Kozlowski
2019-04-29 12:38       ` Lukasz Luba
2019-04-29 12:38         ` Lukasz Luba
2019-04-19 14:19   ` [PATCH v6 10/10] ARM: exynos_defconfig: enable DMC driver Lukasz Luba
2019-04-19 14:19     ` Lukasz Luba

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=62f85c18-d3ac-3425-8ee3-538f8c677603@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=digetx@gmail.com \
    --cc=jroedel@suse.de \
    --cc=keescook@chromium.org \
    --cc=kgene@kernel.org \
    --cc=krzk@kernel.org \
    --cc=kyungmin.park@samsung.com \
    --cc=l.luba@partner.samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=myungjoo.ham@samsung.com \
    --cc=s.nawrocki@samsung.com \
    --cc=tony@atomide.com \
    --cc=treding@nvidia.com \
    --cc=willy.mh.wolff.ml@gmail.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