Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1114160yba; Thu, 9 May 2019 10:58:29 -0700 (PDT) X-Google-Smtp-Source: APXvYqyO+N3UQ58wid3LMSN7chpuLixCc+BFBFiPPOMm8/rFJUU6cNz15fCgWlQl7wQvDyYkyLTo X-Received: by 2002:a63:e406:: with SMTP id a6mr7567690pgi.132.1557424709413; Thu, 09 May 2019 10:58:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557424709; cv=none; d=google.com; s=arc-20160816; b=imGiy4GDq6xVjTibWY+fywytjOwyQL2cAvGJ9e4zjIIoLsAbGBfnQDWLihuz1+o5z3 bidI4SaLK8aBdMdB3pjq8jHdGoOYWhkmmn+Cws2CYlVji+LBTqU9y+i5GsHY7aouh/XS fga6tjGy2p1V6nB8LxCJaKyx2C52B3/rtDeHko5V9SeKazMa3IXuEvCNlyWrDcKrRYwf aq+Vj0shNBdi3bhbRIdD84fz42Y46HxXbGmI0fSESIcJOW+IOZP98fRCjLY5EdnkvAKC bxPY8WCqnSE6kJw9nAjNGCAoj9B1mKiDPkmZYPTUx4Tea6IO7iEoY2O+wNcj0hu7hqP4 x8Cw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=2/Ojxz6R9uaL2KTgaEJOCwL4nXhymGztvuWe0n46Oas=; b=nU6XdCpYbEsZ/bQ6CEDIRZvsU9j1rHU5ycy41GfZK+3LlhMeoUSY1adU2D5+GnrhDD /4UbkYN+bsXdu1FH37+WxqQ7lWelNVAKi9iGKIbN+6FUsRb6sG7pyU5um8K3zbWyJnEM F7RuJj2ZNkNVFqP2YsAy6emIiGS8IhFlzZi3rM42o8ICCoFUNjmrbePZuwT5fUxnO9p1 CWBAGQFH+z+Gt+rtizyqebG9QVahdsxO1Yeq46iS1Yth+Kz28YxMXgyaR+UPXQEJQUKF tWaAs4VC+DignptsUMdBSEYKy+ZUmPv5PAc0nHZcA26nZKeBe/PKNs6EnLycFxPuRSOm PG+w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=sqyPOTbm; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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 vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 62si3602882ple.364.2019.05.09.10.58.11; Thu, 09 May 2019 10:58:29 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=sqyPOTbm; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726753AbfEIR5O (ORCPT + 99 others); Thu, 9 May 2019 13:57:14 -0400 Received: from mail-pg1-f194.google.com ([209.85.215.194]:39992 "EHLO mail-pg1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726558AbfEIR5O (ORCPT ); Thu, 9 May 2019 13:57:14 -0400 Received: by mail-pg1-f194.google.com with SMTP id d31so1588019pgl.7; Thu, 09 May 2019 10:57:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2/Ojxz6R9uaL2KTgaEJOCwL4nXhymGztvuWe0n46Oas=; b=sqyPOTbmHW6d3BX5lQrXfvRvmVT8Vhf37Zr+ifzy1/AgKiStiC9VncCPXw53Es650A o5ff9frbPDhp/mEsQfUpU1WVYwKXl1VyWBxUrh34SoAXBFueb9AmKn0EYOFI3WkecKmc 4m7bI1fs0aZtf1cckpad1DGFyfIbfTSL8ZwtCLnTbVxp/qJEARtpbyeqPH0M74Uur9RN MrUQQaPCrDhOVJhLA5Xf9SpFspA9IdMg4l6f4F9cgHQ7iwGzzRdTQTAmZkA91yJ9lKBg uu5SiC0pNRlwvSLyh92gOYpw+eg0QJd49eTZrnNyipIzxP3D2p51UUsLWOEUihg+ThZl Lylg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2/Ojxz6R9uaL2KTgaEJOCwL4nXhymGztvuWe0n46Oas=; b=eqp3xJqkySTq2Hw5VKtY8x/f4HxSX5DZmE32KIriTBZPXT2teuAWS2iTcBFZ0phlrW canUwrxqZX0qxWwgq3U2cvrrdidn+ZZI8UE6gFIPPg0maWN3JGnq5gVCbSdfb/gKSnvY VdwGOYonkxN5xAiQ5/FMicDYtdscwnXfW5FQq8t9vX8WzpzkgBjuAsdj0Dcw4zbtgNAa XW7xj9bRq8bwtlACdtzcaZ5IwLoEysnsD+dX3WjXxRvIGDgZuEjM3KyHEx2SHzQbQ3oU rbbliitFnVz8eG9VeNFaFv261Yd9FVKJL8QyVJwWTqh7iUR9+PwdqfCdS3nW0My5V4RV Auxg== X-Gm-Message-State: APjAAAUu+XaSC6qhn/9oLAyUbQMu8VALSLP2RMfDLmm4vKmpofLJewGt MH1DkTey8LVvujE41XOLs9uYBIfpeLkKgnLjdDQ= X-Received: by 2002:aa7:8212:: with SMTP id k18mr7162450pfi.50.1557424633583; Thu, 09 May 2019 10:57:13 -0700 (PDT) MIME-Version: 1.0 References: <7acd57fe-604a-a96a-4ca2-a25bc88d6405@gmail.com> <92518192-8cf0-7529-0c05-4b3e44ce04b7@gmail.com> In-Reply-To: <92518192-8cf0-7529-0c05-4b3e44ce04b7@gmail.com> From: Andy Shevchenko Date: Thu, 9 May 2019 20:57:02 +0300 Message-ID: Subject: Re: [PATCH v3 04/11] platform/x86: asus-wmi: Improve DSTS WMI method ID detection To: Yurii Pavlovskyi Cc: Daniel Drake , Corentin Chary , Darren Hart , Andy Shevchenko , acpi4asus-user , Platform Driver , Linux Kernel Mailing List , "Rafael J. Wysocki" , Len Brown , ACPI Devel Maling List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 9, 2019 at 8:29 PM Yurii Pavlovskyi wrote: > On 08.05.19 15:36, Andy Shevchenko wrote:> On Fri, Apr 19, 2019 at 1:08 PM > Yurii Pavlovskyi > > wrote: > >> int rv; > >> + char *wmi_uid; > > > > Keep them in reversed spruce order. > > What do you mean by that? Do you mean like this? > + char *wmi_uid; > int rv; Yes. > int err; Don't see this in the above, though. > >> +#define ASUS_WMI_METHODID_DSTS 0x53544344 /* Device STatuS > (DCTS) */ > > > > It's not clear from the description what 'C' stands for. > > Is there any specification which describes the difference and actual > > abbreviations? > > > Not that I know of. Daniel had written some research in the previous > version thread regarding where it is used, but as I understand from current > implementation the functional difference is not really there, as it serves > the same purpose as DSTS, just for another hardware. > > On 09.05.19 08:08, Daniel Drake wrote: > > For clarity I think the constants could be renamed as > > ASUS_WMI_METHODID_DCTS and ASUS_WMI_METHODID_DSTS. > > > Agree, that'll be better. Also makes sense, but then fix up capitalization in the comment (perhaps "Device status" would be good in both cases). -- With Best Regards, Andy Shevchenko