From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S933071AbcETJue (ORCPT <rfc822;w@1wt.eu>);
	Fri, 20 May 2016 05:50:34 -0400
Received: from relay4-d.mail.gandi.net ([217.70.183.196]:51641 "EHLO
	relay4-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S932816AbcETJud (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 20 May 2016 05:50:33 -0400
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up
	entirely of whitespace (char 09 hex): References:
	...in.tissoires@redhat.com>\n\t\n <1463507131.3[...]
X-Originating-IP: 83.155.44.161
Message-ID: <1463737826.3440.40.camel@hadess.net>
Subject: Re: [PATCH v2 0/6] Input: soc_button_array fixes and support of the
 Surface 3
From: Bastien Nocera <hadess@hadess.net>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org,
        linux-kernel@vger.kernel.org, Lejun Zhu <lejun.zhu@linux.intel.com>,
        Fabio Estevam <festevam@gmail.com>
Date: Fri, 20 May 2016 11:50:26 +0200
In-Reply-To: <20160520075348.GI23234@mail.corp.redhat.com>
References: <1463155554-11747-1-git-send-email-benjamin.tissoires@redhat.com>	
 <1463507131.3440.7.camel@hadess.net>
	 <20160520075348.GI23234@mail.corp.redhat.com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.20.2 (3.20.2-1.fc24) 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, 2016-05-20 at 09:53 +0200, Benjamin Tissoires wrote:
> 
<snip>
> Bastien told me in a different thread that the power button is not
> working only after a reboot from Windows. After a cold start, it
> works
> fine.

Not quite. It worked after a hot reboot from Windows another time.

>  There might be something that needs to be set at the I2C level,
> but I think while we don't know much about the I2C protocol there, it
> should be safe to still get this upstream.

I don't know what the problem could be, but it seems safe enough for
now.

Cheers