Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751859AbdFIPqh (ORCPT ); Fri, 9 Jun 2017 11:46:37 -0400 Received: from esa6.dell-outbound.iphmx.com ([68.232.149.229]:13418 "EHLO esa6.dell-outbound.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751633AbdFIPqf (ORCPT ); Fri, 9 Jun 2017 11:46:35 -0400 From: X-LoopCount0: from 10.175.216.249 X-IronPort-AV: E=Sophos;i="5.39,317,1493701200"; d="scan'208";a="515910622" To: CC: , , , , , , , Subject: RE: [PATCH 15/16] platform/x86: wmi-mof: New driver to expose embedded WMI MOF metadata Thread-Topic: [PATCH 15/16] platform/x86: wmi-mof: New driver to expose embedded WMI MOF metadata Thread-Index: AQHS3kk7xMJsawcrI0WF/5NgAk77dKIXKtQAgAAFrACAANB6AP//0/SQgAHYjGyAAC0fcIAAXAaAgAJ7srA= Date: Fri, 9 Jun 2017 15:46:12 +0000 Message-ID: <67cc75c9e0ef4a21a168ab3b4dd1e727@ausx13mpc124.AMER.DELL.COM> References: <201706071939.25681@pali> <201706072250.25953@pali> In-Reply-To: <201706072250.25953@pali> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.143.242.75] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id v59Fkeg9005444 Content-Length: 3080 Lines: 74 > -----Original Message----- > From: Pali Rohár [mailto:pali.rohar@gmail.com] > Sent: Wednesday, June 7, 2017 3:50 PM > To: Limonciello, Mario > Cc: luto@amacapital.net; dvhart@infradead.org; platform-driver- > x86@vger.kernel.org; andriy.shevchenko@linux.intel.com; luto@kernel.org; > rjw@rjwysocki.net; linux-kernel@vger.kernel.org; linux-acpi@vger.kernel.org > Subject: Re: [PATCH 15/16] platform/x86: wmi-mof: New driver to expose > embedded WMI MOF metadata > > On Wednesday 07 June 2017 22:23:08 Mario.Limonciello@dell.com wrote: > > > -----Original Message----- > > > From: Pali Rohár [mailto:pali.rohar@gmail.com] > > > Sent: Wednesday, June 7, 2017 12:39 PM > > > To: Limonciello, Mario > > > Cc: luto@amacapital.net; dvhart@infradead.org; platform-driver- > > > x86@vger.kernel.org; andriy.shevchenko@linux.intel.com; > > > luto@kernel.org; rjw@rjwysocki.net; linux-kernel@vger.kernel.org; > > > linux-acpi@vger.kernel.org Subject: Re: [PATCH 15/16] > > > platform/x86: wmi-mof: New driver to expose embedded WMI MOF > > > metadata > > > > > > On Tuesday 06 June 2017 15:56:21 Pali Rohár wrote: > > > > On Tuesday 06 June 2017 13:46:16 Mario.Limonciello@dell.com wrote: > > > > > 2) On my system when you expand the arguments for "void DoBFn" > > > > > the source doesn't describe individual arguments like you do. > > > > > Again this might not matter to MOF parsing tools but wanted to > > > > > let you know in case it does. > > > > > > > > I know, this part is missing. Order of arguments are only in ID > > > > qualifier and not sorted + in/out de-duplicated. > > > > > > Implemented! Now arguments are correctly placed based on ID > > > qualifier. > > > > I think it's still off a little though. > > > > What I'm getting back now from bmf2mof is: > > void DoBFn([in, Description("Fn buf"), out] BDat Data); > > > > Whereas source puts Description as the last argument: > > void DoBFn([in, out, Description("Fn buf")] BDat Data); > > In BMOF from my Latitude E6440 there are specified two parameters with > index 0. One with qualifiers ("in", Description("Fn buf")) and one with > ("out", Description("Fn buf")). I think you have similar/same data in > BMOF. > > In my bmf2mof I just combined those two parameters into one (when name, > type and index matches) and concatenate also qualifiers with removing > duplicates. > > Do not know what is correct way, but I think qualifiers are just > unordered set. MS decompiler probably put "in" and "out" qualifiers > before any other for better readability. Have you tried to run it through mofcomp.exe and then decompile again with bmf2mof? As long as it's coming out the same you're probably right. > > > > > > source: > > > > > void DoBFn([in, out, Description("Fn buf")] BDat Data); > > > > > > > > > > bmf2mof: > > > > > void doBFn([in, Description("Fn buf"), ID(0)] BDat Data, [out, > > > > > Description("Fn buf"), ID(0)] BDat Data); > > > > > > -- > > > Pali Rohár > > > pali.rohar@gmail.com > > -- > Pali Rohár > pali.rohar@gmail.com