Received: by 10.213.65.68 with SMTP id h4csp2799223imn; Mon, 2 Apr 2018 14:20:48 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+VaeAe28D3+EWPmr3M051CcGPxiphlPK5DmzAkz6Qr7ngWT8cmTahlCnZm0EtO8MNvk//X X-Received: by 10.99.114.86 with SMTP id c22mr7160495pgn.72.1522704048785; Mon, 02 Apr 2018 14:20:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522704048; cv=none; d=google.com; s=arc-20160816; b=IxicxHSN7xOq27QXv+7eFi3pfn4hWgd8WdmRP1kO10uZabvAT4QL13ecp/dcLQL4cJ 8r4ufIfNOCcqSYhBvteDpoynoI3rZsuTQFiMtxowiCsAhXtOiekxz1esBZ9o/n7UaBSq D1k1rIAlwN8mUnmG/w01M3VrC5mdQigBEHsVY4K9Dnyr25PJLXfEYa1pNH+uU1JS+H5Y rH2hjYPYUtjNMusNck0Hw+QLJ6HMxBcYmRtR/qqW3nVUuGdg7/EAnUzr1hIjoCkqMBsu J9BtRgD5QaTX1uNfg3WgNXtIJuH55+XIojogLqVrfB8FxtW0nZ7z3v6erUBxvsBF10bE YyxQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-disposition :content-transfer-encoding:mime-version:in-reply-to:references:cc :user-agent:date:subject:to:from:dkim-signature :arc-authentication-results; bh=4QI6KdV2Bxpb8tUft4EQrc+jZUK1nXjzEVbKRhfcO0A=; b=KzaFU9GkWYB3J31WdfEtVyn2rYGvqMTL+9B7q5xR+ZVnWi9Zy8uDpfyoYwDeQtt5Xs jwIcNIhFd5Y7EbOUDJ078fxbkacJFpbGZ4J3uNzP0QbkcG67hPGDUzp+l9WHz/QV2qzw YM4bbg6ZVMvCRp3caq2n0zKsBRNhlcBewCOyvogiTUOmuPqd1IXI53NMZBDiU4f9oBDX fFue5xqZ52o1NUcNbLOAjMmt1a+tRiwR6b1Qe1PC0UPOYQqLoeoGsqjz6ilZLB/c2LV6 dZNe+eHnrrrsDrrkbxTNpyQAVRgMZvwSrh4rXx2DdDPmDtg50ELz4JCVXl01w8aQB5dh w30Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=temperror (no key for signature) header.i=@rainbow-software.org header.s=atlsmtp header.b=Z363zHwf; 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 g4si766610pgr.471.2018.04.02.14.20.34; Mon, 02 Apr 2018 14:20:48 -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; dkim=temperror (no key for signature) header.i=@rainbow-software.org header.s=atlsmtp header.b=Z363zHwf; 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 S1754514AbeDBVTH (ORCPT + 99 others); Mon, 2 Apr 2018 17:19:07 -0400 Received: from smtp-1b.atlantis.sk ([80.94.52.26]:60785 "EHLO smtp-1b.atlantis.sk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753397AbeDBVTG (ORCPT ); Mon, 2 Apr 2018 17:19:06 -0400 Received: from [192.168.0.2] (188-167-69-119.dynamic.chello.sk [188.167.69.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp-1b.atlantis.sk (Postfix) with ESMTPSA id 6EB3283491B8; Mon, 2 Apr 2018 23:19:04 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=rainbow-software.org; s=atlsmtp; t=1522703944; bh=JnO7ySoZiKWcMC7ZOVurRyUVdk9hUZGTi1SDVd1dzCQ=; h=From:To:Subject:Date:Cc:References:In-Reply-To; b=Z363zHwfiAl+0p06yh4FQ/D5XL7yNLNX6cgVdwKlDgW63K0qR6zZ0PMDd52GRT6jq kytfcfqlVtCNmzAG5h44Fpc7gncsO7CCNt9DpPuX2Zplff8cDXRgElAkO+cVx2XWpo gzF7h6YfJP/F8zCWYLgbtXaYoXZGMSBa9TEtoxHQ= From: Ondrej Zary To: Dmitry Torokhov Subject: Re: Sony Vaio VGN-CS31S touch sensor buttons breaking touchpad Date: Mon, 2 Apr 2018 23:19:02 +0200 User-Agent: KMail/1.9.10 (enterprise35 0.20100827.1168748) Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org References: <201804012321.56423.linux@rainbow-software.org> <201804022239.59370.linux@rainbow-software.org> <20180402210529.GA62080@dtor-ws> In-Reply-To: <20180402210529.GA62080@dtor-ws> X-KMail-QuotePrefix: > MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201804022319.02256.linux@rainbow-software.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday 02 April 2018 23:05:29 Dmitry Torokhov wrote: > On Mon, Apr 02, 2018 at 10:39:59PM +0200, Ondrej Zary wrote: > > On Sunday 01 April 2018 23:21:55 Ondrej Zary wrote: > > > Hello, > > > I got a Sony Vaio VGN-CS31S laptop with Synaptics touchpad that > > > exhibits weird behavior. It seems to work until I touch the "Touch > > > Sensor Buttons" bar above the keyboard - then the buttons start to act > > > weirdly: click or remain pressed (sometimes it breaks even without > > > touching the bar). > > > > > > It seems to be a known problem with VGN-CS series: > > > https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/ > > >+bug /774877 > > > https://wiki.freegeekvancouver.org/article/Laptop_Troubleshooting > > > (mentions nasty partial workaround: psmouse.resetafter=1) > > > > > > Many models of the VGN-CS series have the Touch Sensor Buttons: > > > ftp://124.40.41.224/PUB/MANUALS/SWT/Z009/Z009690111.PDF > > > > > > From the hardware side (can be found in MBX-196 Quanta GD2 schematic), > > > the touch bar is a separate PS/2 device connected to third PS/2 port of > > > the EC (Embedded Controller) WPC775L. The touchpad is on the 1st PS/2 > > > port, 2nd port is unused. However, the i8042 does not seem to support > > > multiplexing, the firmware probably combines the data internally > > > somehow. > > > > Good news: it supports multiplexing but i8042_nomux is set because of: > > /* > > * Most (all?) VAIOs do not have external PS/2 ports nor > > * they implement active multiplexing properly, and > > * MUX discovery usually messes up keyboard/touchpad. > > */ > > .matches = { > > DMI_MATCH(DMI_SYS_VENDOR, "Sony Corporation"), > > DMI_MATCH(DMI_BOARD_NAME, "VAIO"), > > }, > > in drivers/input/serio/i8042-x86ia64io.h > > (How can this be modified to exclude VGN-CS series?) > > I guess we'd need a whitelist for MUXes, because older VAIOs would > behave really really badly when one tried to probe for active > multiplexing... > > If you enable MUX, does it survive suspend/resume? Yes, suspends and resumes fine. (Suspend takes 20-25 seconds after the HDD stops but it's the same regardless of MUX.) -- Ondrej Zary