Received: by 2002:a05:6a10:2726:0:0:0:0 with SMTP id ib38csp2223945pxb; Wed, 30 Mar 2022 19:53:03 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzHM5SJMRNwGsugYQ/kvaPeOu4XgT+nL32zTSz6ebLgDafhOPTaE6HDz+bl5bUvNgH3B6Sj X-Received: by 2002:a17:902:cec5:b0:154:6b18:6157 with SMTP id d5-20020a170902cec500b001546b186157mr3029424plg.145.1648695182970; Wed, 30 Mar 2022 19:53:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1648695182; cv=none; d=google.com; s=arc-20160816; b=HCs6vpTC8toPf2V5po60+eBdOCnrB9ba+UB3hghTxUM9I33FE/nqlf8hLtTiX6OHgb jzCivZj7xoodWq65qU1RlcV0BJhUXt8mIbhvwXoWpcBoLPRVTdsb7MoIs8GQpBhLMApA DvOe92L97El/nhJbTT0MJ0Z6DqIh/coz5ypbzoLCeFUXor4Vfs35E+yf3+FWE0OwVhUz 0fsl4D2uRiz67lWp/eDGAOXz+b4qfPZZI8LCQqN2NjUfK6k2Ss+haqgfNjyZY0k8jADR XRu+Era77pdeHngHPha3DvkjwOgZsrZOqDhOAI0GsCvV5ljpDtH3QXLVm6ShYJTwcVOz xKvg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=K4jqbVE230M9wS+1QXIPRjVS4MYSGVkCyAOthMzzuT8=; b=aPy/dFGJ/pIOV2T0BMncaY6V+UntJU04YmSS1UvYKmnfTD3sN3COGlNJUDGRt5O6JN VAH+m+Mk6BxBjWft9yCMZ4tIkRZXpXP6axHe/nw5DuOxXNLWrB4ABpyGLIemKA2JgAMH KV8otdvT7R01Als5ku5IO2Zo6X2nqYTK/UjLkLGK9u5HGn1zk1DDd+SRt7siinjf9SkY JPdNzkvD7pDSKjQHqLkgaEGL+CAvjIsokdEvxoqlas9u+4fxMHFIgamq5+tOvBdSQkiQ a1eByGP4mrEZNB4mkdXxyvYTASE3cZZ/Y9eDRzk/rrGiYOuuaR138+BF13dZ0n7a9TvA nzLQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=NdX1PJx7; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id s197-20020a632cce000000b003816043ef0csi23485039pgs.257.2022.03.30.19.53.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 30 Mar 2022 19:53:02 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=NdX1PJx7; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id D9776C55B7; Wed, 30 Mar 2022 19:39:01 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243898AbiC3HiK (ORCPT + 99 others); Wed, 30 Mar 2022 03:38:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58876 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243896AbiC3HiE (ORCPT ); Wed, 30 Mar 2022 03:38:04 -0400 Received: from mail-il1-x12e.google.com (mail-il1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0023B55BE0; Wed, 30 Mar 2022 00:36:18 -0700 (PDT) Received: by mail-il1-x12e.google.com with SMTP id e9so13996005ilu.9; Wed, 30 Mar 2022 00:36:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=K4jqbVE230M9wS+1QXIPRjVS4MYSGVkCyAOthMzzuT8=; b=NdX1PJx79ceLi53HWoka1JaM+2R9nUAaulmuuGNGSXDWk/ZLlchEF0lgouHL3SrPUx cXgivj92UK2ugRw0qCpIPkaphY97RGnb3cDtRBFdKtEusG2csEkg/ocbKfiwzf8uLsYh +bkh+5M3oRdQq/gJtJQUGM66Pgv1ZAlPR4H8xJSNmoB1AHqqqEbWMoECXc7OSo9da4+y qlkS5AXnoguqnqNBAG7FzqVjEkM3CRFkpKKW3qRXjSS4B9FzOZLEjZXaEWoqJ2qs7rNL 24WgjHYrMvxs4vMR7mgqhDldrvzsn5Oej6F+eb0octlfFWvbZOJcqNvEgSN7zLKcvUjr ix6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=K4jqbVE230M9wS+1QXIPRjVS4MYSGVkCyAOthMzzuT8=; b=Vt0NvpuPJxfD4gQf2IddAi17YifMUEamc0HdWtQV+P3Ywu3k/NYOAYS7xd48xoXv5L krWdEDSZAQQqbe5hTZMDcSv3IhottPRrtQRKu9jQawlBmQ61QS5yr8s7oYkZBaODTuwL CsP6Bn2opFYuukSFzbyzB2f1kK1BTrA7jm8iTfsYp4c69KLIl5vWlr5sZS2YD6r6qz9Q xvhhEIasdTiD97Mnp3Z/+xtBygw6NWA+7HdCyzCl/NUOTS27RSG7yxMyMkuxWFdTRDEy VIX1PfDJBMeJU8UKvSryzrFv+AElDfRyEavksjxQ7vgMZ1m+Q4UY1OMOUvOSER6rzIwB 4IfA== X-Gm-Message-State: AOAM532BwH+ASTVvdshoyM9skIYGK6ao3p1AT6XwseeneFJy+3fkLgBI XXsGNrRz6lfRvMeYdH5iwA/K50IlqEaYO/vW+1O1OiwHgss= X-Received: by 2002:a05:6e02:d88:b0:2c8:713f:dcff with SMTP id i8-20020a056e020d8800b002c8713fdcffmr10307147ilj.289.1648625778394; Wed, 30 Mar 2022 00:36:18 -0700 (PDT) MIME-Version: 1.0 References: <20220327121404.1702631-1-eugene.shalygin@gmail.com> <20220327121404.1702631-3-eugene.shalygin@gmail.com> In-Reply-To: From: Eugene Shalygin Date: Wed, 30 Mar 2022 09:36:06 +0200 Message-ID: Subject: Re: [PATCH 2/4] hwmon: (asus-ec-sensors) implement locking via the ACPI global lock To: Guenter Roeck Cc: darcagn@protonmail.com, Jean Delvare , linux-hwmon@vger.kernel.org, Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RDNS_NONE, SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 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 On Wed, 30 Mar 2022 at 01:37, Guenter Roeck wrote: > > On 3/29/22 15:11, Eugene Shalygin wrote: > > On Tue, 29 Mar 2022 at 23:23, Guenter Roeck wrote: > > > >>> +/* Moniker for the ACPI global lock (':' is not allowed in ASL identifiers) */ > >>> +#define ACPI_GLOBAL_LOCK_PSEUDO_PATH ":GLOBAL_LOCK" > >>> + > >> > >> That needs to be documented. > > > > Do you mean a note in the /Documentation/..../...rst or adding details > > here? There is an additional bit of information on this identifier > > below, in the ec_board_info struct declaration. > > > My understanding was that the user would/could request its use via > the module parameter, so it needs to be documented in the rst file. I see now, thank you. > >>> + if (!mutex_path || !strlen(mutex_path)) { > >> > >> When would mutex_path be NULL ? > > When it is set to NULL in the board definition struct ec_board_info. > > > > Are there any such board definitions ? I don't recall seeing any. You are right, there are no such definitions neither in this submission nor before. I'm messaging with a user who showed a hint that such boards might exist [1]. We have not confirmed it yet, but I thought this little test is obvious enough to be put in the code already. Best regards, Eugene [1] https://github.com/zeule/asus-ec-sensors/issues/19