From: Greg KH <gregkh@linuxfoundation.org>
To: Jean Delvare <jdelvare@suse.de>
Cc: stable@vger.kernel.org, mika.westerberg@linux.intel.com,
benjamin.tissoires@redhat.com, luto@kernel.org,
pali.rohar@gmail.com, rafael.j.wysocki@intel.com,
wsa@the-dreams.de
Subject: Re: [PATCH v4.4+v4.6] i2c: i801: Allow ACPI SystemIO OpRegion to conflict with PCI BAR
Date: Sun, 14 Aug 2016 17:02:55 +0200 [thread overview]
Message-ID: <20160814150255.GI27230@kroah.com> (raw)
In-Reply-To: <20160728115111.5ccb8299@endymion>
On Thu, Jul 28, 2016 at 11:51:11AM +0200, Jean Delvare wrote:
> Upstream commit: a7ae81952cdab56a1277bd2f9ed7284c0f575120
>
> Many Intel systems the BIOS declares a SystemIO OpRegion below the SMBus
> PCI device as can be seen in ACPI DSDT table from Lenovo Yoga 900:
>
> Device (SBUS)
> {
> OperationRegion (SMBI, SystemIO, (SBAR << 0x05), 0x10)
> Field (SMBI, ByteAcc, NoLock, Preserve)
> {
> HSTS, 8,
> Offset (0x02),
> HCON, 8,
> HCOM, 8,
> TXSA, 8,
> DAT0, 8,
> DAT1, 8,
> HBDR, 8,
> PECR, 8,
> RXSA, 8,
> SDAT, 16
> }
>
> There are also bunch of AML methods that that the BIOS can use to access
> these fields. Most of the systems in question AML methods accessing the
> SMBI OpRegion are never used.
>
> Now, because of this SMBI OpRegion many systems fail to load the SMBus
> driver with an error looking like one below:
>
> ACPI Warning: SystemIO range 0x0000000000003040-0x000000000000305F
> conflicts with OpRegion 0x0000000000003040-0x000000000000304F
> (\_SB.PCI0.SBUS.SMBI) (20160108/utaddress-255)
> ACPI: If an ACPI driver is available for this device, you should use
> it instead of the native driver
>
> The reason is that this SMBI OpRegion conflicts with the PCI BAR used by
> the SMBus driver.
>
> It turns out that we can install a custom SystemIO address space handler
> for the SMBus device to intercept all accesses through that OpRegion. This
> allows us to share the PCI BAR with the AML code if it for some reason is
> using it. We do not expect that this OpRegion handler will ever be called
> but if it is we print a warning and prevent all access from the SMBus
> driver itself.
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=110041
> Reported-by: Andy Lutomirski <luto@kernel.org>
> Reported-by: Pali Roh�r <pali.rohar@gmail.com>
> Suggested-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Reviewed-by: Jean Delvare <jdelvare@suse.de>
> Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> Tested-by: Pali Roh�r <pali.rohar@gmail.com>
> Tested-by: Jean Delvare <jdelvare@suse.de>
> Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
> Cc: stable@vger.kernel.org
> ---
> This is a backport of upstream commit
> a7ae81952cdab56a1277bd2f9ed7284c0f575120 suitable for kernels v4.4 and
> v4.6. Thanks.
Thanks for this, now applied.
greg k-h
prev parent reply other threads:[~2016-08-14 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 9:51 [PATCH v4.4+v4.6] i2c: i801: Allow ACPI SystemIO OpRegion to conflict with PCI BAR Jean Delvare
2016-08-08 7:56 ` Mika Westerberg
2016-08-14 15:02 ` Greg KH [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=20160814150255.GI27230@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=benjamin.tissoires@redhat.com \
--cc=jdelvare@suse.de \
--cc=luto@kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=pali.rohar@gmail.com \
--cc=rafael.j.wysocki@intel.com \
--cc=stable@vger.kernel.org \
--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).