linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Bastien Nocera <hadess@hadess.net>, linux-input@vger.kernel.org
Subject: Re: [PATCH 1/5] Input: Add input_copy_abs() function
Date: Mon, 31 Jan 2022 14:21:03 +0100	[thread overview]
Message-ID: <939ea349-bfd7-4580-0745-013fcbc98100@redhat.com> (raw)
In-Reply-To: <YbbTERA000U9bPPR@google.com>

Hi Dmitry,

Thank you for your review of this patch series; and sorry for
being so slow in getting back to you on this.

On 12/13/21 05:58, Dmitry Torokhov wrote:
> Hi Hans,
> 
> On Sun, Dec 12, 2021 at 01:42:38PM +0100, Hans de Goede wrote:
>> Add a new helper function to copy absinfo from one input_dev to
>> another input_dev.
>>
>> This is useful to e.g. setup a pen/stylus input-device for combined
>> touchscreen/pen hardware where the pen uses the same coordinates as
>> the touchscreen.
>>
>> Suggested-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>> ---
>>  drivers/input/input.c | 34 ++++++++++++++++++++++++++++++++++
>>  include/linux/input.h |  2 ++
>>  2 files changed, 36 insertions(+)
>>
>> diff --git a/drivers/input/input.c b/drivers/input/input.c
>> index ccaeb2426385..60f3eb38906f 100644
>> --- a/drivers/input/input.c
>> +++ b/drivers/input/input.c
>> @@ -526,6 +526,40 @@ void input_set_abs_params(struct input_dev *dev, unsigned int axis,
>>  }
>>  EXPORT_SYMBOL(input_set_abs_params);
>>  
>> +/**
>> + * input_copy_abs - Copy absinfo from one input_dev to another
>> + * @dst: Destination input device to copy the abs settings to
>> + * @dst_axis: ABS_* value selecting the destination axis
>> + * @src: Source input device to copy the abs settings from
>> + * @src_axis: ABS_* value selecting the source axis
>> + *
>> + * Set absinfo for the selected destination axis by copying it from
>> + * the specified source input device's source axis.
>> + * This is useful to e.g. setup a pen/stylus input-device for combined
>> + * touchscreen/pen hardware where the pen uses the same coordinates as
>> + * the touchscreen.
>> + */
>> +void input_copy_abs(struct input_dev *dst, unsigned int dst_axis,
>> +		    const struct input_dev *src, unsigned int src_axis)
>> +{
>> +	/*
>> +	 * input_alloc_absinfo() may have failed for the source. Our caller is
>> +	 * expected to catch this when registering the input devices, which may
>> +	 * happen after the input_copy_abs() call.
>> +	 */
>> +	if (!src->absinfo)
>> +		return;
> 
> I'd probably check if source device actually declared EV_ABS/src_axis
> and yelled loudly (WARN?) in such case.

Ack, I will add this for v2.

> 
>> +
>> +	input_alloc_absinfo(dst);
>> +	if (!dst->absinfo)
>> +		return;
>> +
>> +	dst->absinfo[dst_axis] = src->absinfo[src_axis];
>> +
>> +	__set_bit(EV_ABS, dst->evbit);
>> +	__set_bit(dst_axis, dst->absbit);
> 
> input_set_capability() ?

Ack.

Regards,

Hans



> 
>> +}
>> +EXPORT_SYMBOL(input_copy_abs);
> 
> Thanks.
> 


  reply	other threads:[~2022-01-31 13:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-12 12:42 [PATCH 0/5] Input: goodix - Various fixes and improvements Hans de Goede
2021-12-12 12:42 ` [PATCH 1/5] Input: Add input_copy_abs() function Hans de Goede
2021-12-13  4:58   ` Dmitry Torokhov
2022-01-31 13:21     ` Hans de Goede [this message]
2021-12-12 12:42 ` [PATCH 2/5] Input: goodix - Use input_copy_abs() helper Hans de Goede
2021-12-12 12:42 ` [PATCH 3/5] Input: goodix - Improve gpiod_get() error logging Hans de Goede
2021-12-13  4:56   ` Dmitry Torokhov
2021-12-12 12:42 ` [PATCH 4/5] Input: goodix - 2 small fixes for pen support Hans de Goede
2021-12-13  4:56   ` Dmitry Torokhov
2021-12-12 12:42 ` [PATCH 5/5] Input: goodix - Fix race on driver unbind Hans de Goede
2021-12-13  4:56   ` Dmitry Torokhov
2022-01-31 14:31     ` Hans de Goede

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=939ea349-bfd7-4580-0745-013fcbc98100@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hadess@hadess.net \
    --cc=linux-input@vger.kernel.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).