LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: Ciprian Ciubotariu <cheepeero@gmx.net>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	Jiri Kosina <jkosina@suse.cz>
Subject: Re: Logitech G-series drivers
Date: Thu, 19 Feb 2015 10:48:27 +0100	[thread overview]
Message-ID: <20150219104827.7f5d4e38@pluto.restena.lu> (raw)
In-Reply-To: <2384594.RyRtmbhCrj@pink>

Hi Ciprian,

Adding linux-input and Jiri (HID maintainer) to CC.

On Sun, 15 Feb 2015 23:17:27 +0200 Ciprian Ciubotariu wrote:
> I would like to submit to your attention for inclusion in the mainline kernel 
> a series of drivers for a set of Logitech keybord devices. I forked the 
> sources under a GPL/GPLv2 license and performed maintenance and stabilization 
> work on them.
> 
> The repository I am working on is at 
> 
>     https://github.com/CMoH/lg4l
> 
> Short description of the modules and files:
> 
>     - hid-g110 - Logitech G110 (tested)
>     - hid-g13 - Logitech G13 (tested)
>     - hid-g15v2 - Logitech G15, version 2 (tested)
>     - hid-g19 - Logitech G19 (tested)
> 
>     - hid-g15 - Logitech G15 (not tested)
>     - hid-g510 - Logitech G510 - not ready
> 
>     - hid-gcore - common functions for other modules
>     - hid-gfb - framebuffer implementation for on-device displays
>     - hid-ids.h - product IDs 
> 
> I would like the opinion of a kernel developer on the possibility of including 
> these drivers in the kernel. If the answer is favorable, I will prepare a 
> series of patches against the kernel's master branch and work towards them 
> being accepted.

>From a quick look at your github tree the drivers are prepared for
building out-of-tree.

Did you check for older work on Logitech keyboards that has been
proposed on linux-input list some time ago and what is currently
present in Linus' tree?

An overview of the features covered by the drivers would help
understand what the new drivers add (and the differences between all
the covered keyboard variants).
There seem to be individual drivers for each keyboard type.
Are the features so different that distinct drivers are needed or can
the drivers be unified?


If you would like to get the drivers merged please create patches
against upstream tree, eventually starting with support for the
keyboard you own, adding support for the other keyboards in separate
patches.
You could also split your patch based on feature support.

It might be worth exploring the option to organize the driver(s) as a
MFD (multi-function-device) device.

Bruno

  reply	other threads:[~2015-02-19  9:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15 21:17 Ciprian Ciubotariu
2015-02-19  9:48 ` Bruno Prémont [this message]
2015-02-21 15:46   ` Ciprian Ciubotariu
2015-02-21 15:50     ` [PATCH] Add drivers for Logitech G110, G13, G15v2 and G19 Ciprian Ciubotariu
2015-02-21 17:21       ` Paul Bolle
2015-02-23 20:47         ` Ciprian Ciubotariu
2015-03-03 21:52           ` Paul Bolle
2015-02-21 21:57     ` Logitech G-series drivers Bruno Prémont
2015-02-24  0:32       ` Ciprian Ciubotariu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150219104827.7f5d4e38@pluto.restena.lu \
    --to=bonbons@linux-vserver.org \
    --cc=cheepeero@gmx.net \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Logitech G-series drivers' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).