From: Lee Jones <lee.jones@linaro.org>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: seanpaul@google.com, fparent@baylibre.com, airlied@linux.ie,
sadolfsson@google.com, intel-gfx@lists.freedesktop.org,
eballetbo@gmail.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Stefan Adolfsson <sadolfsson@chromium.org>,
felixe@google.com, hans.verkuil@cisco.com, olof@lixom.net,
bleung@google.com, darekm@google.com,
linux-media@vger.kernel.org
Subject: Re: [PATCH v8 3/6] mfd: cros-ec: Increase maximum mkbp event size
Date: Thu, 12 Jul 2018 13:26:18 +0100 [thread overview]
Message-ID: <20180712122618.GD4641@dell> (raw)
In-Reply-To: <1530716901-30164-4-git-send-email-narmstrong@baylibre.com>
On Wed, 04 Jul 2018, Neil Armstrong wrote:
> Having a 16 byte mkbp event size makes it possible to send CEC
> messages from the EC to the AP directly inside the mkbp event
> instead of first doing a notification and then a read.
>
> Signed-off-by: Stefan Adolfsson <sadolfsson@chromium.org>
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
> Tested-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
> ---
> drivers/platform/chrome/cros_ec_proto.c | 40 +++++++++++++++++++++++++--------
> include/linux/mfd/cros_ec.h | 2 +-
> include/linux/mfd/cros_ec_commands.h | 16 +++++++++++++
> 3 files changed, 48 insertions(+), 10 deletions(-)
For my own reference:
Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-07-12 12:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 15:08 [PATCH v8 0/6] Add ChromeOS EC CEC Support Neil Armstrong
2018-07-04 15:08 ` [PATCH v8 1/6] media: cec-notifier: Get notifier by device and connector name Neil Armstrong
2018-07-04 15:08 ` [PATCH v8 2/6] drm/i915: hdmi: add CEC notifier to intel_hdmi Neil Armstrong
2018-07-04 15:08 ` [PATCH v8 3/6] mfd: cros-ec: Increase maximum mkbp event size Neil Armstrong
2018-07-12 12:26 ` Lee Jones [this message]
2018-07-04 15:08 ` [PATCH v8 4/6] mfd: cros-ec: Introduce CEC commands and events definitions Neil Armstrong
2018-07-04 15:08 ` [PATCH v8 5/6] mfd: cros_ec_dev: Add CEC sub-device registration Neil Armstrong
2018-07-04 15:08 ` [PATCH v8 6/6] media: platform: Add ChromeOS EC CEC driver Neil Armstrong
2018-07-04 15:10 ` ✗ Fi.CI.BAT: failure for Add ChromeOS EC CEC Support (rev9) Patchwork
2018-07-12 12:26 ` [PATCH v8 0/6] Add ChromeOS EC CEC Support Lee Jones
2018-07-12 12:42 ` Neil Armstrong
2018-07-12 13:02 ` Hans Verkuil
2018-07-13 7:46 ` [GIT PULL] Immutable branch between MFD and DRM/i915, Media and Platform due for the v4.19 merge window Lee Jones
2018-07-16 7:38 ` Neil Armstrong
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=20180712122618.GD4641@dell \
--to=lee.jones@linaro.org \
--cc=airlied@linux.ie \
--cc=bleung@google.com \
--cc=darekm@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eballetbo@gmail.com \
--cc=felixe@google.com \
--cc=fparent@baylibre.com \
--cc=hans.verkuil@cisco.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=olof@lixom.net \
--cc=sadolfsson@chromium.org \
--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 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).