From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Cc: Henrik Rydberg <rydberg@euromail.se>,
Nick Dyer <nick.dyer@itdev.co.uk>,
Sjoerd Simons <sjoerd.simons@collabora.co.uk>,
Doug Anderson <dianders@chromium.org>,
Olof Johansson <olof@lixom.net>,
Yufeng Shen <miletus@chromium.org>,
Benson Leung <bleung@chromium.org>,
Chung-yih Wang <cywang@chromium.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Input: atmel_mxt_ts - Split out touchpad initialisation logic
Date: Mon, 6 Apr 2015 13:30:57 -0700 [thread overview]
Message-ID: <20150406203057.GC36776@dtor-ws> (raw)
In-Reply-To: <1426600846-13346-3-git-send-email-javier.martinez@collabora.co.uk>
On Tue, Mar 17, 2015 at 03:00:46PM +0100, Javier Martinez Canillas wrote:
> From: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
>
> If the "linux,gpio-keymap" DT property is defined, the T19 keys are configured
> and the device is setup as a touchpad rather than a touchscreen. The logic is
> part of the input device initialization routine but it can be factored out to
> its own function to simplify the former.
>
> Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> ---
> drivers/input/touchscreen/atmel_mxt_ts.c | 48 +++++++++++++++++++-------------
> 1 file changed, 28 insertions(+), 20 deletions(-)
>
> diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c b/drivers/input/touchscreen/atmel_mxt_ts.c
> index 749371761669..e2e55cf857cb 100644
> --- a/drivers/input/touchscreen/atmel_mxt_ts.c
> +++ b/drivers/input/touchscreen/atmel_mxt_ts.c
> @@ -1815,15 +1815,40 @@ static int mxt_read_t100_config(struct mxt_data *data)
> static int mxt_input_open(struct input_dev *dev);
> static void mxt_input_close(struct input_dev *dev);
>
> +static bool mxt_initialize_t19(struct input_dev *input_dev,
> + struct mxt_data *data)
I renamed it as mxt_set_up_as_touchpad() and made void, otherwise
applied.
Thanks.
> +{
> + const struct mxt_platform_data *pdata = data->pdata;
> + int i;
> +
> + if (pdata->t19_num_keys) {
> + __set_bit(INPUT_PROP_BUTTONPAD, input_dev->propbit);
> +
> + for (i = 0; i < pdata->t19_num_keys; i++)
> + if (pdata->t19_keymap[i] != KEY_RESERVED)
> + input_set_capability(input_dev, EV_KEY,
> + pdata->t19_keymap[i]);
> +
> + input_abs_set_res(input_dev, ABS_X, MXT_PIXELS_PER_MM);
> + input_abs_set_res(input_dev, ABS_Y, MXT_PIXELS_PER_MM);
> + input_abs_set_res(input_dev, ABS_MT_POSITION_X,
> + MXT_PIXELS_PER_MM);
> + input_abs_set_res(input_dev, ABS_MT_POSITION_Y,
> + MXT_PIXELS_PER_MM);
> +
> + input_dev->name = "Atmel maXTouch Touchpad";
> + return true;
> + }
> + return false;
> +}
> +
> static int mxt_initialize_input_device(struct mxt_data *data)
> {
> struct device *dev = &data->client->dev;
> - const struct mxt_platform_data *pdata = data->pdata;
> struct input_dev *input_dev;
> int error;
> unsigned int num_mt_slots;
> unsigned int mt_flags = 0;
> - int i;
>
> switch (data->multitouch) {
> case MXT_TOUCH_MULTI_T9:
> @@ -1859,26 +1884,9 @@ static int mxt_initialize_input_device(struct mxt_data *data)
> set_bit(EV_ABS, input_dev->evbit);
> input_set_capability(input_dev, EV_KEY, BTN_TOUCH);
>
> - if (pdata->t19_num_keys) {
> - __set_bit(INPUT_PROP_BUTTONPAD, input_dev->propbit);
> -
> - for (i = 0; i < pdata->t19_num_keys; i++)
> - if (pdata->t19_keymap[i] != KEY_RESERVED)
> - input_set_capability(input_dev, EV_KEY,
> - pdata->t19_keymap[i]);
> -
> + if (mxt_initialize_t19(input_dev, data))
> mt_flags |= INPUT_MT_POINTER;
>
> - input_abs_set_res(input_dev, ABS_X, MXT_PIXELS_PER_MM);
> - input_abs_set_res(input_dev, ABS_Y, MXT_PIXELS_PER_MM);
> - input_abs_set_res(input_dev, ABS_MT_POSITION_X,
> - MXT_PIXELS_PER_MM);
> - input_abs_set_res(input_dev, ABS_MT_POSITION_Y,
> - MXT_PIXELS_PER_MM);
> -
> - input_dev->name = "Atmel maXTouch Touchpad";
> - }
> -
> /* For single touch */
> input_set_abs_params(input_dev, ABS_X,
> 0, data->max_x, 0, 0);
> --
> 2.1.4
>
--
Dmitry
next prev parent reply other threads:[~2015-04-06 20:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 14:00 [PATCH 0/2] Input: atmel_mxt_ts - Add support for T100 multi-touch Javier Martinez Canillas
2015-03-17 14:00 ` [PATCH 1/2] Input: atmel_mxt_ts - Implement support for T100 touch object Javier Martinez Canillas
2015-04-06 20:10 ` Dmitry Torokhov
2015-08-06 10:51 ` Dirk Behme
2015-08-06 11:11 ` Sjoerd Simons
2015-08-06 11:19 ` Javier Martinez Canillas
2015-08-06 13:02 ` Nick Dyer
2015-03-17 14:00 ` [PATCH 2/2] Input: atmel_mxt_ts - Split out touchpad initialisation logic Javier Martinez Canillas
2015-04-06 20:30 ` Dmitry Torokhov [this message]
2015-03-27 20:29 ` [PATCH 0/2] Input: atmel_mxt_ts - Add support for T100 multi-touch Javier Martinez Canillas
-- strict thread matches above, loose matches on Subject: below --
2014-12-15 10:39 Javier Martinez Canillas
2014-12-15 10:39 ` [PATCH 2/2] Input: atmel_mxt_ts - Split out touchpad initialisation logic Javier Martinez Canillas
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=20150406203057.GC36776@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=bleung@chromium.org \
--cc=cywang@chromium.org \
--cc=dianders@chromium.org \
--cc=javier.martinez@collabora.co.uk \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miletus@chromium.org \
--cc=nick.dyer@itdev.co.uk \
--cc=olof@lixom.net \
--cc=rydberg@euromail.se \
--cc=sjoerd.simons@collabora.co.uk \
/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).