[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <94F2FBAB4432B54E8AACC7DFDE6C92E37E592F3B@ORSMSX110.amr.corp.intel.com>
Date: Fri, 14 Apr 2017 23:32:48 +0000
From: "Moore, Robert" <robert.moore@...el.com>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
CC: Guenter Roeck <linux@...ck-us.net>,
"Zheng, Lv" <lv.zheng@...el.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
Len Brown <lenb@...nel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"devel@...ica.org" <devel@...ica.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] ACPICA: Export mutex functions
> -----Original Message-----
> From: Rafael J. Wysocki [mailto:rjw@...ysocki.net]
> Sent: Friday, April 14, 2017 3:30 PM
> To: Moore, Robert
> Cc: Guenter Roeck; Zheng, Lv; Wysocki, Rafael J; Len Brown; linux-
> acpi@...r.kernel.org; devel@...ica.org; linux-kernel@...r.kernel.org
> Subject: Re: [PATCH] ACPICA: Export mutex functions
>
> On Wednesday, April 12, 2017 09:56:37 PM Moore, Robert wrote:
> >
> > > -----Original Message-----
> > > From: Guenter Roeck [mailto:linux@...ck-us.net]
> > > Sent: Wednesday, April 12, 2017 2:23 PM
> > > To: Moore, Robert <robert.moore@...el.com>
> > > Cc: Zheng, Lv <lv.zheng@...el.com>; Wysocki, Rafael J
> > > <rafael.j.wysocki@...el.com>; Len Brown <lenb@...nel.org>; linux-
> > > acpi@...r.kernel.org; devel@...ica.org; linux-kernel@...r.kernel.org
> > > Subject: Re: [PATCH] ACPICA: Export mutex functions
> > >
> > > On Wed, Apr 12, 2017 at 03:29:55PM +0000, Moore, Robert wrote:
> > > > The ACPICA mutex functions are based on the host OS functions, so
> > > > they
> > > don't really buy you anything. You should just use the native Linux
> > > functions.
> > > >
> > >
> > > You mean they don't really acquire the requested ACPI mutex, and the
> > > underlying DSDT which declares and uses the mutex just ignores if
> > > the mutex was acquired by acpi_acquire_mutex() ?
> > >
> > [Moore, Robert]
> >
> > OK, I understand now. Yes, these mutex interfaces are in fact intended
> for the purpose you mention:
> >
> > * FUNCTION: AcpiAcquireMutex
> > *
> > * PARAMETERS: Handle - Mutex or prefix handle (optional)
> > * Pathname - Mutex pathname (optional)
> > * Timeout - Max time to wait for the lock
> (millisec)
> > *
> > * RETURN: Status
> > *
> > * DESCRIPTION: Acquire an AML mutex. This is a device driver interface
> to
> > * AML mutex objects, and allows for transaction locking
> between
> > * drivers and AML code. The mutex node is pointed to by
> > * Handle:Pathname. Either Handle or Pathname can be NULL,
> but
> > * not both.
> >
> >
> > And yes, both the acquire and release interfaces should be exported.
>
> OK, so I'm assuming this will go in through the upstream ACPICA.
>
Yes, done for next release.
Bob
> Thanks,
> Rafael
Powered by blists - more mailing lists