Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp1023198ybp; Fri, 11 Oct 2019 07:56:58 -0700 (PDT) X-Google-Smtp-Source: APXvYqyxtTR6UR5Mv9jPk2rwaZAwNPgeghH2crS/tWKFbfnkqWzAE1q4ULXbdzeIF48WcxX25yqX X-Received: by 2002:a05:6402:698:: with SMTP id f24mr14124960edy.172.1570805818842; Fri, 11 Oct 2019 07:56:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570805818; cv=none; d=google.com; s=arc-20160816; b=LYAYNFDZRVGOUoQGYNinSPknAio3eNzDfBy0rPyTVl8MR5Odw97zPzyFUOArlgu0c6 966q0keWJItaZifd/iwRPJSzbeK2r+iEzUSDrZv0g8O6LyUwnOldIqhjz+O1AmhN2+k3 azXwZ+LvvOQNSCwMpji0ZQuLz9EJZ7+gVo5EoQ17oZcZo7bS4CYI4ZNaBjh+VzNiamJA 2iv5o0AtG56g6V92dIwhwk35SdmeEjR8XrWJicS0BdhbYeMCjvncUy6y9CtONrtSgxLS QbRF0jgr77FPYp1Sy1WKK1gtasg0MQ1gSXLCPWtZHNCAMpW+2IUJIxkBsNW0kgUW3ob5 psgA== 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:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=FiDA3QBts5KfCGtUBop3Hw/Oo24dQFtETwEmLErKTH4=; b=qJdH6VMq/lHCBgjv+aSgrlLThdF2hWJp3Iwpy6/Cx/WSaWfRQ9IjPKDjs4vrG/bupV PrnPSGAjXw5upMWorG4a2tXPtKfsABBkJYSPgVGI2/e0ZW2GQFoeH01wAva8YozcTNrb +r0pJdEoI0ClWkHP4/ji8KocFKptkilVXCFnG5pnOVOtWUr4bmarPIK7ieqqj/bCfvEP 99NLbgEPbvos17DrKouuskhhLdp/ebRX/BHLiOy/+bDwK4gTfZgb5wAC0bCiJFlQPIqn Pidl2ML+hiQ5Ic5RmVAjjntflX6aRIqu8NF7CjS4b+2N1HRHqJMYjTSDBBuZ2PG0LGic cbow== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=YfC5aK6C; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g37si6198655edg.59.2019.10.11.07.56.35; Fri, 11 Oct 2019 07:56:58 -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=pass header.i=@redhat.com header.s=mimecast20190719 header.b=YfC5aK6C; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726714AbfJKO4J (ORCPT + 99 others); Fri, 11 Oct 2019 10:56:09 -0400 Received: from us-smtp-1.mimecast.com ([207.211.31.81]:55755 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726328AbfJKO4J (ORCPT ); Fri, 11 Oct 2019 10:56:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1570805768; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=FiDA3QBts5KfCGtUBop3Hw/Oo24dQFtETwEmLErKTH4=; b=YfC5aK6CiBxTYyITNFO4dL5sxQtW3PhXrLjMjARigFj/vH6RI/XmuunmeI14ZzSpygxMqa oT+A/60RPJtaAC7CCCkcpsXIMh0ZQNjOQ6hltpRxgKws7G5U40HaH+SKk9qeTBcYgKseAT +gAenYXisfqK8xjojvjV4Gj8XAIvIZo= Received: from mail-qt1-f199.google.com (mail-qt1-f199.google.com [209.85.160.199]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-327-zODSv_bAPUaIlkvihGjNsw-1; Fri, 11 Oct 2019 10:56:03 -0400 Received: by mail-qt1-f199.google.com with SMTP id r19so9654132qtk.15 for ; Fri, 11 Oct 2019 07:56:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JATZHH1NgtP8u5fFJewNDLUv2TCv4ss7bPRKEHICbr0=; b=hz6/C/D//XWVqc0UXzu/Gl5eyhQRwPFntuaR9ks7eEMlGqLWS8hlDGiZMSjx8YmfDx hIZy3HuOAqZbx8JiMl4XBp/zYbxcsNPA5FMfBwS1wWItW1Sa7RAtGDakVn+HXJVIzhq3 nAiBoHwIC2LKdt4XmEUxTPKca49afHD4DeIhXHJw4qDrE2o2j7juVQ2OGLXtD/qUfk0k BrVlTP7zpwCcCfnKrteE7NolZSwkdRwSWAvTcVcmmEJthgYz+6qremjSQjng7OujAIf3 +94SKsu57patGCSf8gi4q80ElU7Kx6k9kdnu1vyk0/OZiJg0ts1aegspbMKBJ5kEGOl4 iXMw== X-Gm-Message-State: APjAAAXr0li4NcoF5kTxJ9DeGd++D6/YqK9TS0jk8zGLHxfIWaf95S4r /DA37R1tS1ZVCxwKQIN8LCTJ++mg+w/iWN1YzUDXCvnlP8KX04cH7F+KpHOn8PRRzZPsHPy1+KW OdwAd8HldToWUqCmK56ZViCvwWGOCmYN6NtUkpqYE X-Received: by 2002:ae9:f306:: with SMTP id p6mr16089656qkg.169.1570805763042; Fri, 11 Oct 2019 07:56:03 -0700 (PDT) X-Received: by 2002:ae9:f306:: with SMTP id p6mr16089632qkg.169.1570805762825; Fri, 11 Oct 2019 07:56:02 -0700 (PDT) MIME-Version: 1.0 References: <20191007051240.4410-1-andrew.smirnov@gmail.com> <20191007051240.4410-4-andrew.smirnov@gmail.com> In-Reply-To: <20191007051240.4410-4-andrew.smirnov@gmail.com> From: Benjamin Tissoires Date: Fri, 11 Oct 2019 16:55:51 +0200 Message-ID: Subject: Re: [PATCH 3/3] HID: logitech-hidpp: add G920 device validation quirk To: Andrey Smirnov Cc: "open list:HID CORE LAYER" , Sam Bazely , Jiri Kosina , Henrik Rydberg , "Pierre-Loup A . Griffais" , Austin Palmer , lkml , "3.8+" X-MC-Unique: zODSv_bAPUaIlkvihGjNsw-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 7, 2019 at 7:13 AM Andrey Smirnov wr= ote: > > G920 device only advertises REPORT_ID_HIDPP_LONG and > REPORT_ID_HIDPP_VERY_LONG in its HID report descriptor, so querying > for REPORT_ID_HIDPP_SHORT with optional=3Dfalse will always fail and > prevent G920 to be recognized as a valid HID++ device. > > Modify hidpp_validate_device() to check only REPORT_ID_HIDPP_LONG with > optional=3Dfalse on G920 to fix this. > > Fixes: fe3ee1ec007b ("HID: logitech-hidpp: allow non HID++ devices to be = handled by this module") > Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=3D204191 > Reported-by: Sam Bazely > Signed-off-by: Andrey Smirnov > Cc: Jiri Kosina > Cc: Benjamin Tissoires > Cc: Henrik Rydberg > Cc: Sam Bazely > Cc: Pierre-Loup A. Griffais > Cc: Austin Palmer > Cc: linux-input@vger.kernel.org > Cc: linux-kernel@vger.kernel.org > Cc: stable@vger.kernel.org > --- > drivers/hid/hid-logitech-hidpp.c | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/hid/hid-logitech-= hidpp.c > index cadf36d6c6f3..f415bf398e17 100644 > --- a/drivers/hid/hid-logitech-hidpp.c > +++ b/drivers/hid/hid-logitech-hidpp.c > @@ -3511,6 +3511,12 @@ static bool hidpp_validate_report(struct hid_devic= e *hdev, int id, > > static bool hidpp_validate_device(struct hid_device *hdev) > { > + struct hidpp_device *hidpp =3D hid_get_drvdata(hdev); > + > + if (hidpp->quirks & HIDPP_QUIRK_CLASS_G920) > + return hidpp_validate_report(hdev, REPORT_ID_HIDPP_LONG, > + HIDPP_REPORT_SHORT_LENGTH, f= alse); > + with https://patchwork.kernel.org/patch/11184749/ we also have a need for such a trick for BLE mice. I wonder if we should not have a more common way of validating the devices This can probably be handled later, as your patch fixes the current devices= . Cheers, Benjamin > return hidpp_validate_report(hdev, REPORT_ID_HIDPP_SHORT, > HIDPP_REPORT_SHORT_LENGTH, false) && > hidpp_validate_report(hdev, REPORT_ID_HIDPP_LONG, > -- > 2.21.0 >