linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Heiny <cheiny@synaptics.com>
To: Daniel Drake <dsd@laptop.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org, pgf@laptop.org, djkurtz@google.com
Subject: Re: [PATCH v2] synaptics: add support for Relative mode
Date: Tue, 8 Nov 2011 12:41:21 -0800	[thread overview]
Message-ID: <4EB993F1.7050905@synaptics.com> (raw)
In-Reply-To: <CAMLZHHSKXvcC6NasLS9wcRfoD3v4KdE486_fRGgEHBKq+PiZRg@mail.gmail.com>

On 11/08/2011 10:36 AM, Daniel Drake wrote:
> On Tue, Nov 8, 2011 at 12:34 AM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com>  wrote:
>>> >>  @@ -968,11 +1030,29 @@ int synaptics_init(struct psmouse *psmouse)
>>> >>                 psmouse->rate = 40;
>>> >>         }
>>> >>
>>> >>  +     err = sysfs_create_file(&psmouse->ps2dev.serio->dev.kobj,
>>> >>  +&psmouse_attr_synaptics_disable_gesture.dattr.attr);
>>> >>  +     if (err) {
>>> >>  +             dev_err(&psmouse->ps2dev.serio->dev,
>>> >>  +                     "Failed to create disable_gesture attribute (%d)", err);
>>> >>  +             goto init_fail;
>>> >>  +     }
>> >
>> >  This attribute does not make sense in absolute mode so we should only
>> >  create it when relative mode is requested.
> I think it could make some sense - to me it seems possible that there
> would be a use case where absolute input is requested but the software
> chooses to let the hardware do the gesture detection. But I don't know
> of such a use case, and it isn't interesting for OLPC, so either way
> is fine with me.

I agree with Daniel's statement.

						Chris

      reply	other threads:[~2011-11-08 20:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 16:44 [PATCH v2] synaptics: add support for Relative mode Daniel Drake
2011-11-08  6:34 ` Dmitry Torokhov
2011-11-08 18:36   ` Daniel Drake
2011-11-08 20:41     ` Christopher Heiny [this message]

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=4EB993F1.7050905@synaptics.com \
    --to=cheiny@synaptics.com \
    --cc=djkurtz@google.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dsd@laptop.org \
    --cc=linux-input@vger.kernel.org \
    --cc=pgf@laptop.org \
    /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).