Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3570561yba; Tue, 23 Apr 2019 06:12:27 -0700 (PDT) X-Google-Smtp-Source: APXvYqxcU32WEFjxnXz6fI1ISINS9H1d3qSu8pwMrYob3UNO3xYhyHbiJGcT9X4iBE58QQaGylSS X-Received: by 2002:a62:1b8a:: with SMTP id b132mr26445057pfb.19.1556025146957; Tue, 23 Apr 2019 06:12:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556025146; cv=none; d=google.com; s=arc-20160816; b=qbfdGOGoeCLJD4q+Trdzf4XD4TKUwauWtvOtYF2lsNzDZDbAAmEv4EopnCJW+ciKky ydcqLuNyHmumtQj8MsA3PLoCB/nhpEwMyoxjkZsqxA4OKBCltH3u0b0iP8LGCDgx6M3Q F/cEsI+T439nuD+lpI3bd0qAGja28OTcFqIQJ325tgcpEo11n5S5VtVerKhn02wuYjaR Qu3WchwwTFbvqVfHQnVaQba0bEcNeUa3rjfPpUtQec7YvblVcr9BQeqHVOJal+asAJLu xHsT+z/4qEORYtPbSS7qH0T5bTY5LGG+EG+BQTwGuwuqMQJLL4zmZoao0RMWcyyPRE09 6J3g== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=pkA2ZD3js8ujGUpcZ5B6oMrJ90w9fR7iTRa0o8qjidY=; b=PWitbZYv6KRXEnzoNzyvmELmWwo2TAdlyoHxmR1tHBIeBR8/GZ4KcXlxS9BlYSPnn8 0pFF+TH7C8kEX0RV3tTN9a6jTmkowNupzaRnrCAQaxXCkzZhCiXAtGuRgQe0jD/Ts86P SipZVyXbxGrzHPXmY2t12XQcBiTGH4tjntIxWOQoguCWVJ2sWefbQXJJYLoivKaEmde3 DF9jBXUiMfKvj2v8M5fjExI2vA4Cq75Lnd8aCMOwNum4OMI+WugAGWblKc9ssut7AOI/ DKQIGuhq0KDTOhlJ5kUvZY4NJav4eENwoxDsawtCTqfkYw0s6V2nxurdA80mrQ2jX+vM 3B0A== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k14si15184081pll.126.2019.04.23.06.12.11; Tue, 23 Apr 2019 06:12:26 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728143AbfDWNKk (ORCPT + 99 others); Tue, 23 Apr 2019 09:10:40 -0400 Received: from ns.iliad.fr ([212.27.33.1]:52196 "EHLO ns.iliad.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727944AbfDWNKh (ORCPT ); Tue, 23 Apr 2019 09:10:37 -0400 Received: from ns.iliad.fr (localhost [127.0.0.1]) by ns.iliad.fr (Postfix) with ESMTP id 01AB6205F9; Tue, 23 Apr 2019 15:10:36 +0200 (CEST) Received: from [192.168.108.49] (freebox.vlq16.iliad.fr [213.36.7.13]) by ns.iliad.fr (Postfix) with ESMTP id DDBC1205F8; Tue, 23 Apr 2019 15:10:35 +0200 (CEST) Subject: Re: [PATCH v2 00/13] qcom: dts: thermal cleanups To: Amit Kucheria Cc: Andy Gross , LKML , MSM , Bjorn Andersson , Sibi Sankar References: <5583cae1-8fea-724a-24a4-59b38a205ac3@free.fr> <842b06c6-15b2-7ba6-702e-c8b043d390a6@free.fr> From: Marc Gonzalez Message-ID: <903fa0a6-5c40-97b4-1c01-fd84f3e51c62@free.fr> Date: Tue, 23 Apr 2019 15:10:35 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP ; ns.iliad.fr ; Tue Apr 23 15:10:36 2019 +0200 (CEST) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 23/04/2019 14:56, Amit Kucheria wrote: > On Tue, Apr 23, 2019 at 3:01 PM Marc Gonzalez wrote: > >> On 02/04/2019 20:46, Amit Kucheria wrote: >> >>> On Tue, Apr 2, 2019 at 8:58 PM Marc Gonzalez wrote: >>> >>>> On 29/03/2019 11:12, Amit Kucheria wrote: >>>> >>>>> Changes since v1: >>>>> - Devices that are not associated with cooling-maps use the 'hot' type >>>>> - Remove critical trip from such devices too and restrict that type of CPUs >>>>> - For 8916, add the sensor on the modem >>>>> >>>>> Description: >>>>> - Expose all temperature sensors on msm8916, msm996, msm8998, sdm845 >>>>> - split up the register address map for msm8998 >>>>> - standardize names of the various thermal-zones across boards to make it >>>>> easy for test scripts to parse >>>> >>>> This is what I see on msm8998 with your patch series applied on top of >>>> yesterday's next: >>>> >>>> # dmesg | grep of_parse_thermal_zones >>>> of_parse_thermal_zones: build cpu0-thermal zone 0 >>>> of_parse_thermal_zones: build cpu1-thermal zone 0 >>>> of_parse_thermal_zones: build cpu2-thermal zone 0 >>>> of_parse_thermal_zones: build cpu3-thermal zone 0 >>>> of_parse_thermal_zones: build cpu4-thermal zone 0 >>>> of_parse_thermal_zones: build cpu5-thermal zone 0 >>>> of_parse_thermal_zones: build cpu6-thermal zone 0 >>>> of_parse_thermal_zones: build cpu7-thermal zone 0 >>>> of_parse_thermal_zones: build gpu-thermal-bottom zone 0 >>>> of_parse_thermal_zones: build gpu-thermal-top zone 0 >>>> of_parse_thermal_zones: build cluster0-mhm-thermal zone -22 >>>> of_parse_thermal_zones: build cluster1-mhm-thermal zone -22 >>>> of_parse_thermal_zones: build cluster1-l2-thermal zone 0 >>>> of_parse_thermal_zones: build modem-thermal zone 0 >>>> of_parse_thermal_zones: build mem-thermal zone 0 >>>> of_parse_thermal_zones: build wlan-thermal zone 0 >>>> of_parse_thermal_zones: build q6-dsp-thermal zone 0 >>>> of_parse_thermal_zones: build camera-thermal zone 0 >>>> of_parse_thermal_zones: build multimedia-thermal zone 0 >>>> of_parse_thermal_zones: build pm8998 zone 0 >>>> of_parse_thermal_zones: build battery-thermal zone 0 >>>> of_parse_thermal_zones: build skin-thermal zone 0 >>>> >>>> NB: -EINVAL for cluster0-mhm-thermal and cluster1-mhm-thermal >>>> >>>> >>>> # cat /sys/devices/virtual/thermal/thermal_zone*/temp >>>> 35800 >>>> 35200 >>>> 34500 >>>> 34800 >>>> 34500 >>>> 34100 >>>> 34100 >>>> 33500 >>>> 33800 >>>> cat: /sys/devices/virtual/thermal/thermal_zone17/temp: Invalid argument >>>> 36100 >>>> cat: /sys/devices/virtual/thermal/thermal_zone19/temp: Invalid argument >>>> 35500 >>>> 36100 >>>> 35800 >>>> 35200 >>>> 35500 >>>> 36100 >>>> cat: /sys/devices/virtual/thermal/thermal_zone8/temp: Invalid argument >>>> cat: /sys/devices/virtual/thermal/thermal_zone9/temp: Invalid argument >>>> >>>> >>>> Are the failures expected? >>>> (cluster*-mhm-thermal and thermal_zone*/temp) >>> >>> No they are not. Unfortunately, I didn't have HW to test, so >>> appreciate the help with testing. I'll check the 8, 9, 17 and 19 again >>> before resubmitting. >> >> Looks like Andy merged this series? > > Argh! my bad, I completely forgot about the need to fix this up. I > need to get me one of these boards. > >> https://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git/log/?h=for-next >> >> I was expecting a respin, or a discussion of the failures. >> >> Slightly confused. What next? > > We can either revert that one patch for the msm8998, but I think it > might be better if I send a fixup patch that could fixup those 4 zones > instead. > > Does that work for you? Sure. I can give you a Tested-by once everything works on the MEDIABOX I have. You mention the 4 thermal_zone*/temp failures. What about the cluster0-mhm-thermal and cluster1-mhm-thermal failures? Regards.