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 X-Spam-Level: X-Spam-Status: No, score=-0.7 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,DKIM_VALID,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F1F0DC4360F for ; Wed, 3 Apr 2019 03:23:15 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id C1B522146E for ; Wed, 3 Apr 2019 03:23:15 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="orE/JtN2"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="H9Kf+5UF" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C1B522146E Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Date:Message-ID:Subject: From:To:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References: List-Owner; bh=Jb/J0x3XxAgrmiZLjPN0oSm/Q8Ro4EclMCBne3npZgM=; b=orE/JtN2gK8E2e db+t/MMxSybUjTL56wbDzYDozbOVfbLjhqcor1w/Ig1KSxtxMYjQ5MImssEzuCdN/zMW6NLIN8QCY SNDncyo9Tp9O17cqPAcyGP6h7y3Ia0RiCi5K7j+ro5+/VzhF9eirlvNbmL4QQKrEjsOHwjkBJVa+P 7Q12/cu2HEg+6cJdGbJsAaS0CdVh94j9ppSTUkg7h0uk+ok2g8dXBgCcIrKhthjvGUf4Vsy5iNm9a Ucjc6njfnBvZntZU7Nq7CFwXFNcXcWy2lQv+krwLLNnyfv0hvPGzz0BKDyBLFrZi+M6E3LalRgcxC dRfJhkx3KbFSLKppuIjw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1hBWUZ-00041A-9p; Wed, 03 Apr 2019 03:23:11 +0000 Received: from mail-pf1-x443.google.com ([2607:f8b0:4864:20::443]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1hBWUW-00040q-GV for linux-arm-kernel@lists.infradead.org; Wed, 03 Apr 2019 03:23:09 +0000 Received: by mail-pf1-x443.google.com with SMTP id b3so7411664pfd.1 for ; Tue, 02 Apr 2019 20:23:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:openpgp:cc:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=Y5ge1ZjQf8SimZV+7qeZtcyWlnSgvmpT0soqRQJ55g4=; b=H9Kf+5UFn7LA1NF/7etL+9NSFnYQkAIxBPttG0QJfr4QFDPaPVp+Zc5t5d6hSSugdh 2ezrPXXvy/U8xpsoACOU/agFIBolpSvHvvROlA7KlVrL3TErHHWCVZSYJhUj/xvaC5qV rA9GxVtdAQJtgRWYAFLDi0dXKg035esTYEXINxRwYvdglxVozmbRX9bryJ/hG8dGI1aV y+rH5QDkeQVp+5PHU5RepPFj4GOZdKLW4Cq9XGn4Yg54dwGsWWxA2wwvUkgiBlgKD8vp hAr17OSMzycTf0tYExokvz8s5i4UMuA59o03FWL/fQ+nhFSolNHchVGob4IMINwEsVQI yPiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:openpgp:cc:message-id:date :user-agent:mime-version:content-language:content-transfer-encoding; bh=Y5ge1ZjQf8SimZV+7qeZtcyWlnSgvmpT0soqRQJ55g4=; b=asm4wDEIeOm4/hJBEeobJDx3TXXdxAqaLvDRRs3UIkAO5ABEVbl7h9ZA82TMZv21dl 8ObvcTXLMfFQ9XLjabm0WzukgfUKTvmXZRyfQthq4jlWs7nBGGi2ZFFgylHxAmhJYsTl TBgK2JHVz1EENyblgvG6w1dL3acot5Kp+TxBl7WhbHG70O9OWidMOto88oIsNs71/fVY us2ZNJkBd9CV90nMaKwXv8x5a+oDuK/MfQjUQ2YGM7b93z5FJzTgFfBhDADpEU4jBtr5 t+tkgWdh392HevoXw2jDihkCobaztFt/tU24vYt3maDlcrancVpwkyyUUhA9sEqQYgsL wjkQ== X-Gm-Message-State: APjAAAXn3SmswjnakmZGmYQqNX4fAtddQ4rhl3dMtEglhB0eLZmX25m/ /o80YWa2YgpF91pcuRrBjUiZxsSN X-Google-Smtp-Source: APXvYqzEluOStjzEgaV8YApmSvefAXKFlZgW9r1ujFeJQY+7yATMkd+csZ4bvKuyhdOeDpS5d3V2MA== X-Received: by 2002:a62:204b:: with SMTP id g72mr67036332pfg.51.1554261787008; Tue, 02 Apr 2019 20:23:07 -0700 (PDT) Received: from [10.230.28.107] ([192.19.223.250]) by smtp.gmail.com with ESMTPSA id n1sm16755597pgv.19.2019.04.02.20.23.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Apr 2019 20:23:06 -0700 (PDT) To: Sudeep Holla , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , linux-hwmon@vger.kernel.org From: Florian Fainelli Subject: Couple of questions on SCMI sensor protocol and Linux implementation Openpgp: preference=signencrypt Message-ID: <1902f151-7ddd-6b4b-4135-a2affe20c009@gmail.com> Date: Tue, 2 Apr 2019 20:22:58 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 Content-Language: en-US X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190402_202308_552065_BAC2B995 X-CRM114-Status: GOOD ( 11.52 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Guenter Roeck Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Sudeep, There are a couple of things on which I would appreciate your feedback regarding the Linux SCMI sensor protocol: 1) The Linux SCMI implementation has all the nuts and bolts to allow configuring trip points, but the hwmon subsystem through the use of hwmon_thermal_add_sensor() API does not actually make use of that capability. Would it be a big stretch to use the hwmon_ops::write function to get to support that feature? The other thing that puzzles me is that there does not appear to be provision in the SCMI sensor protocol to describe thermal zones, so I assume that people still have to provide supplemental data through Device Tree for devm_thermal_zone_of_sensor_register() to pick up the thermal zones definitions? 2) Support for regulators through SCMI I work with a device where the regulators can only be controlled via a dedicated piece of HW which is accessible through SCMI from the Linux side. Do you think there is value in coming up with a scmi-regulator.c driver that makes use of the sensor protocol for discovering and reporting regulators or would that be something that belongs more to the power domain protocol? Thanks for reading me! Cheers -- Florian _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel