From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=yadro.com (client-ip=89.207.88.252; helo=mta-01.yadro.com; envelope-from=a.kartashev@yadro.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=pass (p=none dis=none) header.from=yadro.com Authentication-Results: lists.ozlabs.org; dkim=pass (1024-bit key; unprotected) header.d=yadro.com header.i=@yadro.com header.a=rsa-sha256 header.s=mta-01 header.b=W5Ska7Dr; dkim-atps=neutral Received: from mta-01.yadro.com (mta-02.yadro.com [89.207.88.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4Bt5xL0xB2zDqTR for ; Fri, 18 Sep 2020 18:05:41 +1000 (AEST) Received: from localhost (unknown [127.0.0.1]) by mta-01.yadro.com (Postfix) with ESMTP id EC8E35809C for ; Fri, 18 Sep 2020 08:05:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yadro.com; h= content-transfer-encoding:mime-version:user-agent:content-type :content-type:organization:references:in-reply-to:date:date:from :from:subject:subject:message-id:received:received:received; s= mta-01; t=1600416336; x=1602230737; bh=+FnR1T8HQ8FsyewQ1nVr9l86q UU1vlJwT4VLtjVXxGA=; b=W5Ska7DrdfLmhWKL62djIRsZ7cDJFrhvI0icHp3BW bfy2ZsWeQoK3t1czsHZvA20a8VfMzNBDfj3wE6as6kssr1J7JahXQ/pW25bmuRTh uGYqOpk3hflBn6uyP8WDBuKmRxfLN3KdNOWO3TFa36YAWrVdKCCg+3JNTMZZ8DwD Uo= X-Virus-Scanned: amavisd-new at yadro.com Received: from mta-01.yadro.com ([127.0.0.1]) by localhost (mta-01.yadro.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3TZ35e_wnWXk for ; Fri, 18 Sep 2020 11:05:36 +0300 (MSK) Received: from T-EXCH-02.corp.yadro.com (t-exch-02.corp.yadro.com [172.17.10.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mta-01.yadro.com (Postfix) with ESMTPS id 0BC745809B for ; Fri, 18 Sep 2020 11:05:35 +0300 (MSK) Received: from [10.199.0.126] (10.199.0.126) by T-EXCH-02.corp.yadro.com (172.17.10.102) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.32; Fri, 18 Sep 2020 11:05:35 +0300 Message-ID: Subject: Re: Quanta requests to create a repo in OpenBMC github From: Andrei Kartashev To: Date: Fri, 18 Sep 2020 11:05:34 +0300 In-Reply-To: References:

<20200917152912.GG6152@heinlein> Organization: YADRO Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.199.0.126] X-ClientProxiedBy: T-EXCH-01.corp.yadro.com (172.17.10.101) To T-EXCH-02.corp.yadro.com (172.17.10.102) X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2020 08:05:43 -0000 > This daemon is intended to be used in combination with > phosphor-pid-control. You define a configuration file with two > sections: sensors and zones. > > Sensors have a D-Bus path to read from along with a target > temperature > and some other parameters. The daemon subtracks the current > temperature from the target temperature to get the "margin". A > smaller > margin means the temperature is closer to the limit. > > Zones group sensors together and look for the worst (lowest) margin > value within that group. This value is then exported for use in > phosphor-pid-control. I wonder, isn't phosphor-pid-control do the same by its own? How does it works inside pid-control daemon, when you set several thermal sensors for one Zone an set setpoint for each of them? -- Best regards, Andrei Kartashev