From: Aaron Sierra <asierra@xes-inc.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: "Peter Hurley" <peter@hurleysoftware.com>,
"Samuel Ortiz" <sameo@linux.intel.com>,
"Agócs Pál" <agocs.pal.86@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>
Subject: Re: [PATCH v3] lpc_ich: fix gpio base and control offsets
Date: Fri, 25 Jan 2013 09:22:54 -0600 (CST) [thread overview]
Message-ID: <b1a97ba8-e8d4-4421-8d7c-633ecdfa318a@zimbra> (raw)
In-Reply-To: <1359121338.883.8.camel@x61.thuisdomein>
> On Fri, 2013-01-25 at 14:25 +0100, Paul Bolle wrote:
> > 0) insmod-ing an updated lpc_ich.ko generated quite a bit of noise
> > in
> > dmesg:
> > <6>[19913.247530] iTCO_wdt: Found a ICH8M-E TCO device
> > (Version=2, TCOBASE=0x1060)
> > <6>[19913.249310] iTCO_wdt: initialized. heartbeat=30 sec
> > (nowayout=0)
> > <4>[19913.249332] ACPI Warning:
> > 0x0000000000001028-0x000000000000102f SystemIO conflicts with
> > Region \_SB_.PCI0.LPC_.PMIO 1 (20120913/utaddress-251)
> > <6>[19913.249338] ACPI: If an ACPI driver is available for this
> > device, you should use it instead of the native driver
> > <4>[19913.249342] ACPI Warning:
> > 0x00000000000011b0-0x00000000000011bf SystemIO conflicts with
> > Region \_SB_.PCI0.LPC_.LPIO 1 (20120913/utaddress-251)
> > <6>[19913.249347] ACPI: If an ACPI driver is available for this
> > device, you should use it instead of the native driver
> > <4>[19913.249349] ACPI Warning:
> > 0x0000000000001180-0x00000000000011af SystemIO conflicts with
> > Region \_SB_.PCI0.LPC_.LPIO 1 (20120913/utaddress-251)
> > <6>[19913.249353] ACPI: If an ACPI driver is available for this
> > device, you should use it instead of the native driver
> > <4>[19913.249355] lpc_ich: Resource conflict(s) found affecting
> > gpio_ich
> >
> > I have no idea whatsoever what that could mean.
>
> But please note that these messages are nothing new. I found
> identical
> messages in all my logs (from v3.7.y kernels; I do not seem to have
> logs
> of older releases anymore).
>
>
> Paul Bolle
Paul,
My understanding of these warnings is that your BIOS defines regions
in its ACPI tables that coincide with regions we want to pass to
gpio-ich. Because the regions are defined in the ACPI tables Linux
assumes that they are actively being used by the BIOS and that they
shouldn't be used, unless you tell the kernel to globally ignore
ACPI resource conflicts.
Similar warnings used to also appear for the TCO watchdog regions until
that was determined to be a regression and the ACPI resource conflict
checks were removed by this patch:
commit 092369efbd6ef6b4a215741ce9f65446bf45beff
Author: Feng Tang <feng.tang@intel.com>
Date: Thu Aug 16 15:50:10 2012 +0800
mfd: lpc_ich: Fix a 3.5 kernel regression for iTCO_wdt driver
[trimmed]
Actually the same check could be removed for the gpio-ich in lpc_ich.c,
but I'm not sure if it will cause problems.
Like Feng, I also am not sure if removing the checks for GPIO would cause
problems, so the noise remains.
-Aaron S.
next prev parent reply other threads:[~2013-01-25 15:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b9fec05c-d383-4282-b2af-c95855ff6abb@zimbra>
2013-01-24 20:52 ` Aaron Sierra
2013-01-25 9:47 ` Linus Walleij
2013-01-25 10:04 ` Paul Bolle
2013-01-25 11:06 ` Linus Walleij
2013-01-25 12:00 ` Paul Bolle
2013-01-25 12:43 ` Linus Walleij
2013-01-25 13:25 ` Paul Bolle
2013-01-25 13:42 ` Paul Bolle
2013-01-25 15:22 ` Aaron Sierra [this message]
2013-01-28 11:41 ` Paul Bolle
2013-01-25 13:44 ` Peter Hurley
2013-01-25 15:28 ` Peter Hurley
2013-01-25 16:48 ` Samuel Ortiz
2013-01-28 10:11 ` Linus Walleij
2013-01-28 11:45 ` Paul Bolle
2013-02-03 17:02 ` Samuel Ortiz
2013-02-04 15:38 ` Aaron Sierra
2013-02-14 22:48 ` Anatol Pomozov
2013-02-15 10:16 ` Samuel Ortiz
2013-02-15 14:28 ` Anatol Pomozov
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=b1a97ba8-e8d4-4421-8d7c-633ecdfa318a@zimbra \
--to=asierra@xes-inc.com \
--cc=agocs.pal.86@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=peter@hurleysoftware.com \
--cc=sameo@linux.intel.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
all inboxes | Powered by JetHome®