From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Olof Johansson <olof@lixom.net>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Vic Yang <victoryang@google.com>,
Lee Jones <lee.jones@linaro.org>,
Gwendal Grignou <gwendal@chromium.org>,
Brian Norris <briannorris@chromium.org>,
Randall Spangler <rspangler@chromium.org>,
Vincent Palatin <vpalatin@chromium.org>,
Benson Leung <bleung@chromium.org>
Subject: Re: [PATCH 1/2] mfd: cros_ec: Add MKBP event support
Date: Tue, 05 Jul 2016 14:00:09 -0700 [thread overview]
Message-ID: <86858048-FA33-4AC7-A7DD-3BEF5160CAFB@gmail.com> (raw)
In-Reply-To: <CAOesGMjPaztVQPYEvGdHkQDDJYsw2bLSnaz5R_e5hsHYDZZsvw@mail.gmail.com>
On July 5, 2016 1:55:44 PM PDT, Olof Johansson <olof@lixom.net> wrote:
>On Tue, Jul 5, 2016 at 1:54 PM, Olof Johansson <olof@lixom.net> wrote:
>> On Fri, Jul 1, 2016 at 2:07 AM, Enric Balletbo i Serra
>> <enric.balletbo@collabora.com> wrote:
>>> From: Vic Yang <victoryang@google.com>
>>>
>>> Newer revisions of the ChromeOS EC add more events besides the
>keyboard
>>> ones. So handle interrupts in the MFD driver and let consumers
>register
>>> for notifications for the events they might care.
>>>
>>> To keep backward compatibility, if the EC doesn't support MKBP
>event, we
>>> fall back to the old MKBP key matrix host command.
>>>
>>> Signed-off-by: Vic Yang <victoryang@google.com>
>>> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
>>> Tested-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
>>> Cc: Randall Spangler <rspangler@chromium.org>
>>> Cc: Vincent Palatin <vpalatin@chromium.org>
>>> Cc: Benson Leung <bleung@chromium.org>
>>
>> Probably easiest to merge this through the MFD tree due to the
>> overlaps, so for that purpose:
>>
>> Acked-by: Olof Johansson <olof@lixom.net>
>
>Argh, I just noticed that the second patch is an input patch, not
>another MFD patch. Either way, I'm OK with this going through the
>input tree if that's easiest. If so, you should probably wait for an
>ack from Lee as well.
Hmm, I thought I already acked input portion to go through MFD tree... or am I confusing this with some other patch?
Thanks.
--
Dmitry
next prev parent reply other threads:[~2016-07-05 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 9:07 [PATCH 0/2] mfd: cros_ec_keyb: " Enric Balletbo i Serra
2016-07-01 9:07 ` [PATCH 1/2] mfd: cros_ec: Add " Enric Balletbo i Serra
2016-07-05 20:54 ` Olof Johansson
2016-07-05 20:55 ` Olof Johansson
2016-07-05 21:00 ` Dmitry Torokhov [this message]
2016-07-05 21:04 ` Olof Johansson
2016-07-11 16:37 ` Lee Jones
2016-07-11 16:39 ` Lee Jones
2016-07-01 9:07 ` [PATCH 2/2] Input: cros_ec_keyb - Stop handling interrupts directly Enric Balletbo i Serra
2016-08-08 11:30 ` [PATCH 0/2] mfd: cros_ec_keyb: MKBP event support Lee Jones
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=86858048-FA33-4AC7-A7DD-3BEF5160CAFB@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=bleung@chromium.org \
--cc=briannorris@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=gwendal@chromium.org \
--cc=lee.jones@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rspangler@chromium.org \
--cc=tomeu.vizoso@collabora.com \
--cc=victoryang@google.com \
--cc=vpalatin@chromium.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
all inboxes | Powered by JetHome®