Received: by 10.223.164.202 with SMTP id h10csp788779wrb; Thu, 9 Nov 2017 14:33:19 -0800 (PST) X-Google-Smtp-Source: ABhQp+QKULgiA7NXrFzfzyy6GtXoydHhJEMM1qkhb1KKbEICXv1GCS9w1xdBb+HcQe3YfTTXcWm9 X-Received: by 10.99.109.193 with SMTP id i184mr1338410pgc.187.1510266799484; Thu, 09 Nov 2017 14:33:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1510266799; cv=none; d=google.com; s=arc-20160816; b=X5ePVTL8Na0Rey310ASu4YboVBpNgVRL7gpdmDvrkovmEZ+AUzcR/p2rCy6bJgnC0D ELK0CzVOeQyi9wMS0mbpQC5uswm4yuQrSeOw7fWVynEO6uvlyZiNjqreAYme1KpvQQlO jxkm8Q/YZKUXhITLlB5k8Es5SyTDYLgzgRkq8G4I9aKHAcj6dmrfPEaySnITafudSZks 9iQsHBCObcYhc9IzgdA0OuWqbi1LI36psDpmGlZb6/omYbbcn6cfXAW0Odnum0prXAFv 8XaQ11ulxby4hZPBVteDt/DfJKJeX8ar86LyuGuQe87Gd4ncRYlB0OS9GFc+u6zlnDAa Cu9w== 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:references:in-reply-to:mime-version :dkim-signature:arc-authentication-results; bh=EHfNp3uKBimocWAbiVVMnh1NtWbDrlTskE3PfdvxNbQ=; b=YrwZuIy7eNBnLQhIyJysjbluU4eeDwROtOx2eV77ThBYB9u3UK7ehZwWTxvVsO3An3 l6vD5hnCpbHJp/jWHIaX448n80ib74Ra0+45g8YmOFKmVcQ8j9VblHS9HSmiumCc7XyP 0RIF36MN+i4LV8Tv9veBe2s8B+ayCwct8SY9uQHZLlb7gMgDtqblqeDYeBS5XsVtk5fG PnhsqP++LeeFV1AZ3bsJbO8r4yAYvra+f06cUSWcVZB3DFQg2c53OQzWeS2oMw+lN+my R3deCYLMMX6EC09NrzHcF3I2PdpeYkRW1yCcPId2BZoIsgMd7M47v0qoT26lS+c2vMZj +8gg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=C0BpqiFe; 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=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p72si7837010pfa.376.2017.11.09.14.33.07; Thu, 09 Nov 2017 14:33:19 -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=@gmail.com header.s=20161025 header.b=C0BpqiFe; 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=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754516AbdKIWc1 (ORCPT + 83 others); Thu, 9 Nov 2017 17:32:27 -0500 Received: from mail-ua0-f179.google.com ([209.85.217.179]:48997 "EHLO mail-ua0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751225AbdKIWcZ (ORCPT ); Thu, 9 Nov 2017 17:32:25 -0500 Received: by mail-ua0-f179.google.com with SMTP id z4so5558850uaz.5; Thu, 09 Nov 2017 14:32:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=EHfNp3uKBimocWAbiVVMnh1NtWbDrlTskE3PfdvxNbQ=; b=C0BpqiFeSrtyQAK7boRALqk+nGwinq53NyT8B4zXWXNYt9cqwKk+omTkjHbzBBdOEt R5hjhWC0S3AEjTh56t25/kTC1npEzgzaIher68fOGoAOyQ4D5hjWzF8R1ODXJRlOofK9 u3+GnBAbH6ygKXazltVScBlTdT1yAgBLP7Jwqk6jrox1l3wQso6a0gsppGYXRZjpJRa7 yiiq6xVPpDEDLfjCrhYQWUs87VrxxCt+TcMxpyGp0yxNwRGcXzElvevm9NKhRKg1OeKa DvOXDUw7zYWmoqgG7h2jG2umOr9vc9cJb/wzP+LzRJ92/YZOVZkDjVqXKphF2DA7vmn/ xK6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=EHfNp3uKBimocWAbiVVMnh1NtWbDrlTskE3PfdvxNbQ=; b=Na0VW+jWlWRfi+BTFb6bhtelTY2VzKmU6nY1hfGFoCpLfjpCuDBQVwgS07dbkO+FZL RutH5GuHxCN6T7UqrUypOWzD6gredvLId192dfmBRvuPwnHO0R4iXrok88iOtJCO0eRL TBKr6VqOGTQMaquHg+4J5FttfZcZZjx9ij5WjC67kL7eZFbuWDXu/2nNnu5RpBA6Lgbk aEeiVOIOzlpDS/ETcurjaSHhTSC50kpMLBIaMBZj2/fICzJz6JxQzDp0qJDZrc8mcd4n ZL6XVSdXrQiWYC2mZLX2jucEpYFxxQOmi0CKgeTWvtNJemA786lCEJ1UlmvXO+AQdVe9 aGeg== X-Gm-Message-State: AJaThX7yyIv7lvVK1pFXFUS4k7OwOye8206SzwYWxouUo82eA/hlr1pZ 4yDSM5fHDmI8JigyJEd7XRZLY+FXV/OjKQQ+cPs= X-Received: by 10.176.14.21 with SMTP id g21mr1905690uak.69.1510266744269; Thu, 09 Nov 2017 14:32:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.31.55.134 with HTTP; Thu, 9 Nov 2017 14:32:23 -0800 (PST) In-Reply-To: References: <20171103172947.15156-1-benjamin.tissoires@redhat.com> <20171106080503.GB9728@mail.corp.redhat.com> From: Jason Gerecke Date: Thu, 9 Nov 2017 14:32:23 -0800 Message-ID: Subject: Re: [PATCH] HID: Wacom: switch Dell canvas into highres mode To: Jiri Kosina Cc: Benjamin Tissoires , Ping Cheng , Linux Input , 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 On Thu, Nov 9, 2017 at 3:42 AM, Jiri Kosina wrote: > On Mon, 6 Nov 2017, Benjamin Tissoires wrote: > >> > >well, this is not the cleanest way of handling this mode set, but it >> > >is the less intrusive AFAICT. >> > > >> > >I was thinking that we might want to add a new field in struct >> > >wacom_feature, but then it wouldn't make sense to keep the set mode >> > >specifics in _wacom_query_tablet_data(). >> > > >> > >So I am open to any better suggestion, but this one works and the >> > >impact on other HID generic tablets is null. >> > > >> > >> > Hmm. Agreed that this isn't ideal. I'd like to take a look at the >> > descriptor, if you wouldn't mind sharing it. The hardware should be >> > similar to other devices of ours and it might be possible to piggyback >> > on existing code. >> > >> >> Sure, here it comes in the hid-replay format (and with a recording >> of a single dot from the pen): > > Jason, > > any word on the descriptor please, did you have time to analyze it? > > Merge window for 4.15 is almost there, so in case you don't want to miss > it, I'd need your Ack/Nack/Postopne rather quickly. > > Thanks, > > -- > Jiri Kosina > SUSE Labs > I spent some time checking for similar devices and didn't anything with a descriptor quite like it. That said, there's a good chance that we'll see something similar in the future... I'm still not entirely happy with the one-off approach, but I'll but my stamp of approval on it. We can work out a more generic way to detect and configure these dual-resolution devices going forward :) Reviewed-by: Jason Gerecke Jason --- Now instead of four in the eights place / you=E2=80=99ve got three, =E2=80=98Cause you added one / (That is to say, eight) to the two, / But you can=E2=80=99t take seven from three, / So you look at the sixty-fours.... From 1583588657656498031@xxx Thu Nov 09 11:43:50 +0000 2017 X-GM-THRID: 1583066908809269246 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread