From: Peter Tyser <ptyser@xes-inc.com>
To: Miles Lane <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Jean Delvare <khali@linux-fr.org>
Subject: Re: 3.6.0+ (GIT) -- lpc_ich: Resource conflict(s) found affecting gpio_ich
Date: Fri, 05 Oct 2012 18:15:22 -0500 [thread overview]
Message-ID: <1349478922.23533.78.camel@petert> (raw)
In-Reply-To: <CAHFgRy975B0fPsBqRY7xW53egRpUxcLG=6DYQGawz+M4hTxWdg@mail.gmail.com>
Hi Miles,
On Thu, 2012-10-04 at 10:14 -0400, Miles Lane wrote:
> ACPI Warning: 0x0000000000000828-0x000000000000082f SystemIO conflicts
> with Region \PMIO 1 (20120711/utaddress-251)
> ACPI: If an ACPI driver is available for this device, you should use
> it instead of the native driver
> ACPI Warning: 0x0000000000000500-0x000000000000053f SystemIO conflicts
> with Region \GPIO 1 (20120711/utaddress-251)
> ACPI: If an ACPI driver is available for this device, you should use
> it instead of the native driver
> lpc_ich: Resource conflict(s) found affecting gpio_ich
Jean Delvare submitted a patch which may allow you to use the GPIO pins
in banks not claimed by the BIOS:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=4f600ada70beeb1dfe08e11e871bf31015aa0a3d
This patch is not in 3.6, but will be included in 3.7.
You could also try adding "acpi_enforce_resources=lax" or
"acpi_enforce_resources=no" to your kernel parameters to disable the
ACPI conflict checking. Note this could have other unintended
consequences.
Best,
Peter
prev parent reply other threads:[~2012-10-06 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 14:14 3.6.0+ (GIT) -- lpc_ich: Resource conflict(s) found affecting gpio_ich Miles Lane
2012-10-05 23:15 ` Peter Tyser [this message]
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=1349478922.23533.78.camel@petert \
--to=ptyser@xes-inc.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.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