Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3460218yba; Mon, 29 Apr 2019 02:47:12 -0700 (PDT) X-Google-Smtp-Source: APXvYqxGZvOrI3jiTLcV4DKTLa1/PeWxQN9kYrGT05qlNwwHX1fgZPczbRF+S/Xu76FtTWFz67rs X-Received: by 2002:a62:b40b:: with SMTP id h11mr60100797pfn.133.1556531232475; Mon, 29 Apr 2019 02:47:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556531232; cv=none; d=google.com; s=arc-20160816; b=AL29jId52rK+T6NVNGvazABypstGksYhnYT5pH2eQP0qAKPFfCqzqJF1JTlp2+roZh KWslOAMJ1z0SKzR93D9O62Dbv2S0zXdlfRUY02+bmIO0XuUQpfmZqYIjJsanZ9e/E3OM errKsOiLRCL4rczNLlCJv/0MUIaEAq3+FzQspXMkKi4cg6y+WVH7jpAQyGsW+2TiIf6g FihGvpaOTum5mq5o9gWBfJmUi6TO5HY8kzBlDTCv4FmRJsl318Rzp1wKrsi6F/9GcjaC +sX61rQdIq9yduFCBy3tTphvh2YXO3lgGof4YvDQ6w1Nno/2HhqS7TuZH2+Xiw08YkHb d27w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:date:cc:to:from:subject :message-id; bh=4BrbaB7prChdzXFUV1mTMjuRFPQyfPkWH7GLH950OBI=; b=qWPMsFgFih0YEfEi0D2LnxRvlNBdllgdXhndiGHPKpnTQh8IgygeCLt/Dz7p6jAdGA ovEpa1Ju5VwUU/BXp97IuiMMbtckn2c6V3/dmTAoYOBqrjLPlqIYsje71LaPFkSxlqSW 9QLrFZpTfpFQqJKGg8JcYP5IyLHlmJRlKYCZpo1yldJHb20FoOaA0MeMbkaSESbLqLJa pkGht6cnLyndgcUdeLh5jPU+Th3cclxIJzFSqXhPySXszNr5M1kIN+fPwawt6ZL7+t2I QB6Ri4ZMSZHzB7rt92J+go5SjFV5KqoNduKYNXuZQYp+gO3Y1GKvxy+B8Y/Y4zpmaU0t QQrA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x4si2045253pgr.41.2019.04.29.02.46.56; Mon, 29 Apr 2019 02:47:12 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727729AbfD2Jpm (ORCPT + 99 others); Mon, 29 Apr 2019 05:45:42 -0400 Received: from mx2.suse.de ([195.135.220.15]:56282 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727239AbfD2Jpm (ORCPT ); Mon, 29 Apr 2019 05:45:42 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 80E2CAD43; Mon, 29 Apr 2019 09:45:40 +0000 (UTC) Message-ID: <1556531138.5647.1.camel@suse.de> Subject: Re: [Bug 203297] Synaptics touchpad TM-3127 functionality broken by PCI runtime power management patch on 4.20.2 From: Jean Delvare To: Benjamin Tissoires , Jarkko Nikula Cc: Bjorn Helgaas , Keijo Vaara , "Rafael J. Wysocki" , Dmitry Torokhov , linux-pm@vger.kernel.org, linux-pci@vger.kernel.org, lkml , linux-input@vger.kernel.org, Wolfram Sang Date: Mon, 29 Apr 2019 11:45:38 +0200 In-Reply-To: References: <20190422130814.GJ173520@google.com> <3a1139ef-10ed-6923-73c5-30fbf0c065c3@linux.intel.com> Organization: Suse Linux Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2019-04-29 at 10:53 +0200, Benjamin Tissoires wrote: > On Mon, Apr 29, 2019 at 10:38 AM Jarkko Nikula > wrote: > > I got another thought about this. I noticed these input drivers need > > SMBus Host Notify, maybe that explain the PM dependency? If that's the > > only dependency then we could prevent the controller suspend if there is > > a client needing host notify mechanism. IMHO that's less hack than the > > patch to rmi_smbus.c. > > So currently, AFAIK, only Synaptics (rmi4) and Elantech are using > SMBus Host Notify. > So this patch would prevent the same bugs for those 2 vendors, which is good. > > It took me some time to understand why this would be less than a hack. > And indeed, given that Host Notify relies on the I2C connection to be > ready for the IRQ, we can not put the controller in suspend like we do > for others where the IRQ controller is still ready. > > So yes, that could work from me. Not sure what Wolfram and Jean would > say though. I would say OK with me, this looks like the cleanest solution to me, so if testing is positive, let's go with it. -- Jean Delvare SUSE L3 Support