From mboxrd@z Thu Jan 1 00:00:00 1970 From: Darren Hart Subject: Re: [PATCH 3/3] platform/wmi: Expose the raw WDG data in sysfs Date: Tue, 1 Aug 2017 13:03:13 -0700 Message-ID: <20170801200313.GC3110@fury> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from bombadil.infradead.org ([65.50.211.133]:47039 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752248AbdHAUDO (ORCPT ); Tue, 1 Aug 2017 16:03:14 -0400 Content-Disposition: inline In-Reply-To: Sender: platform-driver-x86-owner@vger.kernel.org List-ID: To: Andy Lutomirski Cc: platform-driver-x86@vger.kernel.org, Pali =?iso-8859-1?Q?Roh=E1r?= On Tue, Aug 01, 2017 at 08:37:28AM -0700, Andy Lutomirski wrote: > This adds a sysfs binary attribute 'wdg' on the bus device > (i.e. /sys/class/wmi_bus/wmi_bus-*/wdg) that contains the raw _WDG > data from ACPI. This can be used along with the wmi-bmof driver to > decode the raw interface data from ACPI. I don't recall seeing mention of this is the documentation I read as a requirement to decoding the interface with the bmof. Do Windows systems export _WDG to userspace? Why do we need to export _WDG? -- Darren Hart VMware Open Source Technology Center