public inbox for linux-input@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Tomeu Vizoso <tomeu.vizoso@collabora.com>,
	Vic Yang <victoryang@google.com>, Olof Johansson <olof@lixom.net>,
	Gwendal Grignou <gwendal@chromium.org>,
	Brian Norris <briannorris@chromium.org>
Subject: Re: [PATCH 0/2] mfd: cros_ec_keyb: MKBP event support
Date: Mon, 8 Aug 2016 12:30:18 +0100	[thread overview]
Message-ID: <20160808113018.GK5243@dell> (raw)
In-Reply-To: <1467364076-20172-1-git-send-email-enric.balletbo@collabora.com>

On Fri, 01 Jul 2016, Enric Balletbo i Serra wrote:
> Hi,
> 
> The cros-ec MKBP event support will be used on different EC drivers like EC
> keyboard, EC USB PD and EC sensors drivers. The first attempt to merge these two
> patches was within the EC USB PD series [1] sent by Tomeu Vizoso, but these
> series are blocked possibly until we figure out how this maps into the proposed
> type-c infraestructure.
> 
> As these patches ([2] and [3]) were a dependency for other possible patch
> series and have sense send it alone, makes no sense wait for the upstreaming of
> the full EC USB PD series, so I created a new patch series with only these two
> patches and rid of the USB PD stuff.
> 
> Note that the following patch series apply cleanly on top of mainline plus the
> patches to add support for ChromeOS EC PWM by Brian Norris [4] to avoid
> conflicts and because I think are close to be accepted.
> 
> Also note that the two patches need to be taken together, massively reducing the
> chances of a fail.  The chances that a) a bisect will fall exactly between the
> 2 patches and then b) the drivers try to handle the same interrupt at the same
> time are significantly small enough for us to take that risk.
> 
> The patches were tested by myself on a Veyron Jerry checking that after some
> suspend/resumes cycles the keyboard is working.
> 
> Changes:
>  * Add the SoB Vic Yang
>  * Rebased on top of mainline + cros_ec pwm patches, resolved the conflicts.
> 
> [1] https://lwn.net/Articles/679228/
> [2] https://patchwork.kernel.org/patch/8809921/
> [3] https://patchwork.kernel.org/patch/8809931/
> [4] https://lwn.net/Articles/691861/
> 
> Vic Yang (2):
>   mfd: cros_ec: Add MKBP event support
>   Input: cros_ec_keyb - Stop handling interrupts directly
> 
>  drivers/input/keyboard/cros_ec_keyb.c   | 135 ++++++++------------------------
>  drivers/mfd/cros_ec.c                   |  58 +++++++++++++-
>  drivers/platform/chrome/cros_ec_proto.c |  92 ++++++++++++++++++++++
>  include/linux/mfd/cros_ec.h             |  18 +++++
>  include/linux/mfd/cros_ec_commands.h    |  34 ++++++++
>  5 files changed, 230 insertions(+), 107 deletions(-)

Set does not apply on v4.8-rc1.

Please rebase and resend with all the collected Acks applied.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      parent reply	other threads:[~2016-08-08 11:28 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: MKBP event support 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
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 ` Lee Jones [this message]

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=20160808113018.GK5243@dell \
    --to=lee.jones@linaro.org \
    --cc=briannorris@chromium.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=enric.balletbo@collabora.com \
    --cc=gwendal@chromium.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=tomeu.vizoso@collabora.com \
    --cc=victoryang@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