Received: by 2002:ac0:8c9a:0:0:0:0:0 with SMTP id r26csp2473775ima; Sat, 2 Feb 2019 23:56:21 -0800 (PST) X-Google-Smtp-Source: AHgI3IYpeZiPYzzcAooqnqmx4ToAzyOifew3J6E4M7W/KCR4eXO/Rhoh4hNbi4nCu2VKHhlfUmoo X-Received: by 2002:a17:902:7c8a:: with SMTP id y10mr4185613pll.71.1549180581395; Sat, 02 Feb 2019 23:56:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549180581; cv=none; d=google.com; s=arc-20160816; b=SquLyOTaS461PJGFeNbGx8uCji+oIwTuZbFBG5gSwYb1itQZWK9WP8S6lsMU9kQhFq qA7609yEQ5312Y97LW+rqDg7aWb5hPhUCUG/Ojp0VwLdNJkGFTYo+XhIPtCpYIA9wDNg 1Ge12svBCd3xjr63AdKmlqnS1Fl0Hy945ow1Y0CeQU9Or9yfONKiYYIJxLGHkpfBEsDf Ncc7R6X+kwRoMNbXDB2W7C1aMt/wSgg5VpI1eHii6u7qQ2hyBEjFlKmQmW12w27Yn3jJ S+uH3xb6GR7yhYUUtLL5rgrpY7oj+zZAZQOdIqIjtp6Ru6/vyD/1VCwUw37uaKgwnck7 IkcA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:reply-to:in-reply-to:references:mime-version :dkim-signature; bh=BSnmeNvE3EBhH2SfbdbcYylaib6DqHpMf3vu6r4CZqc=; b=XMCxGvWD+ACrs34JIyCmFSebzABYc3IL8HS1fzs9AppWHeVWKt5X0SXLh0lqo/up7k oJZnya23oaGJh2arUuGE2KtVNuX4L21AFzK0ewxMcV+XdSEeTLs5KX5H0yicnS6OFryK ox2bAcEvlvlskjx4OmPK8t/9TOD9EkbkOsQteB4ITQ2hmp1I8wA1izXYsVelXRKgCEyd 3gBuVNBBp7NBLbcOjVqapnbHNAkKjDIXXOM+To/ReRdXEAgpEP9NKCGdGXtJkedGtJxX m70njhbcXt4oZ4MCSyrprP9KT53Gv9qVTVGCay4nPSDpKWjhrEOP0OYPBc2/j+Ym6LhG 2YcQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=eW2ZpxtX; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b61si5286785plb.70.2019.02.02.23.56.05; Sat, 02 Feb 2019 23:56:21 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=eW2ZpxtX; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727273AbfBCHyr (ORCPT + 99 others); Sun, 3 Feb 2019 02:54:47 -0500 Received: from mail-qt1-f196.google.com ([209.85.160.196]:33253 "EHLO mail-qt1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725839AbfBCHyr (ORCPT ); Sun, 3 Feb 2019 02:54:47 -0500 Received: by mail-qt1-f196.google.com with SMTP id l11so12475571qtp.0; Sat, 02 Feb 2019 23:54:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=BSnmeNvE3EBhH2SfbdbcYylaib6DqHpMf3vu6r4CZqc=; b=eW2ZpxtXpeL0dNqBqV7T9P3rj0Jr0ySMM8IyBtnRNfCAmV0FHPBXmJKiVUhRr6c7Ek 5FLvIRS1mPrUFGNUJudBTkWCAb2BNyPBqY1Z3bqNYECtv/uYnrbpEwe+egAy//YLW+89 1iAdSv3L0cw+C740nL0PqHJWpzKVyrjH3GRfFVPCKnMP4NiqdQtoxDksMaBNPv9Xk6OS amoO3Jbh2w2YPueGnRJa2EQYtW4Sb2eCsuRToDzixFcgrEXqnC9936Ud+Ev7admKd+c+ VHk24NLymfTLr5tTwZEIk71wGZXhzcCr9EokcMcuzF0wdKGnhRhogrLsbLttm8RJrBu/ dlrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc:content-transfer-encoding; bh=BSnmeNvE3EBhH2SfbdbcYylaib6DqHpMf3vu6r4CZqc=; b=XkqHA/cwb7/vkyU/fboFqIodkzWwfKPl+2Xtvt4PH2rpuzIKpSTmXZvDF64e1zN57v 6G2NBQqOI8OHy6jAq9rL/oE1Nf6lIX0Ng3adXVHWonMKKbKCLsZfqz1bAcTlP0uSopGH gEQ2qO6to9J4lljXJN1MsV5zQhDSV3w8oVrBVBrbnk6J20v8HDTqhTp2SOtUXGgrHUGC C/MCOhjo8w/mszHBLu0W5a29t/jHEop3iMuvMvUfXJHpgKNH6yQ50N0CaSSVOLTv8Vgt fuGUUWtg3rFUryj0Py8vQ1wbup4ou0wcoCRr63R5E8hcy3WfOEUhRd0altQUgvrLjaHA 0B4A== X-Gm-Message-State: AJcUukdwFYflH34EEzwneycsIYZaY3+FWwqNnefigIV49GMZnwHSSneI GJ6IGaZslj7ozXrYLgKZXqtAhKorOvDCT3InYFg= X-Received: by 2002:ac8:1617:: with SMTP id p23mr45983910qtj.239.1549180485631; Sat, 02 Feb 2019 23:54:45 -0800 (PST) MIME-Version: 1.0 References: <1548924594-19084-1-git-send-email-l.luba@partner.samsung.com> <1548924594-19084-4-git-send-email-l.luba@partner.samsung.com> <0ca15b4c-ddaa-1be5-35be-e76b008b28a8@partner.samsung.com> In-Reply-To: <0ca15b4c-ddaa-1be5-35be-e76b008b28a8@partner.samsung.com> Reply-To: cwchoi00@gmail.com From: Chanwoo Choi Date: Sun, 3 Feb 2019 16:54:09 +0900 Message-ID: Subject: Re: [PATCH v3 3/8] clk: samsung: add BPLL rate table for Exynos 5422 SoC To: Lukasz Luba Cc: Chanwoo Choi , devicetree , linux-kernel , Linux PM list , linux-samsung-soc , Bartlomiej Zolnierkiewicz , Krzysztof Kozlowski , Kukjin Kim , Kyungmin Park , Marek Szyprowski , Sylwester Nawrocki , MyungJoo Ham , Michael Turquette , Stephen Boyd , linux-clk@vger.kernel.org, linux-arm-kernel Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Lukasz, 2019=EB=85=84 2=EC=9B=94 1=EC=9D=BC (=EA=B8=88) =EC=98=A4=ED=9B=84 11:22, L= ukasz Luba =EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84= =B1: > > Hi Chanwoo, > > On 2/1/19 9:44 AM, Chanwoo Choi wrote: > > Hi, > > > > On 19. 1. 31. =EC=98=A4=ED=9B=84 5:49, Lukasz Luba wrote: > >> Add new table rate for BPLL for Exynos5422 SoC supporting Dynamic Memo= ry > >> Controller frequencies for driver's DRAM timings. > >> > >> CC: Sylwester Nawrocki > >> CC: Chanwoo Choi > >> CC: Michael Turquette > >> CC: Stephen Boyd > >> CC: Kukjin Kim > >> CC: Krzysztof Kozlowski > >> CC: linux-samsung-soc@vger.kernel.org > >> CC: linux-clk@vger.kernel.org > >> CC: linux-arm-kernel@lists.infradead.org > >> CC: linux-kernel@vger.kernel.org > >> Signed-off-by: Lukasz Luba > >> --- > >> drivers/clk/samsung/clk-exynos5420.c | 15 ++++++++++++++- > >> 1 file changed, 14 insertions(+), 1 deletion(-) > >> > >> diff --git a/drivers/clk/samsung/clk-exynos5420.c b/drivers/clk/samsun= g/clk-exynos5420.c > >> index 3e87421..8bf9579 100644 > >> --- a/drivers/clk/samsung/clk-exynos5420.c > >> +++ b/drivers/clk/samsung/clk-exynos5420.c > >> @@ -1325,6 +1325,19 @@ static const struct samsung_pll_rate_table exyn= os5420_pll2550x_24mhz_tbl[] __ini > >> PLL_35XX_RATE(24 * MHZ, 200000000, 200, 3, 3), > >> }; > >> > >> +static const struct samsung_pll_rate_table exynos5422_bpll_rate_table= [] =3D { > >> + PLL_35XX_RATE(24 * MHZ, 933000000, 311, 4, 1), > >> + 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), > >> + PLL_35XX_RATE(24 * MHZ, 138000000, 184, 2, 4), > > > > Except for 825Mhz, I can't find the target frequency > > on Exynos5422 TRM document. Usually, Exynos TRM specified > > the supported stable clocks. It means that undefined clocks > > are not stable as I knew. Where do you find them? > > > > When I calculated the PLL frequency with PMS value, it is correct. > > But, just we need to check the reference of undefined clocks on TRM > > in order to guarantee the stable operation. > They values live in vendor code for Android. > I have tested the DMC & DDR with these ratios in stress scenarios > for a few days and it was stable. If possible, please share the url of original vendor code. > > > > > Remove 933/138Mhz because exynos5433-dmc.c doesn't use 933Mhz and 138Mh= z > > and also Exynos5422 TRM doesn't define 933/138Mhz on pll table. > OK, I will remove them. > > > >> +}; > >> + > >> static const struct samsung_pll_rate_table exynos5420_epll_24mhz_tbl= [] =3D { > >> PLL_36XX_RATE(24 * MHZ, 600000000U, 100, 2, 1, 0), > >> PLL_36XX_RATE(24 * MHZ, 400000000U, 200, 3, 2, 0), > >> @@ -1467,7 +1480,7 @@ static void __init exynos5x_clk_init(struct devi= ce_node *np, > >> exynos5x_plls[apll].rate_table =3D exynos5420_pll2550x_24= mhz_tbl; > >> exynos5x_plls[epll].rate_table =3D exynos5420_epll_24mhz_= tbl; > >> exynos5x_plls[kpll].rate_table =3D exynos5420_pll2550x_24= mhz_tbl; > >> - exynos5x_plls[bpll].rate_table =3D exynos5420_pll2550x_24= mhz_tbl; > >> + exynos5x_plls[bpll].rate_table =3D exynos5422_bpll_rate_t= able; > > > > Exynos5422 used the same PLL table for apll, kpll, bpll and so on. > > You don't need to make the separate pll table. Just add new entries > > to exynos5420_pll2550x_24mhz_tbl table. > OK, I will extend the exynos5420_pll2550x_24mhz_tbl table. > > In v4 patch set, it will be fixed. > > Regards, > Lukasz > > > >> } > >> > >> samsung_clk_register_pll(ctx, exynos5x_plls, ARRAY_SIZE(exynos5x_= plls), > >> > > -- Best Regards, Chanwoo Choi Samsung Electronics