linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benson Leung <bleung@google.com>
To: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Cc: dmitry.torokhov@gmail.com, bleung@chromium.org
Subject: [GIT PULL] chrome-platform updates for v4.18
Date: Sun, 3 Jun 2018 20:41:00 -0700	[thread overview]
Message-ID: <20180604034100.GA158510@decatoncale.mtv.corp.google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2529 bytes --]

Hi Linus,

The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:

  Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/bleung/chrome-platform.git tags/chrome-platform-for-linus-4.18

for you to fetch changes up to 79a3d60300fc28def9b58dc30d86274b47052422:

  platform/chrome: Use to_cros_ec_dev more broadly (2018-05-30 11:53:40 -0700)

----------------------------------------------------------------
Changes to chrome-platform for v4.18

Further changes from Dmitry related to the removal of platform data from
atmel_mxt_ts and chromeos_laptop. This time, we have some changes that
teach chromeos_laptop how to supply acpi properties for some input devices
so that the peripheral driver doesn't have to do dmi matching on some
Chromebook platforms.

Also adds the Chromebook Tablet switch driver, which is useful for x86
convertible Chromebooks.

Other misc. cleanup.

Thanks,
Benson

----------------------------------------------------------------
Arnd Bergmann (1):
      platform: chrome: Add input dependency for tablet switch driver

Benson Leung (2):
      platform/chrome: chromeos_tbmc - add SPDX identifier
      Merge branch 'ib-chrome-platform-atmel-mxt-ts-device-properties' into working-branch-for-4.18

Dmitry Torokhov (3):
      platform/chrome: cros_ec_lpc: do not try DMI match when ACPI device found
      platform/chrome: chromeos_laptop - supply properties for ACPI devices
      platform/chrome: chromeos_laptop: fix touchpad button mapping on Celes

Gwendal Grignou (2):
      platform: chrome: Add Tablet Switch ACPI driver
      platform/chrome: Use to_cros_ec_dev more broadly

 drivers/platform/chrome/Kconfig            |  11 +
 drivers/platform/chrome/Makefile           |   1 +
 drivers/platform/chrome/chromeos_laptop.c  | 315 ++++++++++++++++++++++++++---
 drivers/platform/chrome/chromeos_tbmc.c    | 111 ++++++++++
 drivers/platform/chrome/cros_ec_lightbar.c |  21 +-
 drivers/platform/chrome/cros_ec_lpc.c      |  13 +-
 drivers/platform/chrome/cros_ec_sysfs.c    |   2 -
 drivers/platform/chrome/cros_ec_vbc.c      |   9 +-
 include/linux/mfd/cros_ec.h                |   2 +
 9 files changed, 428 insertions(+), 57 deletions(-)
 create mode 100644 drivers/platform/chrome/chromeos_tbmc.c

-- 
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2018-06-04  3:41 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=20180604034100.GA158510@decatoncale.mtv.corp.google.com \
    --to=bleung@google.com \
    --cc=bleung@chromium.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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).