From: Matthew Garrett <matthew.garrett@nebula.com>
To: "bhelgaas@google.com" <bhelgaas@google.com>
Cc: "jamorgan@redhat.com" <jamorgan@redhat.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"seth.heasley@intel.com" <seth.heasley@intel.com>,
"jdelvare@suse.de" <jdelvare@suse.de>,
"prarit@redhat.com" <prarit@redhat.com>,
"janet.morgan@intel.com" <janet.morgan@intel.com>,
"mstowe@redhat.com" <mstowe@redhat.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: Haswell systems & i801 i2c driver
Date: Mon, 7 Apr 2014 20:30:39 +0000 [thread overview]
Message-ID: <1396902638.5276.2.camel@x230> (raw)
In-Reply-To: <CAErSpo5jjo0HBeQTtTkiLdqk6vg+K51rXSF+qEbkwmM+QY1Acw@mail.gmail.com>
> If this is on a shipping BIOS, we might need to figure out some way to
> handle it. I don't remember anything in the ACPI spec that talks
> about issues like this, but maybe we should add something in PCI that
> notices if there's an ACPI device with the same resources and marks
> the PCI device to keep us from moving it or assigning a driver (maybe
> the warning you're seeing already handles the driver part?)
This is, sadly, pretty typical. SMBus devices are often exposed via PCI
even though they're accessed directly via AML. The current behaviour
seems about as good as it gets - we warn the user that this could cause
problems, and they can pass a kernel parameter that allows them to do it
anyway.
--
Matthew Garrett <matthew.garrett@nebula.com>
next prev parent reply other threads:[~2014-04-07 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5342E7C0.4050209@redhat.com>
[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 [this message]
2014-04-07 20:56 ` Jean Delvare
[not found] ` <20140407225620.23d52a0c-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2014-04-09 16:21 ` Prarit Bhargava
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=1396902638.5276.2.camel@x230 \
--to=matthew.garrett@nebula.com \
--cc=bhelgaas@google.com \
--cc=jamorgan@redhat.com \
--cc=janet.morgan@intel.com \
--cc=jdelvare@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mstowe@redhat.com \
--cc=prarit@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=seth.heasley@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;
as well as URLs for NNTP newsgroup(s).