All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Armstrong <narmstrong@baylibre.com>
To: airlied@linux.ie, hans.verkuil@cisco.com, lee.jones@linaro.org,
	olof@lixom.net, seanpaul@google.com
Cc: Neil Armstrong <narmstrong@baylibre.com>,
	sadolfsson@google.com, felixe@google.com, bleung@google.com,
	darekm@google.com, marcheu@chromium.org, fparent@baylibre.com,
	dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/5] Add ChromeOS EC CEC Support
Date: Tue, 15 May 2018 00:40:34 +0200	[thread overview]
Message-ID: <1526337639-3568-1-git-send-email-narmstrong@baylibre.com> (raw)

Hi All,

The new Google "Fizz" Intel-based ChromeOS device is gaining CEC support
throught it's Embedded Controller, to enable the Linux CEC Core to communicate
with it and get the CEC Physical Address from the correct HDMI Connector, the
following must be added/changed:
- Add the CEC sub-device registration in the ChromeOS EC MFD Driver
- Add the CEC related commands and events definitions into the EC MFD driver
- Add a way to get a CEC notifier with it's (optional) connector name
- Add the CEC notifier to the i915 HDMI driver
- Add the proper ChromeOS EC CEC Driver

The CEC notifier with the connector name is the tricky point, since even on
Device-Tree platforms, there is no way to distinguish between multiple HDMI
connectors from the same DRM driver. The solution I implemented is pretty
simple and only adds an optional connector name to eventually distinguish
an HDMI connector notifier from another if they share the same device.

Feel free to comment this patchset !

Neil Armstrong (5):
  mfd: cros_ec_dev: Add CEC sub-device registration
  media: cec-notifier: Get notifier by device and connector name
  drm/i915: hdmi: add CEC notifier to intel_hdmi
  mfd: cros-ec: Introduce CEC commands and events definitions.
  media: platform: Add Chrome OS EC CEC driver

 drivers/gpu/drm/i915/intel_drv.h             |   2 +
 drivers/gpu/drm/i915/intel_hdmi.c            |  10 +
 drivers/media/cec/cec-notifier.c             |  30 ++-
 drivers/media/platform/Kconfig               |  11 +
 drivers/media/platform/Makefile              |   2 +
 drivers/media/platform/cros-ec/Makefile      |   1 +
 drivers/media/platform/cros-ec/cros-ec-cec.c | 331 +++++++++++++++++++++++++++
 drivers/mfd/cros_ec_dev.c                    |  16 ++
 drivers/platform/chrome/cros_ec_proto.c      |  42 +++-
 include/linux/mfd/cros_ec.h                  |   2 +-
 include/linux/mfd/cros_ec_commands.h         |  80 +++++++
 include/media/cec-notifier.h                 |  44 +++-
 12 files changed, 556 insertions(+), 15 deletions(-)
 create mode 100644 drivers/media/platform/cros-ec/Makefile
 create mode 100644 drivers/media/platform/cros-ec/cros-ec-cec.c

-- 
2.7.4

WARNING: multiple messages have this Message-ID (diff)
From: Neil Armstrong <narmstrong@baylibre.com>
To: airlied@linux.ie, hans.verkuil@cisco.com, lee.jones@linaro.org,
	olof@lixom.net, seanpaul@google.com
Cc: Neil Armstrong <narmstrong@baylibre.com>,
	sadolfsson@google.com, intel-gfx@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	fparent@baylibre.com, felixe@google.com, marcheu@chromium.org,
	bleung@google.com, darekm@google.com,
	linux-media@vger.kernel.org
Subject: [RFC PATCH 0/5] Add ChromeOS EC CEC Support
Date: Tue, 15 May 2018 00:40:34 +0200	[thread overview]
Message-ID: <1526337639-3568-1-git-send-email-narmstrong@baylibre.com> (raw)

Hi All,

The new Google "Fizz" Intel-based ChromeOS device is gaining CEC support
throught it's Embedded Controller, to enable the Linux CEC Core to communicate
with it and get the CEC Physical Address from the correct HDMI Connector, the
following must be added/changed:
- Add the CEC sub-device registration in the ChromeOS EC MFD Driver
- Add the CEC related commands and events definitions into the EC MFD driver
- Add a way to get a CEC notifier with it's (optional) connector name
- Add the CEC notifier to the i915 HDMI driver
- Add the proper ChromeOS EC CEC Driver

The CEC notifier with the connector name is the tricky point, since even on
Device-Tree platforms, there is no way to distinguish between multiple HDMI
connectors from the same DRM driver. The solution I implemented is pretty
simple and only adds an optional connector name to eventually distinguish
an HDMI connector notifier from another if they share the same device.

Feel free to comment this patchset !

Neil Armstrong (5):
  mfd: cros_ec_dev: Add CEC sub-device registration
  media: cec-notifier: Get notifier by device and connector name
  drm/i915: hdmi: add CEC notifier to intel_hdmi
  mfd: cros-ec: Introduce CEC commands and events definitions.
  media: platform: Add Chrome OS EC CEC driver

 drivers/gpu/drm/i915/intel_drv.h             |   2 +
 drivers/gpu/drm/i915/intel_hdmi.c            |  10 +
 drivers/media/cec/cec-notifier.c             |  30 ++-
 drivers/media/platform/Kconfig               |  11 +
 drivers/media/platform/Makefile              |   2 +
 drivers/media/platform/cros-ec/Makefile      |   1 +
 drivers/media/platform/cros-ec/cros-ec-cec.c | 331 +++++++++++++++++++++++++++
 drivers/mfd/cros_ec_dev.c                    |  16 ++
 drivers/platform/chrome/cros_ec_proto.c      |  42 +++-
 include/linux/mfd/cros_ec.h                  |   2 +-
 include/linux/mfd/cros_ec_commands.h         |  80 +++++++
 include/media/cec-notifier.h                 |  44 +++-
 12 files changed, 556 insertions(+), 15 deletions(-)
 create mode 100644 drivers/media/platform/cros-ec/Makefile
 create mode 100644 drivers/media/platform/cros-ec/cros-ec-cec.c

-- 
2.7.4

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-05-14 22:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14 22:40 Neil Armstrong [this message]
2018-05-14 22:40 ` [RFC PATCH 0/5] Add ChromeOS EC CEC Support Neil Armstrong
2018-05-14 22:40 ` [RFC PATCH 1/5] mfd: cros_ec_dev: Add CEC sub-device registration Neil Armstrong
2018-05-14 22:40   ` Neil Armstrong
2018-05-14 22:40 ` [RFC PATCH 2/5] media: cec-notifier: Get notifier by device and connector name Neil Armstrong
2018-05-14 22:40   ` Neil Armstrong
2018-05-15  6:27   ` Hans Verkuil
2018-05-15  7:28     ` Neil Armstrong
2018-05-15  7:28       ` Neil Armstrong
2018-05-14 22:40 ` [RFC PATCH 3/5] drm/i915: hdmi: add CEC notifier to intel_hdmi Neil Armstrong
2018-05-14 22:40   ` Neil Armstrong
2018-05-15  6:29   ` Hans Verkuil
2018-05-15  6:29     ` Hans Verkuil
2018-05-15  7:30     ` Neil Armstrong
2018-05-15  7:30       ` Neil Armstrong
2018-05-15  6:34   ` Hans Verkuil
2018-05-15  6:34     ` Hans Verkuil
2018-05-15  7:29     ` Neil Armstrong
2018-05-15  7:29       ` Neil Armstrong
2018-05-14 22:40 ` [RFC PATCH 4/5] mfd: cros-ec: Introduce CEC commands and events definitions Neil Armstrong
2018-05-14 22:40   ` Neil Armstrong
2018-05-14 22:40 ` [RFC PATCH 5/5] media: platform: Add Chrome OS EC CEC driver Neil Armstrong
2018-05-14 22:40   ` Neil Armstrong
2018-05-15  6:58   ` Hans Verkuil
2018-05-15  6:58     ` Hans Verkuil
2018-05-15  7:25     ` Neil Armstrong
2018-05-15  7:25       ` Neil Armstrong
2018-05-15  8:10       ` Hans Verkuil
2018-05-15  8:10         ` Hans Verkuil
2018-05-15  8:28         ` Neil Armstrong
2018-05-15  8:28           ` Neil Armstrong
2018-05-15  8:30           ` Hans Verkuil
2018-05-15  8:30             ` Hans Verkuil
2018-05-14 22:59 ` ✗ Fi.CI.CHECKPATCH: warning for Add ChromeOS EC CEC Support Patchwork
2018-05-14 23:18 ` ✓ Fi.CI.BAT: success " Patchwork
2018-05-15  6:22 ` ✗ Fi.CI.IGT: failure " Patchwork

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=1526337639-3568-1-git-send-email-narmstrong@baylibre.com \
    --to=narmstrong@baylibre.com \
    --cc=airlied@linux.ie \
    --cc=bleung@google.com \
    --cc=darekm@google.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=felixe@google.com \
    --cc=fparent@baylibre.com \
    --cc=hans.verkuil@cisco.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=marcheu@chromium.org \
    --cc=olof@lixom.net \
    --cc=sadolfsson@google.com \
    --cc=seanpaul@google.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.