Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp564824rwb; Wed, 7 Dec 2022 02:05:52 -0800 (PST) X-Google-Smtp-Source: AA0mqf5iXShFhIcp5L6OQ1q7PcMk4yP3IeYRxqRCio4x+BlW+Ih2H8JBHhl7XfjiCpaHb8b7csjj X-Received: by 2002:a17:902:a5cc:b0:186:de87:7ffd with SMTP id t12-20020a170902a5cc00b00186de877ffdmr85077555plq.94.1670407552272; Wed, 07 Dec 2022 02:05:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670407552; cv=none; d=google.com; s=arc-20160816; b=TnJ7bgskO9rHt+Xdw0BNW4n33GeMgmI+M+azblx/ZIZEY1n0Y4+bCgLtBvmQr5sLjQ JcVQJrwFIRXNIQEvEP2Qyh2efVrdrxaougqPptVVXcmCL6ht7hmolo3qRqvbcMHvdCdt tPDFRuLjtkyLMd3Grw2spWaAzPlpx8OAbE9B/ceikW8w3zQBa3Xds9WCDu1zBS/RCh6f soV04gd5T9jM8PXanrZHbYk3/MRxYM7fsIBqiT/CPOWoI2EahMGcwJpJCAc7NrbS2I8p UPA23hEqI//rwic/T3ewDp9whDJRjag44Am6+QObLVesHsElr0ljIFkzNH7dAM3P+W8r 82Wg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent :content-transfer-encoding:references:in-reply-to:date:cc:to:from :subject:message-id; bh=vg8+M5Rs2Uj0nMB05HIE1MH8Zr08v2gN9YAYLIcvoQg=; b=mxU4Ji4T/XOaOIhwDK161qr4FWyxyh8qw4oG0gZjQpg3C2HzotVcKNHi/l3VGRjRa/ Gy0vHnnOsLlprwjFohtrckNT1xbQnsueLH3Qh1cW56MFWTLxJi2NHNFlFfoa4N+r6w4E ZL2Xv0i/pCUt1SpoI/5z6y5caSRocrltRMO67DXWOpSOfSh4DbbUGhEzOpuJhQriznzU yY6H8D6sa48MIDloMmGfGiYKA93c3o6osASmdWTWdSoT9YqB7DFYtydxMDIjvjzc643x CO1DnL1CqAjtm+AliCzsoUYmp+gRl3Eb648m7/0a6ItIZf4dx78iCPNbfSgYKjYESk9i /UvQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w6-20020a170902a70600b00188b79ec70fsi6794608plq.581.2022.12.07.02.05.42; Wed, 07 Dec 2022 02:05:52 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230112AbiLGJ3h convert rfc822-to-8bit (ORCPT + 77 others); Wed, 7 Dec 2022 04:29:37 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43746 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229988AbiLGJ3b (ORCPT ); Wed, 7 Dec 2022 04:29:31 -0500 Received: from relay7-d.mail.gandi.net (relay7-d.mail.gandi.net [IPv6:2001:4b98:dc4:8::227]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 218C23D93B; Wed, 7 Dec 2022 01:29:21 -0800 (PST) Received: (Authenticated sender: hadess@hadess.net) by mail.gandi.net (Postfix) with ESMTPSA id 99A352000C; Wed, 7 Dec 2022 09:29:16 +0000 (UTC) Message-ID: Subject: Re: [PATCH v1 2/2] HID: logitech-hidpp: Add Bluetooth Mouse M336/M337/M535 to unhandled_hidpp_devices[] From: Bastien Nocera To: "Rafael J. Wysocki" , Jiri Kosina Cc: Filipe =?ISO-8859-1?Q?La=EDns?= , Benjamin Tissoires , linux-input@vger.kernel.org, LKML , "Rafael J. Wysocki" , Thorsten Leemhuis Date: Wed, 07 Dec 2022 10:29:16 +0100 In-Reply-To: <2283816.ElGaqSPkdT@kreacher> References: <2262737.ElGaqSPkdT@kreacher> <5647715.DvuYhMxLoT@kreacher> <2283816.ElGaqSPkdT@kreacher> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT User-Agent: Evolution 3.46.2 (3.46.2-1.fc37) MIME-Version: 1.0 X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2022-12-07 at 10:12 +0100, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Evidently, Logitech Bluetooth Mouse M336/M337/M535 (0xb016) does not > work when HID++ is enabled for it, This needs the output of the hidpp-list-features tool mentioned earlier in the thread so we can avoid words like "evidently" and provide concrete proof. But why is it needed in this case? We purposefully try to avoid blanket blocklists. The lack of HID++ can be probed, so the device should work just as it used to (if the fallback code works). We should only list devices that need special handling, and the ones that don't work once HID++ was probed unsuccessfully. > so add it to the list of devices > that are not handled by logitech-hidpp. > > Fixes: 532223c8ac57 ("HID: logitech-hidpp: Enable HID++ for all the > Logitech Bluetooth devices") > Signed-off-by: Rafael J. Wysocki > --- >  drivers/hid/hid-logitech-hidpp.c |    1 + >  1 file changed, 1 insertion(+) > > Index: linux-pm/drivers/hid/hid-logitech-hidpp.c > =================================================================== > --- linux-pm.orig/drivers/hid/hid-logitech-hidpp.c > +++ linux-pm/drivers/hid/hid-logitech-hidpp.c > @@ -4274,6 +4274,7 @@ static const struct hid_device_id unhand >         { HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_LOGITECH, > USB_DEVICE_ID_LOGITECH_HARMONY_PS3) }, >         /* Handled in hid-generic */ >         { HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_LOGITECH, > USB_DEVICE_ID_LOGITECH_DINOVO_EDGE_KBD) }, > +       { HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_LOGITECH, 0xb016) }, >         {} >  }; >   > > >