Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp1315345rwi; Thu, 20 Oct 2022 11:00:08 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4gI8y8cXeNaZrQYVxV6m10c24gMAVfPcsnsBLLdUMffLMfQVrZvHuE+fzcQL83pndJYm5a X-Received: by 2002:a05:6402:27d4:b0:45d:a69e:336d with SMTP id c20-20020a05640227d400b0045da69e336dmr13318971ede.298.1666288808035; Thu, 20 Oct 2022 11:00:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666288808; cv=none; d=google.com; s=arc-20160816; b=gV8tT5OCty0GsBADbpdDfetXS9pLZ4rla3ER6pgpRZoZFnJXdHaT3US7RuDIeHjjni DHLv2cXaK6/Sl6qWeaRyv5/oyXxWdKEy2IpE+mZ5HLlH38dSZ4UtzoFdaxpNgF9E/CV4 EuiQ82Kx6RoQWIlMV/q8zDTG5vt9IdwbzwW2e2qWmiVnMNgdQoZ4+LsaSIza//clRDlX 8npVArc9jVVVduJp8aHt6kZX82UpX0YP/eRXzLG664uLGaEmgPrrGWatCJPrYgPeTk2y iHOkPdCU8tbxRBK05IEDRXJxijnLTplO9Oqz72djsei2hWoCq4MAos8zoIUS+Aj15mWP preQ== 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:to:from :subject:message-id; bh=WE47+xdURLoqiRKOJNn4zM0Wf4H2leMqbZgRrTXyYCE=; b=SSon4p6drx2uX6hxantzA8LLF4UIF3ZDeZREyYIqjJ2sTbkc4AFaiiADcawUOlSPl4 0hKpjhK7BnNbeUSreIQ/n0oQIOoDWEf82/q4E+L8ktVRa+7d2JacHPVKWzlRbaqWTTLx tvDRN4j6gC0aJ6mmAMhse8J7jBxp9xw62eLkMVpisJ9Fq2wdVVt7OuxCAbzZV5Wl2sGU t1tjxtdlRQYao3lo0gnvEZcj1rqtuR+70RHQlV283atuWPM2LsloN8XvuAEb6U9Cir8u f6ghgT+2nKFVocEUKKZLEiUjuOf1VtyFEg6WFLcPfKWU3nTZt2S65NP37dRLQIy3kMf+ Nfqg== 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 k25-20020a17090632d900b007891fd91786si14285512ejk.151.2022.10.20.10.59.42; Thu, 20 Oct 2022 11:00:08 -0700 (PDT) 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 S229920AbiJTRd7 convert rfc822-to-8bit (ORCPT + 99 others); Thu, 20 Oct 2022 13:33:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41150 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229765AbiJTRd4 (ORCPT ); Thu, 20 Oct 2022 13:33:56 -0400 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 CEA981DB261; Thu, 20 Oct 2022 10:33:55 -0700 (PDT) Received: (Authenticated sender: hadess@hadess.net) by mail.gandi.net (Postfix) with ESMTPSA id 993AB20002; Thu, 20 Oct 2022 17:33:53 +0000 (UTC) Message-ID: Subject: Re: [PATCH] Add rumble support to latest xbox controllers From: Bastien Nocera To: Siarhei Vishniakou , Jiri Kosina , Benjamin Tissoires , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org Date: Thu, 20 Oct 2022 19:33:53 +0200 In-Reply-To: <20221020161401.941927-1-svv@google.com> References: <20221020161401.941927-1-svv@google.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT User-Agent: Evolution 3.46.0 (3.46.0-2.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,URIBL_BLOCKED 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 Thu, 2022-10-20 at 09:14 -0700, Siarhei Vishniakou wrote: > Currently, rumble is only supported via bluetooth on a single xbox > controller, called 'model 1708'. On the back of the device, it's > named > 'wireless controller for xbox one'. However, in 2021, Microsoft > released > a firmware update for this controller. As part of this update, the > HID > descriptor of the device changed. The product ID was also changed > from > 0x02fd to 0x0b20. On this controller, rumble was supported via > hid-microsoft, which matched against the old product id (0x02fd). As > a > result, the firmware update broke rumble support on this controller. > > The hid-microsoft driver actually supports rumble on the new > firmware, > as well. So simply adding new product id is sufficient to bring back > this support. > > After discussing further with the xbox team, it was pointed out that > other xbox controllers, such as xbox elite, should also be possible > to > support in a similar way. However, I could only verify this on 2 > controllers so far. > > In this patch, add rumble support for the following 2 controllers: > 1. 'wireless controller for xbox one', model 1708, after applying the >    most recent firmware update as of 2022-10-20. > 2. 'xbox wireless controller', model 1914. This is also sometimes >    referred to as 'xbox series S|X'. This is a good summary of the different models: https://en.wikipedia.org/wiki/Xbox_Wireless_Controller#Summary You can remove the mention of the other names it might have, or the names at the back of the joypad, and use the model numbers instead. I think I have a model of each one of the devices in the list (except 1797 and 1537 IIRC), so I could test this if needed. Do you have a good test case for the various forces of rumble that would exercise both motors?