From: "Moore, Robert" <robert.moore@intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "Zheng, Lv" <lv.zheng@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"'Len Brown'" <lenb@kernel.org>,
"'linux-acpi@vger.kernel.org'" <linux-acpi@vger.kernel.org>,
"'devel@acpica.org'" <devel@acpica.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"Box, David E" <david.e.box@intel.com>
Subject: RE: [PATCH] ACPICA: Export mutex functions
Date: Mon, 17 Apr 2017 20:40:38 +0000 [thread overview]
Message-ID: <94F2FBAB4432B54E8AACC7DFDE6C92E37E593580@ORSMSX110.amr.corp.intel.com> (raw)
In-Reply-To: <20170417194527.GA16734@roeck-us.net>
> -----Original Message-----
> From: Guenter Roeck [mailto:linux@roeck-us.net]
> Sent: Monday, April 17, 2017 12:45 PM
> To: Moore, Robert <robert.moore@intel.com>
> Cc: Zheng, Lv <lv.zheng@intel.com>; Wysocki, Rafael J
> <rafael.j.wysocki@intel.com>; 'Len Brown' <lenb@kernel.org>; 'linux-
> acpi@vger.kernel.org' <linux-acpi@vger.kernel.org>; 'devel@acpica.org'
> <devel@acpica.org>; 'linux-kernel@vger.kernel.org' <linux-
> kernel@vger.kernel.org>; Box, David E <david.e.box@intel.com>
> Subject: Re: [PATCH] ACPICA: Export mutex functions
>
> On Mon, Apr 17, 2017 at 07:27:37PM +0000, Moore, Robert wrote:
> >
> > > -----Original Message-----
> > > From: Moore, Robert
> > > Sent: Monday, April 17, 2017 10:13 AM
> > > To: Guenter Roeck <linux@roeck-us.net>; Zheng, Lv
> > > <lv.zheng@intel.com>
> > > Cc: Wysocki, Rafael J <rafael.j.wysocki@intel.com>; Len Brown
> > > <lenb@kernel.org>; linux-acpi@vger.kernel.org; devel@acpica.org;
> > > linux- kernel@vger.kernel.org
> > > Subject: RE: [PATCH] ACPICA: Export mutex functions
> > >
> > > There is a model for the drivers to directly acquire an AML mutex
> > > object. That is why the acquire/release public interfaces were added
> > > to ACPICA.
> > >
> > > I forget all of the details, but the model was developed with MS and
> > > others during the ACPI 6.0 timeframe.
> > >
> > >
> > [Moore, Robert]
> >
> >
> > Here is the case where the OS may need to directly acquire an AML
> mutex:
> >
> > From the ACPI spec:
> >
> > 19.6.2 Acquire (Acquire a Mutex)
> >
> > Note: For Mutex objects referenced by a _DLM object, the host OS may
> also contend for ownership.
> >
> From the context in the dsdt, and from description of expected use cases
> for _DLM objects I can find, this is what the mutex is used for (to
> serialize access to a resource on a low pin count serial interconnect,
> aka LPC).
>
> What does that mean in practice ? That I am not supposed to use it
> because it doesn't follow standard ACPI mutex declaration rules ?
>
> Thanks,
> Guenter
>
> >
[Moore, Robert]
I'm not an expert on the _DLM method, but I would point you to the description section in the ACPI spec, 5.7.5 _DLM (DeviceLock Mutex).
> >
> >
> > Other than this case, the OS/drivers should never need to directly
> acquire an AML mutex.
> > Bob
> >
next prev parent reply other threads:[~2017-04-17 20:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 15:13 [PATCH] ACPICA: Export mutex functions Guenter Roeck
2017-04-12 15:29 ` Moore, Robert
2017-04-12 21:22 ` Guenter Roeck
2017-04-12 21:56 ` Moore, Robert
2017-04-13 0:55 ` Guenter Roeck
2017-04-14 22:30 ` Rafael J. Wysocki
2017-04-14 23:32 ` Moore, Robert
2017-04-17 9:39 ` Zheng, Lv
2017-04-17 9:48 ` Zheng, Lv
2017-04-17 14:05 ` Guenter Roeck
2017-04-17 23:35 ` Zheng, Lv
2017-04-17 15:56 ` Guenter Roeck
2017-04-17 17:12 ` Moore, Robert
2017-04-17 19:27 ` Moore, Robert
2017-04-17 19:45 ` Guenter Roeck
2017-04-17 20:40 ` Moore, Robert [this message]
2017-04-17 21:03 ` Guenter Roeck
2017-04-17 21:29 ` Rafael J. Wysocki
2017-04-17 22:32 ` Guenter Roeck
2017-04-17 22:56 ` Rafael J. Wysocki
2017-04-17 23:53 ` Zheng, Lv
2017-04-18 4:35 ` Guenter Roeck
2017-04-18 7:06 ` Zheng, Lv
2017-04-18 7:14 ` Zheng, Lv
2017-04-18 13:50 ` Guenter Roeck
2017-04-18 14:15 ` Rafael J. Wysocki
2017-04-18 16:07 ` Moore, Robert
2017-04-19 1:26 ` Zheng, Lv
2017-04-19 1:35 ` Zheng, Lv
2017-04-17 23:46 ` Zheng, Lv
2017-04-17 23:43 ` Zheng, Lv
2017-04-17 19:35 ` Moore, Robert
2017-04-17 23:37 ` Zheng, Lv
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=94F2FBAB4432B54E8AACC7DFDE6C92E37E593580@ORSMSX110.amr.corp.intel.com \
--to=robert.moore@intel.com \
--cc=david.e.box@intel.com \
--cc=devel@acpica.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lv.zheng@intel.com \
--cc=rafael.j.wysocki@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).