All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Whitlock <linux@mattwhitlock.name>
To: linux-input@vger.kernel.org, Henrik Rydberg <rydberg@bitmath.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH 2/2] Input: bcm5974 - report ABS_MT_PRESSURE + remove redundant emulation code
Date: Mon, 06 Jul 2015 14:37:24 -0400	[thread overview]
Message-ID: <7271343.oGOpcDThz2@crushinator> (raw)
In-Reply-To: <1433812075-16622-2-git-send-email-linux@mattwhitlock.name>

It's been four weeks, and I haven't heard back on this patch. I believe I've implemented what was requested. Is there a problem with it?


On Monday, 8 June 2015, at 9:07 pm, Matt Whitlock wrote:
> Now that input_mt_report_pointer_emulation() can synthesize ABS_TOOL_WIDTH
> from ABS_MT_WIDTH_MAJOR, the report_synaptics_data() function in bcm5974.c
> is entirely redundant. This patch removes this function and introduces
> reporting of ABS_MT_PRESSURE (faked from f->touch_major) to cause the
> emulation code to synthesize ABS_PRESSURE.
> 
> Signed-off-by: Matt Whitlock <linux@mattwhitlock.name>

  reply	other threads:[~2015-07-06 18:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 11:49 [PATCH] Input: bcm5974 - report highest finger pressure to Synaptics Matt Whitlock
2015-06-03 12:24 ` Henrik Rydberg
2015-06-03 12:31   ` Matt Whitlock
2015-06-03 12:52     ` Henrik Rydberg
2015-06-09  1:07       ` [PATCH 1/2] Input: input_mt_report_pointer_emulation(), rescale pressure + tool width Matt Whitlock
2015-06-09  1:07         ` [PATCH 2/2] Input: bcm5974 - report ABS_MT_PRESSURE + remove redundant emulation code Matt Whitlock
2015-07-06 18:37           ` Matt Whitlock [this message]
2015-07-06 19:11             ` Henrik Rydberg
2015-07-06 19:35               ` Matt Whitlock
2015-07-06 19:44                 ` Henrik Rydberg
2015-07-06 19:59                   ` Matt Whitlock

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=7271343.oGOpcDThz2@crushinator \
    --to=linux@mattwhitlock.name \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=rydberg@bitmath.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.