Subject: Re: [ACPI] Re: [PATCH] filling in ACPI method access via sysfs
	namespace
From: Alex Williamson <alex.williamson@hp.com>
To: John Belmonte <john@neggie.net>
Cc: acpi-devel@lists.sourceforge.net,
       linux-kernel <linux-kernel@vger.kernel.org>
In-Reply-To: <4077535D.6020403@neggie.net>
References: <1081453741.3398.77.camel@patsy.fc.hp.com>
	 <1081549317.2694.25.camel@patsy.fc.hp.com>  <4077535D.6020403@neggie.net>
Content-Type: text/plain
Message-Id: <1081566768.2562.8.camel@wilson.home.net>
Mime-Version: 1.0
Date: Fri, 09 Apr 2004 21:12:49 -0600
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 973
Lines: 20

On Fri, 2004-04-09 at 19:52, John Belmonte wrote:
> The limitation of this interface is that it's not able to call an ACPI 
> method with some arguments and get the return value, correct?

   Yes, that's unfortunately a limitation.  Most of the standard
interfaces either take no parameters or have no return value, so they
fit nicely into this framework.  I'm open to suggestions on how to work
around this.  We could make the store function save off the method
parameters, then the show function would call the method with the saved
parameters and return the results.  Obviously there are some userspace
ordering issues that could make this complicated, but it's easy to code
on the kernel side.  Other ideas?  Thanks,

	Alex

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/