Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2078116imm; Thu, 20 Sep 2018 07:28:10 -0700 (PDT) X-Google-Smtp-Source: ANB0VdYf9YNFF0nZT3Q6OxeHxIvuUmtMEhUOeoCMZE6fQv0VSGP/GDtogS2U70BMTyBLhxkYSkvz X-Received: by 2002:a62:1d54:: with SMTP id d81-v6mr41785949pfd.139.1537453690672; Thu, 20 Sep 2018 07:28:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537453690; cv=none; d=google.com; s=arc-20160816; b=jriwvZrVWs4iufkVF+MXPdVuUcswQ+krutK7UQ1QoImOXC9jsENnbE2HoJXI06KXF1 HqBm5mf4XgXLVPzZKA/+/3XBsOWCl84ieUlbRWHemsAXBokZpj+i7lXGZ9mMLO52+XBD 6PvxfiQleS3twlfEvrZujYVewqxgr74LiaEKXGgB5UPsiXXMQXTi2m1kV34vikFanHEW /lmGFkLZLXrsAdfymJPuIzbJEVX6PdVWPFMWEhw6Je/IJ3NHfzbCPcZd5FPXdBv9QWf5 4ijnzMEvJNFGnmBDnU3a3B6urymsjSrH4yWzrJ5wc8EfdIx6wMg59u9QT8jzmzmgNcHI Ozrg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:from:to:subject :content-transfer-encoding:mime-version:references:in-reply-to :user-agent:date:dkim-signature; bh=12sUzqfhhQY9eA+y1y0f5VWQVeWbjnyCTzszpVFT00Y=; b=qhoB+eiJ3tQW4nfhzTcAFx/eewOpSrMVC4QazI4emUIxodF4+bGGV7vL1DQ9Zd6O4V 61oMRUYhxl46RGb3ujD8SGb1vlaCbeWTP7avTTMCrmFB94gXZF4ba4iNJ1MTjXfT2gx9 wFWfgVj3Evr56BI5KGlJnu7UeZzYtJ1itH8QG7yliA2j5PtOOuZw7dte49FQYHF92dTR f4aMEjb88yfWrnM8iLeStHso23x/0xNx/hG+HZaCJq8a1zuSJzSlIOwbVI3gNaq+6+SE 0D6F9pUkSLEj3qGkoIog7OSQGKrkdini1TPo+2QqqFzIpYAP7Fp87Ophb2ODNgiv6F0z 2PoQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=Ys3KR3NS; 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=fail (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 p21-v6si23959037plo.182.2018.09.20.07.27.54; Thu, 20 Sep 2018 07:28:10 -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=fail header.i=@gmail.com header.s=20161025 header.b=Ys3KR3NS; 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=fail (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733076AbeITULO (ORCPT + 99 others); Thu, 20 Sep 2018 16:11:14 -0400 Received: from mail-wm1-f66.google.com ([209.85.128.66]:34638 "EHLO mail-wm1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732257AbeITULN (ORCPT ); Thu, 20 Sep 2018 16:11:13 -0400 Received: by mail-wm1-f66.google.com with SMTP id j25-v6so1724928wmc.1; Thu, 20 Sep 2018 07:27:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:user-agent:in-reply-to:references:mime-version :content-transfer-encoding:subject:to:from:message-id; bh=12sUzqfhhQY9eA+y1y0f5VWQVeWbjnyCTzszpVFT00Y=; b=Ys3KR3NSiBiEXXOm0gpGlvvnE2pjtXa4P3NV8tVBnox5OMdtQXtStdgbHSNMGOW8GM a1SEtx3fe0BkfuDi8c8Yyyft9S4RQlM3lXprw5ybRmWHPE2QtIQRCoORmG7zvi/NZt91 AjppTQ3sfS4RiIRtl2+FWy/ScceAYyvefY5QiAPeDhHiQbzU/zUKCqvCsebCFP0prj+G dIgpt7YH/VPmSkvJck2aQf9M8vzGc2qRZBIqdXnxvFzvDEMaTFfs9ismKrIw/NOgpyo6 WmgV4dhcdDHsmTlY1AjPclnW+pbmxpB0r+ORzwcv65tCT91jfrYXe1h2ItcByPT92VwO j9xw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:subject:to:from:message-id; bh=12sUzqfhhQY9eA+y1y0f5VWQVeWbjnyCTzszpVFT00Y=; b=SLc5nGVhoePUg34Hs+772gOjUc6F6D//LsYU50rrpXY3s0vUOelSQFB8uF0W+bwVFX SV+Y05ByXQKVeDl20JvSEqz7V+WhNCwkSflOi+0yiz5Cb3YJ1hQ3m5GP5A/0qP1IS0b7 ONckTeAYyh9ubR4IF1i8NVbf7i4g+MjrX6sr7He/9XYtaGfc9Cd/XGu0tQ+37Czm2b7i 4DDVN2DPQmqM9Z8KNIdr8m1T0H/AzgkUYIjae48YLIjNzmWpaBQZKpUenaf/8cZkP+4p Tmen4YQkFcX5ZMv9xVJ59gsv/4Fzw6DyDcKDqkL/9Wza3z8OcJMnr8jzbg3AP3aP1Ykh KD4Q== X-Gm-Message-State: APzg51CseI+ChVwk39CSqM5YhKQRq4HgBbdQKtU7P4LR9fRVgNGtX3pw jkiWacRe6TWmExb/st/JYA== X-Received: by 2002:a1c:578a:: with SMTP id l132-v6mr2800997wmb.16.1537453645363; Thu, 20 Sep 2018 07:27:25 -0700 (PDT) Received: from android-dhcp-8-1-0-d4-38-9c-a2-1f-05.home (host86-147-9-252.range86-147.btcentralplus.com. [86.147.9.252]) by smtp.gmail.com with ESMTPSA id w17-v6sm2049768wmc.43.2018.09.20.07.27.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Sep 2018 07:27:24 -0700 (PDT) Date: Thu, 20 Sep 2018 15:27:21 +0100 User-Agent: K-9 Mail for Android In-Reply-To: References: <1534248753-2440-1-git-send-email-sricharan@codeaurora.org> <2ae96741-94c0-ba4c-fc19-05d33179683c@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PATCH V12 00/14] Krait clocks + Krait CPUfreq To: Sricharan R , mark.rutland@arm.com, robh@kernel.org, sudeep.holla@arm.com, linux@arm.linux.org.uk, rjw@rjwysocki.net, viresh.kumar@linaro.org, mturquette@baylibre.com, linux-pm@vger.kernel.org, sboyd@codeaurora.org, linux@armlinux.org.uk, thierry.escande@linaro.org, linux-kernel@vger.kernel.org, david.brown@linaro.org, devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, andy.gross@linaro.org, linux-soc@vger.kernel.org, linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org, niklas.cassel@linaro.org From: Craig Message-ID: <132152AA-E8D1-49AF-87C7-3A9ECA0766FA@gmail.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20 September 2018 14:01:57 BST, Sricharan R wrote: > > >On 9/20/2018 1:54 AM, Craig wrote: >> Yup, this patch seems to have fixed the higher frequencies from the >quick test I did=2E >>=20 > Thanks !!=2E Can i take that as Craig Tatlor ? Sure, no problem > >Regards, > Sricharan > > tested-by:=20 >> On 7 September 2018 15:28:53 BST, Craig Tatlor >wrote: >>> >>> >>> On 7 September 2018 10:57:34 BST, Sricharan R >>> wrote: >>>> Hi Craig, >>>> >>>> >>>>>> [v12] >>>>>> * Added my signed-off that was missing in some patches=2E >>>>>> * Added Bjorn's acked that i missed earlier=2E >>>>>> >>>>> >>>>> Can you give this a try on your 8974 device and check if the >>>>> pvs version reporting, scaling for higher frequencies are fine ? >>>>> Sorry, i could not get hold of a 8974 device=2E So in-case if you >>>> still >>>>> have the issues with higher frequencies, can you give a quick >>> debug >>>>> and report=2E That would be of great help=2E >>>>> >>>> Ping on this =2E=2E >>> >>> Hi, didn't see your last message, >>> >>> Will have a try on mine in the weekend and report back=2E >>>> >>>> Regards, >>>> Sricharan >>>> >>>>> Regards, >>>>> Sricharan >>>>> >>>>> >>>>>> [v11] >>>>>> * Dropped patch 13 and 14 from v10 and >>>>>> merged the qcom-cpufreq-krait driver to the existing >>>> qcom-cpufreq-kryo=2Ec >>>>>> * Rebased on top of clk-next >>>>>> * Fixed a bug while populating the pvs version for krait=2E >>>>>> >>>>>> [v10] >>>>>> * Addressed Stephen's comments to add clocks bindings >properties >>>>>> to the newly introduced nodes=2E >>>>>> * Added a change to include opp-supported-hw to qcom-cpufreq=2Ec >>>>>> * Rebased on top of clk-next >>>>>> * Although there were minor changes to bindings and the driver >>>>>> retained the acked-by tags from Rob and Viresh respectively=2E= =20 >=20 >>> >>>>>> >>>>>> [v9] >>>>>> * Fixed a rebase issue in Makefile and added Tag from Robh=2E >>>>>> >>>>>> [v8] >>>>>> * Fixed a bug in path#14 pointed out by Viresh and also added >>>> tags=2E >>>>>> No change in any other patch=2E >>>>>> >>>>>> [v7] >>>>>> * Fixed comments from Viresh for cleaning up the error handling >>>>>> in qcom-cpufreq=2Ec=2E Also changed the init function to latein= it >>>>>> call=2E This is required because nvmem which gets initialised >>> with >>>>>> module_init needs to go first=2E >>>>>> * Fixed Rob's comments for bindings documentation >>>>>> * Fixed kbuild build issue in clk-lpc32xx=2Ec >>>>>> * Rebased on top of clk-next >>>>>> >>>>>> [v6] >>>>>> * Adrressed comments from Viresh for patch #14 in v5 [5] >>>>>> * Introduced a new binding operating-points-v2-krait-cpu >>>>>> as per discussion with Rob >>>>>> * Added Review tags >>>>>> >>>>>> [v5] >>>>>> * Addressed comments from Rob for bindings >>>>>> * Addressed comments from Viresh to use >dev_pm_opp_set_prop_name, >>>> accordingly >>>>>> dropped patch #12 and corrected patch #11 from previous patch >>>> set in [4] >>>>>> * Converted to use #spdx tags for newly introduced files >>>>>> >>>>>> Mostly a resend of the v3 posted by Stephen quite some time back >>> [1] >>>>>> except for few changes=2E >>>>>> Based on reading some feedback from list, >>>>>> * Dropped the patch "clk: Add safe switch hook" from v3 [2]=2E >>>>>> Now this is taken care by patch#10 in this series only for >>>> Krait=2E >>>>>> * Dropped the path "clk: Avoid sending high rates to downstream >>>>>> clocks during set_rate" from v3 [3]=2E >>>>>> * Rebased on top of clk-next=2E >>>>>> * Dropped the DT update from the series=2E Will send separately >>>>>> * Now with cpufreq-dt+opp supporting voltage scaling, >registering >>>> the >>>>>> krait cpu supplies in DT should be sufficient=2E But one issue >>> is, >>>>>> the qcom-cpufreq drivers reads the efuse and based on that >>>> registers >>>>>> the opp data and then registers the cpufreq-dt device=2E So >when >>>>>> cpufreq-dt driver probes and registers the regulator to the >OPP >>>> framework, >>>>>> it expects that the opp data for the device should not be >>>> registered before >>>>>> the regulator=2E Will send a RFC patch removing that check, to >>>> find out the >>>>>> right way of doing it=2E >>>>>> >>>>>> These patches provide cpufreq scaling on devices with Krait CPUs=2E >>>>>> In Krait CPU designs there's one PLL and two muxes per CPU, >>> allowing >>>>>> us to switch CPU frequencies independently=2E >>>>>> >>>>>> secondary >>>>>> +-----+ + >>>>>> | QSB |-------+------------|\ >>>>>> +-----+ | | |-+ >>>>>> | +-------|/ | >>>>>> | | + | >>>>>> +-----+ | | | >>>>>> | PLL |----+-------+ | primary >>>>>> +-----+ | | | + >>>>>> | | +-----|\ +------+ >>>>>> +-------+ | | | \ | | >>>>>> | HFPLL |----------+-----------------| |-----| CPU0 | >>>>>> +-------+ | | | | | | | >>>>>> | | | +-----+ | / +------+ >>>>>> | | +-| / 2 |---------|/ >>>>>> | | +-----+ + >>>>>> | | secondary >>>>>> | | + >>>>>> | +------------|\ >>>>>> | | |-+ >>>>>> +---------------|/ | primary >>>>>> + | + >>>>>> +-----|\ +------+ >>>>>> +-------+ | \ | | >>>>>> | HFPLL |----------------------------| |-----| CPU1 | >>>>>> +-------+ | | | | | >>>>>> | +-----+ | / +------+ >>>>>> +-| / 2 |---------|/ >>>>>> +-----+ + >>>>>> >>>>>> To support this in the common clock framework we model the muxes, >>>>>> dividers, and PLLs as different clocks=2E CPUfreq only interacts >>>>>> with the primary mux (farthest right in the diagram)=2E When >CPUfreq >>>>>> sets a rate, the mux code finds the best parent that can provide >>> the >>>> rate=2E >>>>>> Due to the design, QSB and the top PLL are always a fixed rate >and >>>> thus >>>>>> only support one frequency each=2E These sources provide the lowest >>>>>> frequencies for the CPUs=2E The HFPLLs are where we can make the >CPU >>>> go >>>>>> faster (GHz range)=2E Sometimes we need to run the HFPLL twice as >>>>>> fast and divide it by two to get a particular frequency=2E >>>>>> >>>>>> When switching rates we can't leave the CPU clocked by the HFPLL >>>> because >>>>>> we need to turn off the output of the PLL when changing its >>>> frequency=2E >>>>>> This means we have to switch over to the secondary mux and use >one >>>> of the >>>>>> fixed sources=2E This is why we need something like the safe parent >>>> patch=2E >>>>>> >>>>>> [1] >>>> >http://lists=2Einfradead=2Eorg/pipermail/linux-arm-kernel/2015-March/3326= 07=2Ehtml >>>>>> [2] >>>> >http://lists=2Einfradead=2Eorg/pipermail/linux-arm-kernel/2015-March/3326= 15=2Ehtml >>>>>> [3] >>>> >http://lists=2Einfradead=2Eorg/pipermail/linux-arm-kernel/2015-March/3326= 08=2Ehtml >>>>>> [4] https://lwn=2Enet/Articles/740994/=20 >>>>>> [5] https://lkml=2Eorg/lkml/2017/12/19/537 >>>>>> >>>>>> >>>>>> Sricharan R (3): >>>>>> clk: qcom: Add safe switch hook for krait mux clocks >>>>>> cpufreq: qcom: Re-organise kryo cpufreq to use it for other >nvmem >>>>>> based qcom socs >>>>>> cpufreq: qcom: Add support for krait based socs >>>>>> >>>>>> Stephen Boyd (11): >>>>>> ARM: Add Krait L2 register accessor functions >>>>>> clk: qcom: Add support for High-Frequency PLLs (HFPLLs) >>>>>> clk: qcom: Add HFPLL driver >>>>>> dt-bindings: clock: Document qcom,hfpll >>>>>> clk: qcom: Add MSM8960/APQ8064's HFPLLs >>>>>> clk: qcom: Add IPQ806X's HFPLLs >>>>>> clk: qcom: Add support for Krait clocks >>>>>> clk: qcom: Add KPSS ACC/GCC driver >>>>>> dt-bindings: arm: Document qcom,kpss-gcc >>>>>> clk: qcom: Add Krait clock controller driver >>>>>> dt-bindings: clock: Document qcom,krait-cc >>>>>> >>>>>> =2E=2E=2E/devicetree/bindings/arm/msm/qcom,kpss-acc=2Etxt | 19 + >>>>>> =2E=2E=2E/devicetree/bindings/arm/msm/qcom,kpss-gcc=2Etxt | 44 += ++ >>>>>> =2E=2E=2E/devicetree/bindings/clock/qcom,hfpll=2Etxt | 60 += +++ >>>>>> =2E=2E=2E/devicetree/bindings/clock/qcom,krait-cc=2Etxt | 34 += + >>>>>> =2E=2E=2E/{kryo-cpufreq=2Etxt =3D> qcom-nvmem-cpufreq=2Etxt} | = 7 +- >>>>>> arch/arm/common/Kconfig | 3 + >>>>>> arch/arm/common/Makefile | 1 + >>>>>> arch/arm/common/krait-l2-accessors=2Ec | 48 +++ >>>>>> arch/arm/include/asm/krait-l2-accessors=2Eh | 9 + >>>>>> drivers/clk/qcom/Kconfig | 28 ++ >>>>>> drivers/clk/qcom/Makefile | 5 + >>>>>> drivers/clk/qcom/clk-hfpll=2Ec | 244 >>>> +++++++++++++ >>>>>> drivers/clk/qcom/clk-hfpll=2Eh | 44 +++ >>>>>> drivers/clk/qcom/clk-krait=2Ec | 126 +++++++ >>>>>> drivers/clk/qcom/clk-krait=2Eh | 40 +++ >>>>>> drivers/clk/qcom/gcc-ipq806x=2Ec | 82 +++++ >>>>>> drivers/clk/qcom/gcc-msm8960=2Ec | 172 >+++++++++ >>>>>> drivers/clk/qcom/hfpll=2Ec | 96 +++++ >>>>>> drivers/clk/qcom/kpss-xcc=2Ec | 87 +++++ >>>>>> drivers/clk/qcom/krait-cc=2Ec | 397 >>>> +++++++++++++++++++++ >>>>>> drivers/cpufreq/Kconfig=2Earm | 6 +- >>>>>> drivers/cpufreq/Makefile | 2 +- >>>>>> drivers/cpufreq/cpufreq-dt-platdev=2Ec | 5 + >>>>>> drivers/cpufreq/qcom-cpufreq-kryo=2Ec | 232 >>>> ------------ >>>>>> drivers/cpufreq/qcom-cpufreq-nvmem=2Ec | 387 >>>> ++++++++++++++++++++ >>>>>> include/dt-bindings/clock/qcom,gcc-msm8960=2Eh | 2 + >>>>>> 26 files changed, 1941 insertions(+), 239 deletions(-) >>>>>> create mode 100644 >>>> Documentation/devicetree/bindings/arm/msm/qcom,kpss-gcc=2Etxt >>>>>> create mode 100644 >>>> Documentation/devicetree/bindings/clock/qcom,hfpll=2Etxt >>>>>> create mode 100644 >>>> Documentation/devicetree/bindings/clock/qcom,krait-cc=2Etxt >>>>>> rename Documentation/devicetree/bindings/opp/{kryo-cpufreq=2Etxt >=3D> >>>> qcom-nvmem-cpufreq=2Etxt} (98%) >>>>>> create mode 100644 arch/arm/common/krait-l2-accessors=2Ec >>>>>> create mode 100644 arch/arm/include/asm/krait-l2-accessors=2Eh >>>>>> create mode 100644 drivers/clk/qcom/clk-hfpll=2Ec >>>>>> create mode 100644 drivers/clk/qcom/clk-hfpll=2Eh >>>>>> create mode 100644 drivers/clk/qcom/clk-krait=2Ec >>>>>> create mode 100644 drivers/clk/qcom/clk-krait=2Eh >>>>>> create mode 100644 drivers/clk/qcom/hfpll=2Ec >>>>>> create mode 100644 drivers/clk/qcom/kpss-xcc=2Ec >>>>>> create mode 100644 drivers/clk/qcom/krait-cc=2Ec >>>>>> delete mode 100644 drivers/cpufreq/qcom-cpufreq-kryo=2Ec >>>>>> create mode 100644 drivers/cpufreq/qcom-cpufreq-nvmem=2Ec >>>>>> >>>>> >>=20 --=20 Please, Don't Panic