public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Len Brown <len.brown@intel.com>
Cc: linux-acpi@vger.kernel.org, Pavel Machek <pavel@ucw.cz>
Subject: ACPI requesting I/O ports?
Date: Fri, 2 Mar 2007 22:14:39 +0100	[thread overview]
Message-ID: <20070302221439.e9a67df5.khali@linux-fr.org> (raw)

Hi Len,

As a follow up of this dicussion:
http://lists.lm-sensors.org/pipermail/lm-sensors/2007-March/019015.html

I'd like to know if it would be possible to have the acpi subsystem
somehow declare or even request the I/O ports it will be accessing when
running AML code? There is a need for this, otherwise other drivers
might access the same resources as the AML code does, with possibly bad
consequences.

Another approach proposed by Pavel Machek would be a general mutex to
protect the AML code from the rest of the kernel, this would probably
work too but the granularity (and thus the latency) would be better
with a per-I/O-region approach.

Thanks,
-- 
Jean Delvare

             reply	other threads:[~2007-03-02 21:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02 21:14 Jean Delvare [this message]
2007-03-02 22:05 ` ACPI requesting I/O ports? Moore, Robert
2007-03-03  9:21   ` Jean Delvare

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=20070302221439.e9a67df5.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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