All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephan Günther" <moepi@moepi.net>
To: linux-acpi@vger.kernel.org
Subject: [Apple] MacBook8,1 keyboard/trackpad
Date: Thu, 19 Nov 2015 23:10:16 +0100	[thread overview]
Message-ID: <47df5f3035c4c23ad05817544273df0d@localhost> (raw)

The MacBook8,1 (12" retina model, not the 13" MacBookPro12,1) released
in April 2015 has no Linux support for its internal trackpad/keyboard so
far although the 13" model (MacBookPro12,1) recently got supported.

The problem is that the internal keyboard/trackpad is connected via SPI,
which differs from previous models.


However, according to all I figured out the internal keyboard/trackpad
of the MacBookPro12,1 is connected in precisely the same way:

1) OSX reports both as SPI devices, not USB.

2) Booting Linux the input devices magically show up as USB devices for
the MacBookPro12,1 but remain completely hidden on the MacBook8,1.


I tried to track the problem by mining various kernel modules with
printks. The result for *both* MacBooks:

1) Input devices are behind pci0000:00/0000:00:15.4 (the Intel Lynxpoint
/ Wildcat Point-LP SPI controler).

2) In the ACPI namespace the input devices are located at
PNP0A08:00/INT33C1:00/APP000D:00.

3) __acpi_match_device() is called with the APPLE-SPI-TOPCASE has hwid.
That is what's behind APP000D:00. But it returns NULL and the device is
not enabled.

Now, for any reason I do not understand (I have no idea of ACPI)
anything makes the touchpad controller (bcm5974), which is that
APPLE-SPI-TOPCASE, show up as USB device on the MacBookPro12,1. But on
the MacBook8,1 nothing happens.


Request for help: is it a firmware problem, a missing identifier in the
kernel sources, or is there really no Linux support at all? Maybe it is
not even a problem with ACPI at all...

I can provide you with any logs and even dunps of the DSDT.


Best,
Stephan

                 reply	other threads:[~2015-11-19 22:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=47df5f3035c4c23ad05817544273df0d@localhost \
    --to=moepi@moepi.net \
    --cc=linux-acpi@vger.kernel.org \
    /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.