Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp1610527rwl; Fri, 7 Apr 2023 21:02:31 -0700 (PDT) X-Google-Smtp-Source: AKy350axjI60z5z4DNXuUW0rgM1m7BNFZqh5/ftZfCM3qjm5hEqmzlpo+MMQcIRIXM0Hb+9OktQg X-Received: by 2002:a17:906:350b:b0:947:3af0:66c0 with SMTP id r11-20020a170906350b00b009473af066c0mr1392524eja.26.1680926551303; Fri, 07 Apr 2023 21:02:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1680926551; cv=none; d=google.com; s=arc-20160816; b=LkfomqMFRR8aqJdlGglsKVn0VcLLS7c5IXpgROzd2qZjpniLDCfvk1SzHh5uvs7gjv h/m5Qu065Zt89XpnGbxgQvXvwwrVmoFMwkMfhXL2nuKITDHGSiq7k2AZIBVX57a28S2i gEB0yZFSt+SOoZcFD7RJ7WDn8529Edzp8z0gA9dIPsxC01Wa6VkqEV+c/puwNxHrv2V/ YENhEEInEJf7LkiRKWELY/amRqb4ta00y9Ua8RgciQ/2twzSoUdWs0e27aXvzA55qxfY EklLVPvDSkqJnseDTXgg7bkR4asIa7V85pirnaX0RuV/OJdBmcnC+Z5MSG5P2qKtYsYt Vf1A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:in-reply-to :content-disposition:mime-version:references:message-id:subject:from :date:dkim-signature; bh=9fXf41jSfeH8npS2SnXtOfP5uik6JpmwKRQ6ipNjZhg=; b=d3uK8CX+gZAh1IhhuLzg45Id7DVmm2o6iluCTB7nvJzKM9hiM5cIPuY/2tflyxjYTQ h5NYdv9/kVV7IsCFkwxQMFtKGqoHPScyC7vJeDbW/wivjHrxqheBt6bGuehIiv5ZZiZU uyyRBofslbc/uIxuqbrg8dCsPsp8INYVCe74VELRVdqjQofqEVKmEQcnQSN6yXX3kfF7 /edrU5r3gOLdLKGZLnZWXcd680n2TjIHDLn8Ojk4UPoM/BmchgBHdMETft0Ccz8LdqfI CZw+ERXEKSgHk4Dm3rUq1eS3izXjPwYpRC4q5b+nT65oznpn9NvxUy2GI+XheyqrBHiL rJ+Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@equiv.tech header.s=org header.b="mMH1/aZl"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=equiv.tech Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w14-20020aa7da4e000000b004ced100b0b7si5204920eds.316.2023.04.07.21.02.04; Fri, 07 Apr 2023 21:02:31 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@equiv.tech header.s=org header.b="mMH1/aZl"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=equiv.tech Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229748AbjDHD67 (ORCPT + 99 others); Fri, 7 Apr 2023 23:58:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59280 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229586AbjDHD66 (ORCPT ); Fri, 7 Apr 2023 23:58:58 -0400 Received: from s.wrqvtzvf.outbound-mail.sendgrid.net (s.wrqvtzvf.outbound-mail.sendgrid.net [149.72.126.143]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D01FDD330 for ; Fri, 7 Apr 2023 20:58:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=equiv.tech; h=from:subject:references:mime-version:content-type:in-reply-to:to:cc: content-transfer-encoding:cc:content-type:from:subject:to; s=org; bh=9fXf41jSfeH8npS2SnXtOfP5uik6JpmwKRQ6ipNjZhg=; b=mMH1/aZlfkigrD7oqZwotDQVo/b4Gps6GU01Cot3KtnizHwlc1YMxH8vHOuUfqdnuCGC SGn+ixiHfYx6Bu2utFfKxDrVH2vcBFJQhabWRRsDqH0GXi020AkfwMnGjmS+a/ErGhtW1Y 4uBWi3DmmdxfeSR2TygKP3Kzcy8nlBWo4= Received: by filterdrecv-7457b4c9b5-zkl2v with SMTP id filterdrecv-7457b4c9b5-zkl2v-1-6430E67E-6 2023-04-08 03:58:54.271893053 +0000 UTC m=+3903964.849135075 Received: from localhost (unknown) by geopod-ismtpd-6 (SG) with ESMTP id XJJ8jxPtQIa9xN2G75nh4A Sat, 08 Apr 2023 03:58:53.421 +0000 (UTC) Date: Sat, 08 Apr 2023 03:58:54 +0000 (UTC) From: James Seo Subject: Re: [PATCH v2] hwmon: add HP WMI Sensors driver Message-ID: References: <20230406152321.42010-1-james@equiv.tech> <2257deba-187b-82d2-181c-f1fed08a2ff7@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SG-EID: =?us-ascii?Q?1X41iaRO4wVP+tFXGLuxpQ0yxxMDhGIesR5UcsYKVengQKgidLJSXwOMZlPQwP?= =?us-ascii?Q?WsEyzZr62PnJ8E17NJhhMO0lG3ycUBe69Gwm5XP?= =?us-ascii?Q?UVOGIf7x=2FfnTSULP9ZVcTc=2FVMlX41+BWNk1aAfb?= =?us-ascii?Q?WMk78u45ClkgQzWopc48ZH4Rs=2F0BNxmbi4xb48H?= =?us-ascii?Q?kKMGsqU1rOoQAuH3VBeCplEmsM7UjOQdMUeGpbv?= =?us-ascii?Q?LQyLTJ9ltU0BCbICnMdVUatvXGu3HcSvvCD+OT?= To: Guenter Roeck Cc: Jean Delvare , linux-hwmon@vger.kernel.org, platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org X-Entity-ID: Y+qgTyM7KJvXcwsg19bS4g== Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=1.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_MSPIKE_H2, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Greetings, On Fri, Apr 07, 2023 at 05:54:48AM -0700, Guenter Roeck wrote: > On 4/6/23 22:39, James Seo wrote: >> Hi, >> >>> is it guaranteed that faulty sensors wont become operational later? >>> Also filtering out such sensors would make the support for the hwmon_temp_fault and >>> hwmon_fan_fault attributes meaningless. >> >> Good point. I can't be certain, but the MOF does seem to imply that >> sensors can indeed be faulty on just a temporary basis. >> > > Your current code would explicitly exclude faulty fans from being listed, > which does not exactly sound like a good idea. True enough. I recall my reasoning being that faulty sensors would still be visible in debugfs. I should have seen the problem then. >> I'll filter out only the sensors that are "Not Connected" at probe >> time. My thinking is, even if these might turn into connected sensors >> later, that would mean the user is e.g. hot-plugging a fan (!), and >> keeping them could result in a large number (~10 on my Z420) of >> pointless extra channels. And this would also match the behavior of >> HP's official utility. >> > Ultimately that is an implementation decision. Are the sensors hot-pluggable ? HP's WMI object specification allows sensors to be hot-pluggable in principle. I can't definitively say more than that due to a lack of test hardware (that whitepaper I referenced is from 2005, after all). So I think the answer is that it depends on the board and the WMI implementation. That's also what I meant in my reply to Armin when I said that I couldn't be certain whether faulty sensors can recover. But I take your point that the driver should be able to handle it if the board can. > If so, how does HP's utility handle the insertion or removal of a sensor (fan) ? HP's utility just pretty-prints a snapshot of what is in WMI at the moment when the user clicks a button, and then only for the sensors that were connected when the utility was first started. It doesn't do anything special to handle insertion or removal beyond that. > Either case, it is ok with me if disconnected sensors are not listed. > Not listing faulty sensors seems like a bad idea, though. > > Guenter Acknowledged. Faulty sensors will be listed in the next version. Thanks for reviewing. Further suggestions or concerns from you or anyone else reading this are both welcome and appreciated. James