linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Mark Brown <broonie@kernel.org>,
	Ronald Tschalaer <ronald@innovation.ch>,
	Federico Lorenzi <florenzi@gmail.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Leif Liddy <leif.liddy@gmail.com>,
	Daniel Roschka <danielroschka@phoenitydawn.de>,
	linux-acpi@vger.kernel.org, linux-spi@vger.kernel.org
Subject: [PATCH 0/3] Apple SPI properties
Date: Wed, 21 Jun 2017 20:05:53 +0200	[thread overview]
Message-ID: <cover.1498044532.git.lukas@wunner.de> (raw)

Invoke an Apple-specific _DSM on ACPI scan, convert the resulting device
properties to _DSD format for further consumption by the ACPI core and
take advantage of these properties when setting up an SPI slave if _CRS
data is empty.

The series intends to pave the way for mainlining an out-of-tree driver
for the SPI keyboard built into recent MacBooks and MacBook Pros:
https://github.com/cb22/macbook12-spi-driver/

It follows up on a discussion on linux-acpi@ in March 2016.  This post
contained an excerpt of the DSDT of an affected MacBook:
https://www.spinics.net/lists/linux-spi/msg06964.html

I tested the ACPI patches extensively on my own machine.  The SPI patch
however needs a Tested-by from one of the developers of the out-of-tree
driver (cc: Ronald, Federico).  The SPI patch compiles without the ACPI
patches, so need not go in through the same tree.

Special thanks to Andy Shevchenko for doing some early reviewing of the
patches on GitHub.

Kind regards,

Lukas


Lukas Wunner (3):
  ACPI / property: Don't evaluate objects for devices w/o handle
  ACPI / property: Support Apple _DSM properties
  spi: Use Apple device properties in absence of ACPI resources

 drivers/acpi/property.c | 123 ++++++++++++++++++++++++++++++++++++++++++++++++
 drivers/spi/spi.c       |  30 ++++++++++++
 2 files changed, 153 insertions(+)

-- 
2.11.0


             reply	other threads:[~2017-06-21 18:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21 18:05 Lukas Wunner [this message]
2017-06-21 18:05 ` [PATCH 3/3] spi: Use Apple device properties in absence of ACPI resources Lukas Wunner
2017-06-22  8:10   ` Mika Westerberg
2017-06-22  8:44     ` Lukas Wunner
2017-06-22  9:28     ` Mark Brown
2017-06-21 18:05 ` [PATCH 2/3] ACPI / property: Support Apple _DSM properties Lukas Wunner
2017-06-21 23:05   ` Rafael J. Wysocki
2017-06-22  8:57     ` Lukas Wunner
2017-06-22 14:18       ` Rafael J. Wysocki
2017-06-22  8:06   ` Mika Westerberg
2017-06-22  9:54     ` Lukas Wunner
2017-06-22 10:04       ` Mika Westerberg
2017-06-22 11:24         ` Lukas Wunner
     [not found]           ` <20170622112428.q3hpwpfs4xwumued-JFq808J9C/izQB+pC5nmwQ@public.gmane.org>
2017-06-22 13:25             ` Mark Brown
2017-06-21 18:05 ` [PATCH 1/3] ACPI / property: Don't evaluate objects for devices w/o handle Lukas Wunner

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=cover.1498044532.git.lukas@wunner.de \
    --to=lukas@wunner.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=danielroschka@phoenitydawn.de \
    --cc=florenzi@gmail.com \
    --cc=leif.liddy@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=ronald@innovation.ch \
    /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).