From: Lee Jones <lee.jones@linaro.org>
To: egranata@google.com
Cc: Benson Leung <bleung@chromium.org>,
Olof Johansson <olof@lixom.net>,
linux-kernel@vger.kernel.org,
Gwendal Grignou <gwendal@google.com>,
Brian Norris <briannorris@google.com>,
Enrico Granata <egranata@chromium.org>
Subject: Re: [PATCH] mfd: cros_ec: Add support for MKBP more event flags
Date: Mon, 3 Dec 2018 11:08:10 +0000 [thread overview]
Message-ID: <20181203110810.GI26661@dell> (raw)
In-Reply-To: <20181129195548.204153-1-egranata@chromium.org>
On Thu, 29 Nov 2018, egranata@google.com wrote:
> From: Enrico Granata <egranata@chromium.org>
>
> The ChromeOS EC has support for signaling to the host that
> a single IRQ can serve multiple MKBP events.
>
> Doing this serves an optimization purpose, as it minimizes the
> number of round-trips into the interrupt handling machinery, and
> it proves beneficial to sensor timestamping as it keeps the desired
> synchronization of event times between the two processors.
>
> This patch adds kernel support for this EC feature, allowing the
> ec_irq to loop until all events have been served.
>
> Signed-off-by: Enrico Granata <egranata@chromium.org>
> ---
> drivers/mfd/cros_ec.c | 20 +++++++++++++--
Looks fine, in principle:
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
next prev parent reply other threads:[~2018-12-03 11:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 19:55 [PATCH] mfd: cros_ec: Add support for MKBP more event flags egranata
2018-12-03 11:08 ` Lee Jones [this message]
2018-12-07 22:22 ` Brian Norris
2018-12-21 0:29 ` egranata
2018-12-21 7:24 ` Lee Jones
2018-12-21 21:44 ` [PATCH v2] " egranata
2019-01-14 23:49 ` [PATCH] " Gwendal Grignou
2019-01-15 2:03 ` Brian Norris
2019-01-15 5:42 ` Gwendal Grignou
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=20181203110810.GI26661@dell \
--to=lee.jones@linaro.org \
--cc=bleung@chromium.org \
--cc=briannorris@google.com \
--cc=egranata@chromium.org \
--cc=egranata@google.com \
--cc=gwendal@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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.