linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Jean Delvare <jdelvare@suse.de>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Wolfram Sang <wsa@the-dreams.de>,
	Jarkko Nikula <jarkko.nikula@linux.intel.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Andy Lutomirski <luto@kernel.org>,
	Mario Limonciello <mario_limonciello@dell.com>,
	Matt Fleming <matt@codeblueprint.co.uk>,
	linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [v5] i2c: i801: Allow ACPI SystemIO OpRegion to conflict with PCI BAR
Date: Tue, 5 Jul 2016 13:56:58 +0200	[thread overview]
Message-ID: <201607051356.58794@pali> (raw)
In-Reply-To: <20160705115142.GO23527@lahna.fi.intel.com>

[-- Attachment #1: Type: Text/Plain, Size: 2486 bytes --]

On Tuesday 05 July 2016 13:51:42 Mika Westerberg wrote:
> On Tue, Jul 05, 2016 at 01:30:23PM +0200, Pali Rohár wrote:
> > On Tuesday 05 July 2016 12:14:55 Mika Westerberg wrote:
> > > The whole point of this patch is that we expect that nobody never
> > > uses that OpRegion. I'm 99% sure you don't find a single machine
> > > where it is actually in use.
> > 
> > HP EliteBook 8460p uses it for sure! Here are DSDT snips:
> >                 Method (\_SB.PCI0.LPCB.SMAB, 3, Serialized)
> >                 {
> >                 
> >                     If (LEqual (And (Arg0, 0x01), 0x00))
> >                     {
> >                     
> >                         Store (0x01, Local0)
> >                         Store (\_SB.PCI0.SBUS.SWRB (Arg0, Arg1,
> >                         Arg2), Local1) If (Local1)
> >                         {
> >                         
> >                             Store (0x00, Local0)
> >                         
> >                         }
> >                     
> >                     }
> >                     Else
> >                     {
> >                     
> >                         Store (\_SB.PCI0.SBUS.SRDB (Arg0, Arg1),
> >                         Local0)
> >                     
> >                     }
> >                     
> >                     Return (Local0)
> >                 
> >                 }
> 
> Crap, well that is in that 1% then ;-)

I bet that every HP notebook with accelerometer which is used by 
hp_accel.ko driver is affected by this problem. And then it will be more 
then 1% :-)

> > ...
> > 
> >                 Method (ALRD, 1, Serialized)
> >                 {
> >                 
> >                     Store (\_SB.PCI0.LPCB.SMAB (0x33, Arg0, 0x00),
> >                     Local0) Return (Local0)
> >                 
> >                 }
> >                 
> >                 Method (ALWR, 2, Serialized)
> >                 {
> >                 
> >                     Store (\_SB.PCI0.LPCB.SMAB (0x32, Arg0, Arg1),
> >                     Local0) Return (Local0)
> >                 
> >                 }
> > 
> > And ALRD and ALWR methods are used by hp_accel.ko kernel driver.
> 
> So are you able to test what happens when you unload the driver?

As I wrote in previous email, I do not own these EliteBooks anymore, so 
cannot test it. Just have DSDT dump...

-- 
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2016-07-05 11:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-23  8:04 [PATCH v5] i2c: i801: Allow ACPI SystemIO OpRegion to conflict with PCI BAR Mika Westerberg
2016-06-08 16:29 ` [v5] " Benjamin Tissoires
2016-06-09  8:15   ` Mika Westerberg
2016-06-13  9:19   ` Jean Delvare
2016-06-13  9:45     ` Pali Rohár
2016-06-13  9:46       ` Mika Westerberg
2016-06-13  9:48         ` Pali Rohár
2016-06-13  9:54           ` Mika Westerberg
2016-06-24 14:12             ` Jean Delvare
2016-06-29  7:56               ` Pali Rohár
2016-06-29 10:39               ` Mika Westerberg
2016-07-04  8:22                 ` Jean Delvare
2016-07-04 14:30                   ` Pali Rohár
2016-07-05 10:14                   ` Mika Westerberg
2016-07-05 11:30                     ` Pali Rohár
2016-07-05 11:51                       ` Mika Westerberg
2016-07-05 11:56                         ` Pali Rohár [this message]
2016-07-05 12:00                           ` Pali Rohár
2016-07-05 14:31                             ` Mika Westerberg
2016-07-24 10:08                               ` Martin Vajnar
2016-07-25 10:19                                 ` Pali Rohár
2016-07-14 11:52                             ` Pali Rohár
2016-07-14 14:20                               ` Rafael J. Wysocki
2016-07-25 10:22                   ` Pali Rohár

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=201607051356.58794@pali \
    --to=pali.rohar@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=jdelvare@suse.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mario_limonciello@dell.com \
    --cc=matt@codeblueprint.co.uk \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rjw@rjwysocki.net \
    --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).