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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 81882C433EF for ; Fri, 4 Feb 2022 18:13:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1377417AbiBDSNc (ORCPT ); Fri, 4 Feb 2022 13:13:32 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42622 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1377401AbiBDSN3 (ORCPT ); Fri, 4 Feb 2022 13:13:29 -0500 Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A9793C061714 for ; Fri, 4 Feb 2022 10:13:29 -0800 (PST) Received: by mail-wm1-x32d.google.com with SMTP id s22-20020a1ca916000000b0037b91599cd0so1509548wme.5 for ; Fri, 04 Feb 2022 10:13:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=H5RG1NlLigZ3a+HzA+NMogI8AZIGVKKErA7UKMgzcRc=; b=WuBmH1B8vZigPDrh6FITt8iihWdrzP00zvNomzwa6MRvFPHLuEZodEOD78KVOAw0rT EYv1tFbzACbbZW9qW8qYm/freu7N5wUjKRMExpeHwcl7kHMx5kv3swEQR6phajrvhZyI 7Bp9UzxkHzx7Xr2NPLNBWTqdvcSGO3khBHdSFh+ZYW7jS0QEEbwD6KvRBe+5Ism9/rb5 Nxuf605G4bsUt2tOodECpYVIZhUXLmOMvisSJ0+mmTcEgw5kfMCTEnWG77QD1qedN3Cs 5hzuE3gIdvl95kl4ed1Y1lZLeUPYw41g7VYYUQmMnEsbLRhsxUJR8ArQ7Y4RywUZwlf/ KrzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=H5RG1NlLigZ3a+HzA+NMogI8AZIGVKKErA7UKMgzcRc=; b=R9f/OeVjXLx6/qJTvpkEdhSB7NVYSgu4TksreaUhrXY5+Btt38NAdpIumEws+AV/NY CO4EQE8w1TWlE3HsMj+G3DpO5mRgwmAnh/jq3BH6xzav2GXZ1/dOX8jC4IDTkqHZCoVv UnAawG6DbDxml9z37dLCR9H54jCnqr4Hvkb+ULH5+zS4PJzLJx/vXfBcrmJBztQ1Gm8R PkeI3GLoxGZ3lRvmT6tmXCFgyZZ7o+Qeg5bHdt68r2Ddxzk1vYov0PRFjqHdh53mPDUb 26GRjPNNidAQA2sCRNzfx0CZRrZFQlmJjY8+oizuyw8TRH5eMZF22hotkQS81+4a3vQB oKoA== X-Gm-Message-State: AOAM530Ld2iOgt4uH+972BuUlHRKGFio1Myugvk3q2P78F9U7bCM2dG5 bL9WGXBDuPMVWSrkRwg3FNfatg== X-Google-Smtp-Source: ABdhPJw9ceKqgGwdJX9RKZ1cnO/MM07FkjqzMlRQyVWl1W/eQK85RCwh4OxkvC57gu98M/5MrrMnhA== X-Received: by 2002:a1c:f413:: with SMTP id z19mr3262806wma.144.1643998408138; Fri, 04 Feb 2022 10:13:28 -0800 (PST) Received: from ?IPV6:2a01:e34:ed2f:f020:46b:d462:f12b:a36? ([2a01:e34:ed2f:f020:46b:d462:f12b:a36]) by smtp.googlemail.com with ESMTPSA id e11sm2084339wmq.16.2022.02.04.10.13.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 04 Feb 2022 10:13:27 -0800 (PST) Message-ID: <2297b79e-b99c-30a5-1e5c-560d5553e146@linaro.org> Date: Fri, 4 Feb 2022 19:13:25 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [PATCH] tools/lib/thermal: Add a thermal library Content-Language: en-US To: "Rafael J. Wysocki" Cc: Linux PM , Linux Kernel Mailing List , Jonathan Cameron , William Breathitt Gray , Viktor Rosendahl , Sasha Levin , Colin Ian King , Srinivas Pandruvada , "Zhang, Rui" References: <20220204161518.163536-1-daniel.lezcano@linaro.org> From: Daniel Lezcano In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/02/2022 18:11, Rafael J. Wysocki wrote: > CC Rui and Srinivas > > On Fri, Feb 4, 2022 at 5:15 PM Daniel Lezcano wrote: >> >> The thermal framework implements a netlink notification mechanism to >> be used by the userspace to have a thermal configuration discovery, >> trip point changes or violation, cooling device changes notifications, >> etc... >> >> This library provides a level of abstraction for the thermal netlink >> notification allowing the userspace to connect to the notification >> mechanism more easily. The library is callback oriented. >> >> As it is the very first iteration, the API may be subject to >> changes. For this reason, the documentation will be provided after >> those are stabilized. > > So shouldn't this be an RFC? Yes, it could be. > Also, I would prefer documentation to be provided or at least some > intended usage examples to be given. Sure, no problem. I'll resend with the RFC and the examples -- Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog