From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Ben Gamari <ben@smart-cactus.org>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>
Subject: Re: OpRegion conflicts for Skylake LPSS
Date: Tue, 26 Apr 2016 18:54:37 +0300 [thread overview]
Message-ID: <20160426155437.GA10202@lahna.fi.intel.com> (raw)
In-Reply-To: <87lh41nqqq.fsf@smart-cactus.org>
On Tue, Apr 26, 2016 at 02:44:13AM +0200, Ben Gamari wrote:
>
> While trying to troubleshoot some touchpad issues on a Dell Latitude
> E7470 (namely the touchpad being exposed only as a PS/2 device) I
> noticed that the intel-lpss driver (using a 4.6-rc4 kernel) fails to
> load with,
>
> ACPI Warning: SystemMemory range 0x00000000FE028000-0x00000000FE0281FF conflicts with OpRegion 0x00000000FE028000-0x00000000FE028207 (\_SB.PCI0.GEXP.BAR0) (20160108/utaddress-255)
> ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
> intel-lpss: probe of INT3446:00 failed with error -16
>
> The DSDT OpRegion in question looks like this,
>
> Scope (_SB.PCI0)
> {
> Device (GEXP)
> {
> Name (_ADR, One) // _ADR: Address
> Name (_STA, 0x0B) // _STA: Status
> OperationRegion (BAR0, SystemMemory, SB04, 0x0208)
> Field (BAR0, DWordAcc, NoLock, Preserve)
> {
> ICON, 32,
> TAR, 32,
> Offset (0x10),
> DATA, 32,
> HCNT, 32,
> LCNT, 32,
> Offset (0x2C),
> , 5,
> ABRT, 1,
> Offset (0x40),
> RBCK, 32,
> Offset (0x54),
> CLR, 32,
> Offset (0x6C),
> ENB, 1,
> Offset (0x70),
> ACTV, 1,
> TFNF, 1,
> , 1,
> RFNE, 1,
> Offset (0x7C),
> HOLD, 32,
> Offset (0x9C),
> ENSB, 1,
> Offset (0x204),
> RST, 32
> }
>
> It looks very much like these are describing the same device. Perhaps
> the lpss driver should be binding to this ACPI node? Or perhaps this is
> a firmware issue? Any guidance would be greatly appreciated.
Can you send me full acpidump of that machine?
next parent reply other threads:[~2016-04-26 15:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87lh41nqqq.fsf@smart-cactus.org>
2016-04-26 15:54 ` Mika Westerberg [this message]
2016-04-26 21:10 ` OpRegion conflicts for Skylake LPSS Ben Gamari
2016-04-29 7:30 ` Ben Gamari
2016-04-29 7:42 ` Mika Westerberg
2016-04-30 22:47 ` Ben Gamari
2016-05-02 10:35 ` Mika Westerberg
2020-10-01 22:10 ` Laurent Pinchart
2020-10-02 10:35 ` Andy Shevchenko
2020-10-02 12:26 ` Laurent Pinchart
2020-10-07 0:35 ` Laurent Pinchart
2020-10-09 21:12 ` Laurent Pinchart
2021-01-11 22:29 ` Laurent Pinchart
2021-01-12 11:35 ` Andy Shevchenko
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=20160426155437.GA10202@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ben@smart-cactus.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@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).