Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id DCB75C25B50 for ; Mon, 23 Jan 2023 19:26:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232483AbjAWT0V (ORCPT ); Mon, 23 Jan 2023 14:26:21 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34930 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230267AbjAWT0T (ORCPT ); Mon, 23 Jan 2023 14:26:19 -0500 Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E55092113; Mon, 23 Jan 2023 11:26:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1674501978; x=1706037978; h=message-id:subject:from:to:cc:date:in-reply-to: references:mime-version:content-transfer-encoding; bh=Jy150XyuERCh2fiwnJuz+EToeoCHCaLdsWTWyPJgDPA=; b=LeAMQCP/ml5BMLzbKgKnT4T5xeBo++hHrSbMxwFlfLwBghKXmT+qljQ1 2Y8uuNs7h4dJCMmsCRf3DMwJUNME59g0oJVd0o/F6bcRPjAJbGqzUQG4K 9c+8qrIHp4YZtI1h5Fp4hsqx8m1t9kZm89zSfMwQcWGGZVn5oA3PZQnjP xvTCGazdpGzElVYp+zp27u70P2cz5oAgPYQnrZ14fvlMnA5mSviBth+t4 25L/+CjPj1kR3I/sSyx4F/DlCwqXl4wEYpQANS+ijzpKlrgTBzXIDb56q Txhu6BQ7B7qveZqQrjYXoFcR/qO7oIJkG45jxYo/5wx5i3rf5HyOpX4FR g==; X-IronPort-AV: E=McAfee;i="6500,9779,10599"; a="412355868" X-IronPort-AV: E=Sophos;i="5.97,240,1669104000"; d="scan'208";a="412355868" Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Jan 2023 11:26:18 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10599"; a="663789877" X-IronPort-AV: E=Sophos;i="5.97,240,1669104000"; d="scan'208";a="663789877" Received: from mhkirsch-mobl1.amr.corp.intel.com (HELO spandruv-desk1.amr.corp.intel.com) ([10.212.134.26]) by fmsmga007-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Jan 2023 11:26:18 -0800 Message-ID: <19f1860e20fbc75c3d2c3eefda29cccd18ca59a9.camel@linux.intel.com> Subject: Re: [PATCH v7 0/3] thermal: intel: Use generic trip points in 2 drivers From: srinivas pandruvada To: "Rafael J. Wysocki" , Linux PM Cc: LKML , Linux ACPI , Daniel Lezcano , Zhang Rui Date: Mon, 23 Jan 2023 11:26:09 -0800 In-Reply-To: <3234230.44csPzL39Z@kreacher> References: <5916342.lOV4Wx5bFT@kreacher> <2882611.e9J7NaK4W3@kreacher> <3234230.44csPzL39Z@kreacher> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.42.4 (3.42.4-2.fc35) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2023-01-23 at 19:52 +0100, Rafael J. Wysocki wrote: > On Monday, January 23, 2023 7:45:30 PM CET Rafael J. Wysocki wrote: > > On Monday, January 23, 2023 7:36:52 PM CET Rafael J. Wysocki wrote: > > > Hi All, > > > > > > This is a new version of the series from Daniel posted as: > > > > > > https://lore.kernel.org/linux-pm/20230120231530.2368330-1-daniel.lezcano@linaro.org/ > > > > > > The first patch has been reworked (see > > > https://lore.kernel.org/linux-pm/5911499.lOV4Wx5bFT@kreacher/) > > > and the other two have been rebased on top of it. > > > > > > I have retained the R-by tags from Rui, because the changes in > > > patches [2-3/3] are > > > not essential, but I think that this new set needs to be tested > > > again. > > > > > > Srinivas, can you test it please? > > > > Something's wrong, sorry. > > > > I get some invalid trip temperatures with this set. > > Sorry, scratch this, I got confused by THERMAL_TEMP_INVALID showing > up in > sysfs, but it did show up before too. > > Please test! > > > > It will be easy if you have some test branch to avoid dependecies on > other patches. Thanks, Srinivas > >