From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Darren Hart <dvhart@infradead.org>, Kast Bernd <kastbernd@gmx.de>,
corentin.chary@gmail.com, lenb@kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
acpi4asus-user@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org
Subject: Re: [RFC 1/2] ACPI: activate&export acpi_os_get_physical_address
Date: Fri, 1 May 2015 05:56:19 +0100 [thread overview]
Message-ID: <20150501045618.GA22054@srcf.ucam.org> (raw)
In-Reply-To: <2766179.6BuP3vhKAH@vostro.rjw.lan>
On Fri, May 01, 2015 at 03:45:52AM +0200, Rafael J. Wysocki wrote:
> And I don't really understand the Matthew's comment regarding limiting
> operation regions to system memory. This is about a specific operation
> region (which BTW only seems to be used as a means to access system memory
> at the location pointed to by the arg) in that particular method.
My feeling was that it really ought to have been the ACPI code dealing
with this in some way, but having looked at it again I accept that this
is really something that's limited by the vendor implementation.
virt_to_phys() isn't the worst thing to do here.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2015-05-01 4:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 14:12 [RFC 0/2] asus notebook fan control Kast Bernd
2015-04-22 14:12 ` [RFC 2/2] asus-wmi: add " Kast Bernd
2015-04-30 18:42 ` Darren Hart
2015-05-02 12:37 ` Corentin Chary
2015-04-22 14:12 ` [RFC 1/2] ACPI: activate&export acpi_os_get_physical_address Kast Bernd
2015-04-30 18:10 ` Darren Hart
2015-05-01 1:32 ` Rafael J. Wysocki
2015-05-01 1:45 ` Rafael J. Wysocki
2015-05-01 4:56 ` Matthew Garrett [this message]
2015-05-03 17:57 ` Darren Hart
2015-04-30 18:00 ` [RFC 0/2] asus notebook fan control Darren Hart
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=20150501045618.GA22054@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentin.chary@gmail.com \
--cc=dvhart@infradead.org \
--cc=kastbernd@gmx.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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).