From: Prarit Bhargava <prarit-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Seth Heasley
<seth.heasley-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Janet Morgan
<janet.morgan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Janet Morgan <jamorgan-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Jean Delvare <jdelvare-l3A5Bk7waGM@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Bjorn Helgaas <bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
Myron Stowe <mstowe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Haswell systems & i801 i2c driver
Date: Mon, 07 Apr 2014 14:00:32 -0400 [thread overview]
Message-ID: <5342E7C0.4050209@redhat.com> (raw)
When loading the i801 i2c bus driver on an i5-46xx CPU, and this chipset
http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/8-series-chipset-pch-datasheet.pdf
I see the following warning:
i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ACPI: resource 0000:00:1f.3 [io 0xefa0-0xefbf] conflicts with ACPI region SMBI
[io 0xefa0-0xefaf]
ACPI: This conflict may cause random problems and system instability
ACPI: If an ACPI driver is available for this device, you should use it instead
of the native driver
It seems like the BIOS/ACPI defines a region, SMBI, which is defined for the
SMBus to use, but there is no ACPI driver available for the SMBus (at least
AFAICT).
I'm using "acpi_enforce_resources=lax" as a kernel parameter to work around
the issue but was wondering if there was a more robust fix planned for this
problem? If not -- anyone want to point me in the right direction of a fix?
Thanks,
P.
next reply other threads:[~2014-04-07 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 18:00 Prarit Bhargava [this message]
[not found] ` <5342E7C0.4050209-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-04-07 20:25 ` Haswell systems & i801 i2c driver Bjorn Helgaas
2014-04-07 20:30 ` Matthew Garrett
2014-04-07 20:56 ` Jean Delvare
[not found] ` <20140407225620.23d52a0c-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2014-04-09 16:21 ` Prarit Bhargava
2014-04-07 20:28 ` Heasley, Seth
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=5342E7C0.4050209@redhat.com \
--to=prarit-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=jamorgan-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=janet.morgan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=jdelvare-l3A5Bk7waGM@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mstowe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=seth.heasley-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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).