From: Jean Delvare <jdelvare@suse.com>
To: Thilo Cestonaro <thilo@cestona.ro>
Cc: linux-i2c@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH] i2c-i801: use MEM resource instead of IO resource
Date: Tue, 12 Apr 2016 09:02:42 +0200 [thread overview]
Message-ID: <1460444562.5044.3.camel@chaos.suse> (raw)
In-Reply-To: <4b887e81aae134c2cfea3e8bb0443c7d@cestona.ro>
Hi Thilo,
On lun., 2016-04-11 at 11:24 +0200, Thilo Cestonaro wrote:
> > 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)
> > -----------------------
> >
>
> As the resource conflict is about the IO resource, I overworked the
> i2c-i801 module to use the MEM resource which is altough available.
> This is IMHO the better alternative to using the
> "acpi_enforce_resources=lax" boot parameter.
>
> The patched module is working on my machine.
To be honest, I didn't know the 82801 SMBus controller supported memory
access. Does it actually work since the first supported controller
(82801AA)?
But anyway, I can't see how using it solves any problem. I guess you
access the very same registers, just using a different method. If the
BIOS is actually using the SMBus controller, you have exactly the same
conflict as before, the only difference is that it is no longer
reported. This would be a regression, not an improvement.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2016-04-12 7:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 9:24 [PATCH] i2c-i801: use MEM resource instead of IO resource Thilo Cestonaro
2016-04-12 7:02 ` Jean Delvare [this message]
2016-04-12 7:33 ` Thilo Cestonaro
2016-04-13 7:01 ` Jean Delvare
2016-04-14 14:27 ` Thilo Cestonaro
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=1460444562.5044.3.camel@chaos.suse \
--to=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
--cc=thilo@cestona.ro \
--cc=wsa@the-dreams.de \
/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).