From: Ben Gamari <ben@smart-cactus.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
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 23:10:47 +0200 [thread overview]
Message-ID: <87eg9snkiw.fsf@smart-cactus.org> (raw)
In-Reply-To: <20160426155437.GA10202@lahna.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
Mika Westerberg <mika.westerberg@linux.intel.com> writes:
> On Tue, Apr 26, 2016 at 02:44:13AM +0200, Ben Gamari wrote:
>>
snip
>> 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?
It can be found at
https://github.com/bgamari/dell-e7470-dsdt/blob/master/acpi.log.
Cheers,
- Ben
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2016-04-26 21:11 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 ` OpRegion conflicts for Skylake LPSS Mika Westerberg
2016-04-26 21:10 ` Ben Gamari [this message]
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=87eg9snkiw.fsf@smart-cactus.org \
--to=ben@smart-cactus.org \
--cc=andriy.shevchenko@linux.intel.com \
--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=mika.westerberg@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.