From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.3 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 89B66C32750 for ; Mon, 12 Aug 2019 15:28:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5E8BC2070C for ; Mon, 12 Aug 2019 15:28:33 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="RHYO2LRR" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728155AbfHLP2c (ORCPT ); Mon, 12 Aug 2019 11:28:32 -0400 Received: from mail-lj1-f196.google.com ([209.85.208.196]:40939 "EHLO mail-lj1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727696AbfHLP2b (ORCPT ); Mon, 12 Aug 2019 11:28:31 -0400 Received: by mail-lj1-f196.google.com with SMTP id e27so3532781ljb.7 for ; Mon, 12 Aug 2019 08:28:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=hgRkzXbbFmA3Q2Zv0rEz4OjwQ8vdleRxSlP6kVoEu4o=; b=RHYO2LRRbZVVHhAAUaNKKEDN8NajKtK8q91SUFV6qIqWj29qigjT4M1fbdwhmfM5uX j4XvBExlMzBwRfNH0dzDn63BCDaCszhrSAlVFsoIDxZpwQLm6YNA+tm1lbO8FptnuW2R QsxenZ4WyFbmETyx/8FeQzf9SOCMYvUGc1yoRbHPIuUc9QsQCm1OCFKUSo4DSlIKoVHn nOoWU2dM5ToC1t4htrb89UsgT1gEVr78xdCQQxjpFa4/uN7TxvKuQKao13Fvl4Luk9ol FkywXuApfxFrPiBqCSDOA7NWPn2B7qRP/G3ljLMJx2OT68/eflmymj87HzCKR/RkBiUT gTKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=hgRkzXbbFmA3Q2Zv0rEz4OjwQ8vdleRxSlP6kVoEu4o=; b=pFh7zOYYsZI44yEtRjzElQ5A3WXM9qyyG0gzY3IffMyJSulfkU4U+KP+wdPfxcTBX4 hzOOPpiiU3QzmDYwwh1CvrCRPJJ7lTCqd2afS4+0slqFGYtSFwwY4dTNZAPWfqh13Jhn 06RWVNcKP84uC2LcoIYNdpxHKZXBsGgVsokPLjYJ79UVIaUjur4KKxM/9fPkUutnxVGE amjdt3EDnzBLM/c+3TZwYa5h4UZXBYMufRorA9NZ7lCO8+6nQRHhEWhAqas7YJBZVHw3 p/uEnnzD+T2Xx+/v3vdCnTSTclRrywioEzNAVFEKmDkHKwmEmffs8mXPNWLmTNQahskQ vNpg== X-Gm-Message-State: APjAAAUhCfhpMgc572lTG5mAseYkMkgRRsGP/K7ZgIITZWFV0NDD3p5g cgg2LdFe8lF5KiCHo5NrFtra1A== X-Google-Smtp-Source: APXvYqwUmSGekdM518oHm5YmsPxuO3pZgErv7gZZOAkXmjPQw54dzNZSR7pYytvzTLEDpYt1bR7jwQ== X-Received: by 2002:a2e:800a:: with SMTP id j10mr5258515ljg.137.1565623709249; Mon, 12 Aug 2019 08:28:29 -0700 (PDT) Received: from centauri (ua-84-219-138-247.bbcust.telenor.se. [84.219.138.247]) by smtp.gmail.com with ESMTPSA id n187sm19035377lfa.30.2019.08.12.08.28.27 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Mon, 12 Aug 2019 08:28:28 -0700 (PDT) Date: Mon, 12 Aug 2019 17:28:26 +0200 From: Niklas Cassel To: Amit Kucheria Cc: Luca Weiss , LKML , Brian Masney , linux-arm-msm , Bjorn Andersson , Eduardo Valentin , Andy Gross , Andy Gross , Daniel Lezcano , Mark Rutland , Rob Herring , Zhang Rui , Marc Gonzalez , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Linux PM list Subject: Re: [PATCH 00/15] thermal: qcom: tsens: Add interrupt support Message-ID: <20190812152826.GA7958@centauri> References: <20190729090735.GA897@onstation.org> <2123341.TWUfUUIiFt@g550jk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 29, 2019 at 03:20:11PM +0530, Amit Kucheria wrote: > On Mon, Jul 29, 2019 at 3:03 PM Luca Weiss wrote: > > > > On Montag, 29. Juli 2019 11:07:35 CEST Brian Masney wrote: > > > On Sat, Jul 27, 2019 at 12:58:54PM +0530, Amit Kucheria wrote: > > > > On Fri, Jul 26, 2019 at 4:59 PM Brian Masney wrote: > > > > > On Fri, Jul 26, 2019 at 04:40:16PM +0530, Amit Kucheria wrote: > > > > > > How well does cpufreq work on 8974? I haven't looked at it yet but > > > > > > we'll need it for thermal throttling. > > > > > > > > > > I'm not sure how to tell if the frequency is dynamically changed during > > > > > runtime on arm. x86-64 shows this information in /proc/cpuinfo. Here's > > > > > > > > > the /proc/cpuinfo on the Nexus 5: > > > > Nah. /proc/cpuinfo won't show what we need. > > > > > > > > Try the following: > > > > > > > > $ grep "" /sys/devices/system/cpu/cpufreq/policy?/* > > > > > > > > More specifically, the following files have the information you need. > > > > Run watch -n1 on them. > > > > > > > > $ grep "" /sys/devices/system/cpu/cpufreq/policy?/scaling_*_freq > > > > > > There's no cpufreq directory on msm8974: > > > > > > # ls -1 /sys/devices/system/cpu/ > > > cpu0 > > > cpu1 > > > cpu2 > > > cpu3 > > > cpuidle > > > hotplug > > > isolated > > > kernel_max > > > modalias > > > offline > > > online > > > possible > > > power > > > present > > > smt > > > uevent > > > > > > I'm using qcom_defconfig. > > > > > > Brian > > > > Hi Brian, > > cpufreq isn't supported on msm8974 yet. > > I have these patches [0] in my tree but I'm not sure they work correctly, but I haven't tested much with them. Feel free to try them on hammerhead. > > > > Luca > > > > [0] https://github.com/z3ntu/linux/compare/b0917f53ada0e929896a094b451219cd8091366e...6459ca6aff498c9d12acd35709b4903effc4c3f8 > > Niklas is working on refactoring some of the Krait code[1]. I'm not > sure if he looked at 8974 directly as part of the refactor adding him > here to get a better sense of the state of cpufreq on 8974. Hello, I took and cleaned up Sricharans commit "cpufreq: qcom: Re-organise kryo cpufreq to use it for other nvmem based qcom socs" from his Krait cpufreq series. The commit renames and refactors the Kryo cpufreq driver. This commit is now in linux-next: https://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git/commit/?h=cpufreq/arm/linux-next&id=106b976debd36b0e61847769f8edd71bfea56ed7 I also added Qualcomm A53 support to this driver. However, Krait CPUs are different from both Kryo and Qualcomm A53, so you will need to take Sricharans patch series and rebase it on top of linux-next. Kind regards, Niklas > > [1] https://lore.kernel.org/linux-arm-msm/20190726080823.xwhxagv5iuhudmic@vireshk-i7/T/#t