From: "thilo.cestonaro@ts.fujitsu.com" <thilo.cestonaro@ts.fujitsu.com>
To: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: i2c-i801 and ACPI resource conflict
Date: Thu, 31 Mar 2016 06:45:57 +0000 [thread overview]
Message-ID: <1459406614.29230.4.camel@ts.fujitsu.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
Hey!
Whenever I load the i2c-i801 smbus controller module I get a resource
conflict with the ACPI:
-----------------------
ACPI Warning: SystemIO range 0x000000000000F040-0x000000000000F05F
conflicts with OpRegion 0x000000000000F040-0x000000000000F04F
(\_SB_.PCI0.SBUS.SMBI) (20150619/utaddress-254)
-----------------------
This resource conflict is due to some ASL code in the BIOS claiming the
resource.
What should be done to fix that sort of resource conflict? Does the
BIOS vendor need to remove the ASL code, or should the driver do
something different or do I need to write a module which uses the ACPI
to access the smbus controller?
Any hints would be nice!
Thanks!
BR,
Thilo
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3847 bytes --]
reply other threads:[~2016-03-31 6:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1459406614.29230.4.camel@ts.fujitsu.com \
--to=thilo.cestonaro@ts.fujitsu.com \
--cc=linux-i2c@vger.kernel.org \
/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).