Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755522AbcCXOaa (ORCPT ); Thu, 24 Mar 2016 10:30:30 -0400 Received: from mx2.suse.de ([195.135.220.15]:43135 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750818AbcCXOaW (ORCPT ); Thu, 24 Mar 2016 10:30:22 -0400 Date: Thu, 24 Mar 2016 15:30:20 +0100 (CET) From: Jiri Kosina X-X-Sender: jkosina@pobox.suse.cz To: =?UTF-8?q?Cl=C3=A9ment=20Vuchener?= cc: Benjamin Tissoires , linux-kernel@vger.kernel.org, linux-input@vger.kernel.org Subject: Re: [PATCH 0/2] hid: corsair: Driver simplification and new supported device In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 903 Lines: 22 On Wed, 23 Mar 2016, =?UTF-8?q?Cl=C3=A9ment=20Vuchener?= wrote: > So, I decided to move all USB related features in user-space (as far as > I know, I was the only user, but if someone is looking for a > replacement, I wrote a small tool available here: > https://github.com/cvuchener/corsair-usb-config). This simplification > only leaves the usage code remapping part and the driver no longer > depends on USB and LED subsystems. This should make the driver easier to > maintain or to add new supported devices. While you are performing this move, is there anything that's actually preventing you from doing the remapping from userspace as well? HID subsystem has for long time been providing the setkeycode() hook for remapping usages, and udev (well, more precisely, that s*****d thing) is actually shipping a lot of hw-specific remap data these days. Thanks, -- Jiri Kosina SUSE Labs