From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Yufeng Shen <miletus@chromium.org>
Cc: linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Henrik Rydberg <rydberg@euromail.se>,
Iiro Valkonen <iiro.valkonen@atmel.com>,
Joonyoung Shim <jy0922.shim@samsung.com>,
Chris Leech <christopher.leech@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: atmel_mxt_ts - Report pressure information from the driver
Date: Wed, 27 Jul 2011 08:48:18 +0800 [thread overview]
Message-ID: <4E2F6052.4090101@cn.fujitsu.com> (raw)
In-Reply-To: <1311721553-17241-1-git-send-email-miletus@chromium.org>
On 07/27/2011 07:05 AM, Yufeng Shen wrote:
> Atmel mxt1386 touch controller has the touch pressure information but
> the current driver atmel_mxt_ts does not expose it to the user space.
> This patch makes the driver report the touch pressure information to
> user space.
>
> Change-Id: Ie0e4683a3cd5ec79222f7682b0ddc24f909af543
>
> ---
> drivers/input/touchscreen/atmel_mxt_ts.c | 8 ++++++++
> 1 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c b/drivers/input/touchscreen/atmel_mxt_ts.c
> index ae00604..7cedb06 100644
> --- a/drivers/input/touchscreen/atmel_mxt_ts.c
> +++ b/drivers/input/touchscreen/atmel_mxt_ts.c
> @@ -244,6 +244,7 @@ struct mxt_finger {
> int x;
> int y;
> int area;
> + int pressure;
Spaces you are introducing.
> };
>
> /* Each client has this additional data */
> @@ -536,6 +537,8 @@ static void mxt_input_report(struct mxt_data *data, int single_id)
> finger[id].x);
> input_report_abs(input_dev, ABS_MT_POSITION_Y,
> finger[id].y);
> + input_report_abs(input_dev, ABS_MT_PRESSURE,
> + finger[id].pressure);
> } else {
> finger[id].status = 0;
> }
> @@ -560,6 +563,7 @@ static void mxt_input_touchevent(struct mxt_data *data,
> int x;
> int y;
> int area;
> + int pressure;
same
>
> /* Check the touch is present on the screen */
> if (!(status& MXT_DETECT)) {
> @@ -584,6 +588,7 @@ static void mxt_input_touchevent(struct mxt_data *data,
> y = y>> 2;
>
> area = message->message[4];
> + pressure = message->message[5];
same
>
> dev_dbg(dev, "[%d] %s x: %d, y: %d, area: %d\n", id,
> status& MXT_MOVE ? "moved" : "pressed",
> @@ -594,6 +599,7 @@ static void mxt_input_touchevent(struct mxt_data *data,
> finger[id].x = x;
> finger[id].y = y;
> finger[id].area = area;
> + finger[id].pressure = pressure;
same
>
> mxt_input_report(data, id);
> }
> @@ -1125,6 +1131,8 @@ static int __devinit mxt_probe(struct i2c_client *client,
> 0, data->max_x, 0, 0);
> input_set_abs_params(input_dev, ABS_MT_POSITION_Y,
> 0, data->max_y, 0, 0);
> + input_set_abs_params(input_dev, ABS_MT_PRESSURE,
> + 0, 255, 0, 0);
>
> input_set_drvdata(input_dev, data);
> i2c_set_clientdata(client, data);
So, please indent with tabs instead of spaces.
--
Thanks
Best Regards
Wanlong Gao
prev parent reply other threads:[~2011-07-27 0:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 23:05 [PATCH] Input: atmel_mxt_ts - Report pressure information from the driver Yufeng Shen
2011-07-27 0:48 ` Wanlong Gao [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=4E2F6052.4090101@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=christopher.leech@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=iiro.valkonen@atmel.com \
--cc=jy0922.shim@samsung.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miletus@chromium.org \
--cc=rydberg@euromail.se \
/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).