From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Ben Gamari <bgamari.foss@gmail.com>
Cc: "David Solda" <dso@cypress.com>,
"Troy Abercrombia" <ta@cypress.com>,
"Kamal Mostafa" <kamal@canonical.com>,
"Ozan Çağlayan" <ozancag@gmail.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
customercare <customercare@cypress.com>,
"mario_limonciello@dell.com" <mario_limonciello@dell.com>
Subject: Re: Why Cypress does not upstream its trackpad driver?
Date: Wed, 7 Nov 2012 23:41:54 -0800 [thread overview]
Message-ID: <20121108074154.GA4037@core.coreip.homeip.net> (raw)
In-Reply-To: <877gpwlpus.fsf@gmail.com>
On Wed, Nov 07, 2012 at 10:45:31PM -0500, Ben Gamari wrote:
> David Solda <dso@cypress.com> writes:
>
> > Dmitry, all,
> >
> > To clarify my comment. Our protocol utilizes 8 bytes which are needed
> > in our driver. In order for the Linux system to accept 8 bytes of
> > data, the Linux psmouse system driver is required to be modified.
> > Without this modification, the driver that you are referring to will
> > not work correctly. The psmouse system driver change that would be
> > required is the item that would be rejected.
> >
> > I appreciate your comments and of course, if the driver could be
> > upstreamed, it would (we already have I2C drivers updstreamed for
> > Chrome systems), but there is a difference here.
> >
> > I will again look into the possibility of what you are requesting,
> > however, the changes are extremely low if not zero that it will be
> > accepted.
> >
> You are speaking to the people who ultimately decide whether your change
> will be accepted or not. Currently there is no way anyone could know
> whether the desired change is acceptable as no patch has been
> submitted.
>
> Send a patch with the (minimal, well-organized) needed changes and the
> matter can be discussed from there. If the changes are sane and well
> justified, then there's little reason why they can't be accepted.
OK, so I looked at the psmouse changes briefly and indeed some of them
will not be accepted, because they are really ... weird. Surely if your
device produces command responses in excess of 6 bytes that is currently
the limit in libps2 module the easiest way would be increasing the
buffer in struct ps2dev.
The rest of psnouse-base changes are OK (and indeed because protocol
types are exported to userspace and thus form ABI new definitions has to
go to the end of the list); the driver itself needs bunch cleanups.
Henrik needs to see it as well.
It looks like you are trying to implement both relative and absolute
modes of operation, but we only want absolute as it provides best
experience.
Please post the patches and we'll go form there.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2012-11-08 7:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 22:47 Why Cypress does not upstream its trackpad driver? Ozan Çağlayan
2012-11-07 18:32 ` Kamal Mostafa
2012-11-07 23:13 ` Troy Abercrombia
2012-11-07 23:27 ` richard -rw- weinberger
2012-11-07 23:30 ` David Solda
2012-11-08 0:00 ` David Daney
2012-11-08 0:15 ` Dmitry Torokhov
2012-11-08 0:26 ` David Solda
2012-11-08 3:45 ` Ben Gamari
2012-11-08 7:41 ` Dmitry Torokhov [this message]
2012-11-08 8:09 ` David Solda
2012-11-08 8:13 ` Ozan Çağlayan
2012-11-08 8:54 ` Dmitry Torokhov
2012-11-09 4:06 ` Robert Hancock
2012-11-12 10:57 ` Cruz Julian Bishop
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=20121108074154.GA4037@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=bgamari.foss@gmail.com \
--cc=customercare@cypress.com \
--cc=dso@cypress.com \
--cc=kamal@canonical.com \
--cc=linux-input@vger.kernel.org \
--cc=mario_limonciello@dell.com \
--cc=ozancag@gmail.com \
--cc=ta@cypress.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;
as well as URLs for NNTP newsgroup(s).