linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benson Leung <bleung@google.com>
To: torvalds@linux-foundation.org
Cc: bleung@kernel.org, bleung@chromium.org, bleung@google.com,
	enric.balletbo@collabora.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL] chrome-platform changes for v5.6
Date: Mon, 3 Feb 2020 15:14:30 -0800	[thread overview]
Message-ID: <20200203231430.GA205960@google.com> (raw)

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

Hi Linus,

The following changes since commit e42617b825f8073569da76dc4510bfa019b1c35a:

  Linux 5.5-rc1 (2019-12-08 14:57:55 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git tags/tag-chrome-platform-for-v5.6

for you to fetch changes up to 034dbec179e5d2820480f477c43acbc50245e56d:

  platform/chrome: cros_ec: Match implementation with headers (2020-02-03 17:14:50 +0100)

----------------------------------------------------------------
chrome platform changes for 5.6

* CrOS EC
- Refactoring of some of cros_ec's headers. include/linux/mfd/cros_ec.h now
  removed, new cros_ec.h added drivers/platform/chrome which contains shared
  operations of cros_ec transport drivers.
- Response tracing in cros_ec_proto

* Wilco EC
- Fix unregistration order.
- Fix keyboard backlight probing on systems without keyboard backlight
- Minor cleanup (newlines in printks, COMPILE_TEST)

* Misc
- chromeos_laptop converted to use i2c_new_scanned_device instead of
  i2c_new_probed_device

----------------------------------------------------------------
Ben Dooks (Codethink) (1):
      platform/chrome: cros_ec_ishtp: Make init_lock static

Benson Leung (1):
      Merge branch 'chrome-platform-5.5-fixes' into for-kernelci

Daniel Campello (2):
      platform/chrome: wilco_ec: Fix unregistration order
      platform/chrome: wilco_ec: Fix keyboard backlight probing

Enric Balletbo i Serra (4):
      platform/chrome: cros_ec_trace: Match trace commands with EC commands
      platform/chrome: cros_ec_lpc: Use platform_get_irq_optional() for optional IRQs
      cros_ec: treewide: Remove 'include/linux/mfd/cros_ec.h'
      platform/chrome: cros_ec: Match implementation with headers

Raul E Rangel (1):
      platform/chrome: cros_ec_proto: Add response tracing

Stephen Boyd (3):
      platform/chrome: wilco_ec: Add newlines to printks
      platform/chrome: wilco_ec: Allow wilco to be compiled in COMPILE_TEST
      platform/chrome: cros_ec: Drop unaligned.h include

Wolfram Sang (1):
      platform/chrome: chromeos_laptop: Convert to i2c_new_scanned_device

 drivers/iio/accel/cros_ec_accel_legacy.c           |  1 -
 .../iio/common/cros_ec_sensors/cros_ec_sensors.c   |  1 -
 .../common/cros_ec_sensors/cros_ec_sensors_core.c  |  1 -
 drivers/iio/light/cros_ec_light_prox.c             |  1 -
 drivers/iio/pressure/cros_ec_baro.c                |  1 -
 drivers/media/platform/cros-ec-cec/cros-ec-cec.c   |  1 -
 drivers/mfd/cros_ec_dev.c                          |  1 -
 drivers/platform/chrome/chromeos_laptop.c          | 18 ++--
 drivers/platform/chrome/cros_ec.c                  |  3 +-
 drivers/platform/chrome/cros_ec.h                  | 19 +++++
 drivers/platform/chrome/cros_ec_chardev.c          |  1 -
 drivers/platform/chrome/cros_ec_debugfs.c          |  1 -
 drivers/platform/chrome/cros_ec_i2c.c              |  2 +
 drivers/platform/chrome/cros_ec_ishtp.c            |  4 +-
 drivers/platform/chrome/cros_ec_lightbar.c         |  1 -
 drivers/platform/chrome/cros_ec_lpc.c              |  3 +-
 drivers/platform/chrome/cros_ec_proto.c            |  6 +-
 drivers/platform/chrome/cros_ec_rpmsg.c            |  2 +
 drivers/platform/chrome/cros_ec_sensorhub.c        |  1 -
 drivers/platform/chrome/cros_ec_spi.c              |  2 +
 drivers/platform/chrome/cros_ec_sysfs.c            |  1 -
 drivers/platform/chrome/cros_ec_trace.c            | 97 ++++++++++++++++++++--
 drivers/platform/chrome/cros_ec_trace.h            | 26 ++++--
 drivers/platform/chrome/cros_ec_vbc.c              |  1 -
 drivers/platform/chrome/cros_usbpd_logger.c        |  1 -
 drivers/platform/chrome/wilco_ec/Kconfig           |  3 +-
 drivers/platform/chrome/wilco_ec/core.c            |  4 +-
 drivers/platform/chrome/wilco_ec/keyboard_leds.c   | 32 ++++---
 drivers/platform/chrome/wilco_ec/mailbox.c         |  4 +-
 drivers/platform/chrome/wilco_ec/telemetry.c       |  6 +-
 drivers/power/supply/cros_usbpd-charger.c          |  1 -
 drivers/rtc/rtc-cros-ec.c                          |  1 -
 include/linux/mfd/cros_ec.h                        | 35 --------
 include/linux/platform_data/cros_ec_proto.h        | 29 +++++--
 34 files changed, 208 insertions(+), 103 deletions(-)
 create mode 100644 drivers/platform/chrome/cros_ec.h
 delete mode 100644 include/linux/mfd/cros_ec.h

-- 
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: 228 bytes --]

             reply	other threads:[~2020-02-03 23:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03 23:14 Benson Leung [this message]
2020-02-04  8:05 ` [GIT PULL] chrome-platform changes for v5.6 pr-tracker-bot

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=20200203231430.GA205960@google.com \
    --to=bleung@google.com \
    --cc=bleung@chromium.org \
    --cc=bleung@kernel.org \
    --cc=enric.balletbo@collabora.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).