From: Aaron Lu <aaron.lu@intel.com>
To: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
linux-acpi@vger.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Bastien Nocera <hadess@hadess.net>
Subject: Re: New Surface 3 (atom x7) having problems with ACPI regions
Date: Thu, 10 Sep 2015 11:46:50 +0800 [thread overview]
Message-ID: <55F0FD2A.7050900@intel.com> (raw)
In-Reply-To: <CAN+gG=FMjShOWf6LXwDd5Fps-ME4cDCtN2h6bTZRvOifhAMRtQ@mail.gmail.com>
On 09/09/2015 09:51 PM, Benjamin Tissoires wrote:
> Hey,
>
> Bastien (CC-ed) has troubles having the touchscreen of the new Surface
> 3 (atom based) showing up.
> He raised a kernel bugzilla [1] and the dmesg shows:
> ACPI Error: Region GeneralPurposeIo (ID=8) has no handler (20150619/exfldio-297)
>
> Which seems to interrupt the parsing of the DSDT.
>
> I am not sure about the status of ACPI regions in the latest acpi tree
> so I prefer asking here. Does this error actually prevents the
> touchscreen to be loaded by i2c-hid or is there something else
> preventing the enumeration?
There is GPIO operation region handler support in the kernel and
according to the dsdt table provided in bugzilla, Surface 3 is using
cherryview GPIO controller(_HID INT33FF) that is supported by the
pinctrl-cherryview driver. The problem here is, the device node NTRG is
accessing some GPIO operation region field in its _STA control method
and since _STA for ACPI device node is called very early, before any of
the GPIO drivers(where the GPIO operation region handler is installed)
are probed, the error message appeared.
I'm not so sure of the below part:
"
The failure of executing the _STA control method will cause the device
node not having the acpi_device structure created and then in the SPI
ACPI enumerate function acpi_spi_add_device, it will not be created and
used.
"
I guess we need to handle _STA for the _DEP case someway.
Regards,
Aaron
> Cheers,
> Benjamin
>
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=104291
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-09-10 3:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 13:51 New Surface 3 (atom x7) having problems with ACPI regions Benjamin Tissoires
2015-09-10 3:46 ` Aaron Lu [this message]
2015-09-10 7:35 ` Aaron Lu
2015-09-17 12:41 ` Bastien Nocera
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=55F0FD2A.7050900@intel.com \
--to=aaron.lu@intel.com \
--cc=benjamin.tissoires@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-acpi@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.