Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp4635471ybl; Mon, 13 Jan 2020 17:32:54 -0800 (PST) X-Google-Smtp-Source: APXvYqyN4QQjmVVY0iKOGITuY9S0NOsrDoPm1hlVyuptG5m+Aafm5sPYkNwTdTqrWzXNFgIBlOuB X-Received: by 2002:aca:c38c:: with SMTP id t134mr14260419oif.175.1578965574289; Mon, 13 Jan 2020 17:32:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578965574; cv=none; d=google.com; s=arc-20160816; b=heOLp/84ylGrvQ+IbdTS3yUtc8PTXuolNutR15NZiH8pGxPvERI2EULKfcMpJojDFv UA6AiOEMR0jwu2V+w9nPUpgycuuvJUl6qwp67EB3r1G9xvzruesWebhSnWjSiubqU1uj kpAS37qfeTmHCGPCFkK7hRvu3e7ACagnl99G7chYhfNaNHPLkfEa2PZQ1gWCVdmVnpUL 7mjaJTDcgR/JrCGkNdWZzb5ohMzc+DgHwOxykUy3FSvLYKmBkaBqevs5YZ9ac0DHHHCB AtzHu+BjEZambauaRaza8RUa+hsOAq+sJ0URNYW7BeDqVWcEmL+b4aLkManbjhN3lZNd +wDg== 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=pcPgHMjbM1tTuJs57rpRm00UDVEplEHbWgFk0hTeOZ4=; b=C0rLCim25YJKkD6ICH9DgtS8J5auDCGxoT3B909v3GnLmuMz+9H3Psc1smaHs10g+6 xB7PX9IGQNYXiJDQCwzwS3nz4+KdpzPncc2zSvByZMtV04vLlvdTCdUYVMuESf+TSNvp 8SJG+j9mJ2jmrXGPWKZOHy0aVcVqabBGtqLP8dqLHSmlfQ4+qdboPjqtZhsasVD2P9cC tP69PjpIoQBGOY2J81sKBkVtvahDYaDG2QJpX2F+GUs5P9eLWScAyhym0rln42XptEdM DHpQDuzJdMVkkapr/IIVVnSTyUSUGf4CgqsflgfjPkKuv+fylF59vMTzhMfUzyEXyZN7 xsoQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hV5nmls0; 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 x24si7966851oto.255.2020.01.13.17.32.42; Mon, 13 Jan 2020 17:32:54 -0800 (PST) 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=hV5nmls0; 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 S1729290AbgANBGL (ORCPT + 99 others); Mon, 13 Jan 2020 20:06:11 -0500 Received: from us-smtp-2.mimecast.com ([207.211.31.81]:24388 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729153AbgANBGL (ORCPT ); Mon, 13 Jan 2020 20:06:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1578963970; 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=pcPgHMjbM1tTuJs57rpRm00UDVEplEHbWgFk0hTeOZ4=; b=hV5nmls0y+UjjLdXrdHioATIafPa74aOEh3qZHQJvgy5NC7qEDePpvhwg5hdNV3a2liUXr NmAh3TeJFoNw8tYD7ZNmETxkud3jxtY1S+9MR/TiJo4DuibrIH4CynbsIr0Ja+UMrWz5fn hfhrY0AeLkUhtu80W49bSBmGLgjeamI= Received: from mail-qv1-f72.google.com (mail-qv1-f72.google.com [209.85.219.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-101-2wdm5lbuMTuscRUgDvVePA-1; Mon, 13 Jan 2020 20:06:08 -0500 X-MC-Unique: 2wdm5lbuMTuscRUgDvVePA-1 Received: by mail-qv1-f72.google.com with SMTP id f16so7657661qvr.7 for ; Mon, 13 Jan 2020 17:06:08 -0800 (PST) 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:content-transfer-encoding; bh=pcPgHMjbM1tTuJs57rpRm00UDVEplEHbWgFk0hTeOZ4=; b=pcOdjthsEFnAx3Gxmwy0vvFfdufqUJ/GQWkWVy4bDCuwHGj6dMVHLMxE6BRBvsbes2 3ZCU6OInKgh+TRBx1J7RfUISqFqLX1Q76VhMTGktZslvWfDon6v9moN0t1gkDAubO7ip YQ1mxKZletdlZoZWx/IznCO+DXx++3L4+AcYN6VuotYEla17gfi7CaMjjVRm6x9GfqZS EUOxuvsLHKlDfL8BGzt4eYnK3/bbrjVXttkvXUVAbijz5/9SPDs1lbLq78g9kY/FB4CE +QSFKJkpo/GEvYWhQNHt28Liu6nJ1n/mPHXA+xCv3EUh1J/ezXIvSHXE5STKoYa42UnR sRow== X-Gm-Message-State: APjAAAXuDSG27/sQzayeZHVdfkcwuvVTptoDpxFo2L4tDCzOpJMYP9ml phy6fYKqmxdr38E3STpMXw+vhQR4/GrOX0DROer8L46FwLfUxlPfLQv4KwsyRJzVZ8H+EjGhZXU jKtYhcDmUkdBMx+dZCpU9Re7l0MvPr/Mbjfub3dmZ X-Received: by 2002:a37:a086:: with SMTP id j128mr14135968qke.459.1578963968132; Mon, 13 Jan 2020 17:06:08 -0800 (PST) X-Received: by 2002:a37:a086:: with SMTP id j128mr14135942qke.459.1578963967884; Mon, 13 Jan 2020 17:06:07 -0800 (PST) MIME-Version: 1.0 References: <20200112220612.3448741-1-lains@archlinux.org> In-Reply-To: <20200112220612.3448741-1-lains@archlinux.org> From: Benjamin Tissoires Date: Tue, 14 Jan 2020 21:03:30 +1000 Message-ID: Subject: Re: [PATCH v2] HID: logitech-hidpp: add support for the Powerplay mat/receiver To: =?UTF-8?Q?Filipe_La=C3=ADns?= Cc: Jiri Kosina , "open list:HID CORE LAYER" , lkml 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 Hi Filipe, On Mon, Jan 13, 2020 at 8:07 AM Filipe La=C3=ADns wro= te: > > The Logitech G Powerplay has a lightspeed receiver with a static HID++ > device with ID 7 attached to it to. It is used to configure the led on > the mat. For this reason I increased the max number of devices. > > I also marked all lightspeed devices as HID++ compatible. As the > internal powerplay device does not have REPORT_TYPE_KEYBOARD or > REPORT_TYPE_MOUSE it was not being marked as HID++ compatible in > logi_hidpp_dev_conn_notif_equad. > > Signed-off-by: Filipe La=C3=ADns > --- > drivers/hid/hid-logitech-dj.c | 10 +++++++--- > 1 file changed, 7 insertions(+), 3 deletions(-) > > diff --git a/drivers/hid/hid-logitech-dj.c b/drivers/hid/hid-logitech-dj.= c > index bb50d6e7745b..732380b55b15 100644 > --- a/drivers/hid/hid-logitech-dj.c > +++ b/drivers/hid/hid-logitech-dj.c > @@ -16,11 +16,11 @@ > #include > #include "hid-ids.h" > > -#define DJ_MAX_PAIRED_DEVICES 6 > +#define DJ_MAX_PAIRED_DEVICES 7 > #define DJ_MAX_NUMBER_NOTIFS 8 > #define DJ_RECEIVER_INDEX 0 > #define DJ_DEVICE_INDEX_MIN 1 > -#define DJ_DEVICE_INDEX_MAX 6 > +#define DJ_DEVICE_INDEX_MAX 7 > > #define DJREPORT_SHORT_LENGTH 15 > #define DJREPORT_LONG_LENGTH 32 > @@ -971,7 +971,7 @@ static void logi_hidpp_recv_queue_notif(struct hid_de= vice *hdev, > case 0x0c: > device_type =3D "eQUAD Lightspeed 1"; > logi_hidpp_dev_conn_notif_equad(hdev, hidpp_report, &work= item); > - workitem.reports_supported |=3D STD_KEYBOARD; > + workitem.reports_supported |=3D STD_KEYBOARD | HIDPP; This feels wrong. The whole initial code was hack-ish, and now this is even more hack-ish. I don't have a simple solution right now (at a conference this week), but I will need to be convinced this is the only sane solution :/ Cheers, Benjamin > break; > case 0x0d: > device_type =3D "eQUAD Lightspeed 1_1"; > @@ -1850,6 +1850,10 @@ static const struct hid_device_id logi_dj_receiver= s[] =3D { > HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, > USB_DEVICE_ID_LOGITECH_NANO_RECEIVER_LIGHTSPEED_1_1), > .driver_data =3D recvr_type_gaming_hidpp}, > + { /* Logitech powerplay mat/receiver (0xc539) */ > + HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, > + 0xc53a), > + .driver_data =3D recvr_type_gaming_hidpp}, > { /* Logitech 27 MHz HID++ 1.0 receiver (0xc513) */ > HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_MX3000_REC= EIVER), > .driver_data =3D recvr_type_27mhz}, > -- > 2.24.1 >