public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@stericsson.com>
To: Greg KH <greg@kroah.com>
Cc: Naveen Kumar GADDIPATI <naveen.gaddipati@stericsson.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	STEricsson_nomadik_linux <STEricsson_nomadik_linux@list.st.com>,
	<linux-input@vger.kernel.org>
Subject: Re: [PATCHv1] staging: Synaptics RMI4 touchpad driver support
Date: Tue, 2 Nov 2010 15:14:48 +0100	[thread overview]
Message-ID: <4CD01CD8.3090206@stericsson.com> (raw)
In-Reply-To: <20101102140337.GC9387@kroah.com>

Greg KH wrote:

>> +Wait for the official upstream synaptics rmi4 clearpad drivers as promised over the past few months
>> +Merge any device support needed from this driver into it
>> +Delete this driver
> 
> Huh?
> 
> Why not just add this driver to the kernel tree instead?  When the
> "promised" driver then eventually shows up (who is promising it?) then
> delete the thing.

Well, Alan (on behalf of Ramesh Agarwal) sent out a very similar
patch (Titled "Synaptics TM1217 Touchscreen Controller driver")
the other day, and OTOMH that was after discussions with Synaptics
where they said they were working on a "real" driver (a rather
complex RMI4 bus driver) and we believe they will fix that sooner
or later.

So, until sooner or later happens we thought we'd keep it in staging.

If you prefer both Alan and we can probably submit our patches for
inclusion in the proper place.

A side effect may be that the Synaptics RMI4 people may have trouble
to merge their driver into input/ since they may be requested to
refactor the existing drivers to use it rather than merging new stuff,
putting some burden on their shoulders.

Yours,
Linus Walleij

  parent reply	other threads:[~2010-11-02 14:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02 12:08 [PATCHv1] staging: Synaptics RMI4 touchpad driver support Naveen Kumar G
2010-11-02 14:03 ` Greg KH
2010-11-02 14:06   ` Alan Cox
2010-11-02 14:22     ` Greg KH
2010-11-02 14:14   ` Linus Walleij [this message]
2010-11-02 15:20     ` Greg KH
2010-11-02 15:40     ` Dmitry Torokhov
2010-11-03 18:10       ` Greg KH
2010-11-03 19:07         ` Dmitry Torokhov
2010-11-03 19:19           ` Greg KH
2010-11-03 21:37             ` Arce, Abraham
2010-11-04  4:14               ` Dmitry Torokhov
2010-11-04  5:36               ` Naveen Kumar GADDIPATI
2010-11-04  5:45                 ` Arce, Abraham
2010-11-04  5:59                   ` Naveen Kumar GADDIPATI
2010-11-04 11:31                   ` Dmitry Torokhov
2010-11-02 16:12   ` Christopher Heiny
2010-11-02 16:29     ` Alan Cox

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=4CD01CD8.3090206@stericsson.com \
    --to=linus.walleij@stericsson.com \
    --cc=STEricsson_nomadik_linux@list.st.com \
    --cc=greg@kroah.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naveen.gaddipati@stericsson.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox