Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp683759ybi; Wed, 17 Jul 2019 03:16:32 -0700 (PDT) X-Google-Smtp-Source: APXvYqyJHv0lleUw60MLm/qYq4bf8wSB0VQpek529zuMi4gXxktsom/BJROGtwses3YIDKZMu0E9 X-Received: by 2002:a63:d4c:: with SMTP id 12mr40924906pgn.30.1563358592143; Wed, 17 Jul 2019 03:16:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563358592; cv=none; d=google.com; s=arc-20160816; b=wvLQbsN3sCH53nFGQUhGK4hQ757EC4Vp2Kw8ZJMbiBUHWJCX4j8L0unrk2XmhT6RU6 /4Sb1ZuOjdQ6z5IqEhJcVQGhudlP/fqvWLxixnIZiAdtFHUWjztez6gMB7+SimNQfBWZ yRKnVhszZ2cmcoWCnyAjLwv33RrVnmgPCZDgyUufaXjO6uomavwj9Q2rr9UR/vwGnGuP fDswr8AnU69p2AlLXou8v1ulg8LWQeKMyCK01v+qhfF0dNRCR/jLSRS1TwkYLYwJRX+S cbBQ18Kj2GxF6E+DQ6vsrYCz7IeraQ1eVPrrhUkIglU00uU7T3IXoLtzeHe0sYTjB2kv S+xg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=F6sAXp/myMHMK+IBj2U2uvo/4EtPwNwRFilChwEA8os=; b=WjQQMCO6Dyt89ZoyxzV+A6LgaB7q1lHxBCKMohWRRj4reVuDu0suOSOJGAx37dFE9N otFH3rP4nUhF0L+JUiUX7jSOoTfqzITtcOkVuRWhvnuuWDM6TLzkDzs02Nl3yimtaeqB jtUupkUsoy47F7eVhyWP9BixB/uM6nSwuegYu8tJgxPg/sz7cQr+CYqruqN+US2U9cKd GJ6FFzucrXALkGiLtxhnWIMVPd/qaSJqUbXDY7JQBBjjzFyTqSyS4Ie2D70NfLa9rR5F aqLww6G2jjGvRhIOQtv8AnVQCFRxHuaZmdNULck7YgFXDuS3X3iA/qri9CB3w1KZ8GBA Gllg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="n/KnnkpP"; 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=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h63si21908826pjb.106.2019.07.17.03.16.15; Wed, 17 Jul 2019 03:16:32 -0700 (PDT) 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=@kernel.org header.s=default header.b="n/KnnkpP"; 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=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726878AbfGQKPw (ORCPT + 99 others); Wed, 17 Jul 2019 06:15:52 -0400 Received: from mail.kernel.org ([198.145.29.99]:33858 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725893AbfGQKPv (ORCPT ); Wed, 17 Jul 2019 06:15:51 -0400 Received: from mail-lf1-f50.google.com (mail-lf1-f50.google.com [209.85.167.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id ADD0E21848; Wed, 17 Jul 2019 10:15:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1563358551; bh=cgTcOvfKUWnyc6EhodXbcn/gUVIS698J1CpP1nKMC00=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=n/KnnkpPOoDuockCCqvNzFXBhnfMYPkeMF9lPDJWPXMA/6e0LhdOtABgbBmeTBKnj 6gGW1i/yM9LoqlWU/G6exRQf6dpSJg17b8VF/uH9VIRYXuWQwztjLfetFhpRhLzJ0B qUlE9CJjq7yXJDIIwBYW9UaUM5NrPnQ87gI40Dqo= Received: by mail-lf1-f50.google.com with SMTP id v85so15988090lfa.6; Wed, 17 Jul 2019 03:15:50 -0700 (PDT) X-Gm-Message-State: APjAAAWU5g++XDnCGxNhFy9Evmdh/s48Cc2I0PXGsDO+5ux7GiXEfgVQ VDa+YOP0Jb4nu2/CqDoF90zUKAuWx/uEqs4y6bk= X-Received: by 2002:a19:f007:: with SMTP id p7mr17384347lfc.24.1563358548916; Wed, 17 Jul 2019 03:15:48 -0700 (PDT) MIME-Version: 1.0 References: <20190715124417.4787-1-l.luba@partner.samsung.com> <20190715124417.4787-28-l.luba@partner.samsung.com> In-Reply-To: <20190715124417.4787-28-l.luba@partner.samsung.com> From: Krzysztof Kozlowski Date: Wed, 17 Jul 2019 12:15:37 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v1 27/50] ARM: dts: exynos: align bus_wcore OPPs in Exynos5420 To: Lukasz Luba Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, "linux-samsung-soc@vger.kernel.org" , linux-clk@vger.kernel.org, mturquette@baylibre.com, sboyd@kernel.org, =?UTF-8?B?QmFydMWCb21pZWogxbtvxYJuaWVya2lld2ljeg==?= , kgene@kernel.org, mark.rutland@arm.com, robh+dt@kernel.org, Chanwoo Choi , kyungmin.park@samsung.com, Andrzej Hajda , Marek Szyprowski , s.nawrocki@samsung.com, myungjoo.ham@samsung.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 15 Jul 2019 at 14:44, Lukasz Luba wrote: > > This is the most important bus in the Exynos5x SoC. The whole communication > inside SoC does through that bus (apart from direct requests from CCI to > DRAM controller). It is also modeled as a master bus in devfreq framework. > It is also the only one OPP table throughout other buses which has voltage > values. The devfreq software controls the speed of that bus and other > buses. The other buses follows the rate of the master. There is only one > regulator. The old lowest OPP had pair 925mV, 84MHz which is enough for s/lowest/slowest/ > this frequency. However, due to the fact that the other buses follows the > WCORE bus by taking the OPP from their table with the same id, e.g. opp02, > the children frequency should be stable with the set voltage. > It could cause random faults very hard to debug. > Thus, the patch removes the lowest OPP to make other buses' lowest OPPs s/lowest/slowest/ > working. The new lowest OPP has voltage high enough for buses working up > to 333MHz. It also changes the frequencies of the OPPs to align them to > PLL value such that it is possible to set them using only a divider without > reprogramming OPP. Reprogramming OPP? What is it? > Reprogramming the PLL was not set, so the real frequency I understood from the previous that reprogramming the OPP (PLL?) was happening... Please rephrase entire sentence. BR, Krzysztof > values were not the one from the OPP table, which could confuse the > governor algorithms which relay on OPP speed values making the system to > behave weird. > > Signed-off-by: Lukasz Luba > --- > arch/arm/boot/dts/exynos5420.dtsi | 12 ++++-------- > 1 file changed, 4 insertions(+), 8 deletions(-) > > diff --git a/arch/arm/boot/dts/exynos5420.dtsi b/arch/arm/boot/dts/exynos5420.dtsi > index f8c36ff0d4c3..a355c76af5a5 100644 > --- a/arch/arm/boot/dts/exynos5420.dtsi > +++ b/arch/arm/boot/dts/exynos5420.dtsi > @@ -1107,22 +1107,18 @@ > compatible = "operating-points-v2"; > > opp00 { > - opp-hz = /bits/ 64 <84000000>; > - opp-microvolt = <925000>; > + opp-hz = /bits/ 64 <150000000>; > + opp-microvolt = <950000>; > }; > opp01 { > - opp-hz = /bits/ 64 <111000000>; > + opp-hz = /bits/ 64 <200000000>; > opp-microvolt = <950000>; > }; > opp02 { > - opp-hz = /bits/ 64 <222000000>; > + opp-hz = /bits/ 64 <300000000>; > opp-microvolt = <950000>; > }; > opp03 { > - opp-hz = /bits/ 64 <333000000>; > - opp-microvolt = <950000>; > - }; > - opp04 { > opp-hz = /bits/ 64 <400000000>; > opp-microvolt = <987500>; > }; > -- > 2.17.1 >