linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Henrik Rydberg" <rydberg@euromail.se>
To: Benjamin Tissoires <benjamin.tissoires@enac.fr>
Cc: Stephane Chatty <chatty@enac.fr>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Jiri Kosina <jkosina@suse.cz>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC v3 1/5] hid: add feature_mapping callback
Date: Fri, 7 Jan 2011 19:59:39 +0100	[thread overview]
Message-ID: <20110107185939.GA29913@polaris.bitmath.org> (raw)
In-Reply-To: <1294425762-29730-2-git-send-email-benjamin.tissoires@enac.fr>

On Fri, Jan 07, 2011 at 07:42:38PM +0100, Benjamin Tissoires wrote:
> Currently hid doesn't export the features it knows to the specific modules.
> Some information can be really important in such features: MosArt and
> Cypress devices are by default not in a multitouch mode.
> We have to send the value 2 on the right feature.
> 
> This patch exports to the module the features report so they can find the
> right feature to set up the correct mode.
> 
> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@enac.fr>
> ---

Hi Benjamin,

the patch series has some impurities (see checkpatch), and some minor comments below, but all in all,

Acked-by: Henrik Rydberg <rydberg@euromail.se>

>  drivers/hid/hid-input.c |   17 +++++++++++++----
>  include/linux/hid.h     |    4 ++++
>  2 files changed, 17 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/hid/hid-input.c b/drivers/hid/hid-input.c
> index bb0b365..e1b48e4 100644
> --- a/drivers/hid/hid-input.c
> +++ b/drivers/hid/hid-input.c
> @@ -287,6 +287,14 @@ static void hidinput_configure_usage(struct hid_input *hidinput, struct hid_fiel
>  		goto ignore;
>  	}
>  
> +	if (field->report_type == HID_FEATURE_REPORT) {
> +		if (device->driver->feature_mapping) {
> +			device->driver->feature_mapping(device, hidinput, field,
> +                                usage);
> +		}
> +		goto ignore;
> +	}
> +
>  	if (device->driver->input_mapping) {
>  		int ret = device->driver->input_mapping(device, hidinput, field,
>  				usage, &bit, &max);
> @@ -836,7 +844,6 @@ int hidinput_connect(struct hid_device *hid, unsigned int force)
>  	struct hid_input *hidinput = NULL;
>  	struct input_dev *input_dev;
>  	int i, j, k;
> -	int max_report_type = HID_OUTPUT_REPORT;
>  
>  	INIT_LIST_HEAD(&hid->inputs);
>  
> @@ -853,10 +860,11 @@ int hidinput_connect(struct hid_device *hid, unsigned int force)
>  			return -1;
>  	}
>  
> -	if (hid->quirks & HID_QUIRK_SKIP_OUTPUT_REPORTS)
> -		max_report_type = HID_INPUT_REPORT;
> +	for (k = HID_INPUT_REPORT; k <= HID_FEATURE_REPORT; k++) {
> +		if (k == HID_OUTPUT_REPORT &&
> +			hid->quirks & HID_QUIRK_SKIP_OUTPUT_REPORTS)

Omitting the parenthesis here is not wrong, but not really customary either.

> +			continue;
>  
> -	for (k = HID_INPUT_REPORT; k <= max_report_type; k++)
>  		list_for_each_entry(report, &hid->report_enum[k].report_list, list) {
>  
>  			if (!report->maxfield)
> @@ -909,6 +917,7 @@ int hidinput_connect(struct hid_device *hid, unsigned int force)
>  				hidinput = NULL;
>  			}
>  		}
> +	}
>  
>  	if (hidinput && input_register_device(hidinput->input))
>  		goto out_cleanup;
> diff --git a/include/linux/hid.h b/include/linux/hid.h
> index bb0f56f..75303b0 100644
> --- a/include/linux/hid.h
> +++ b/include/linux/hid.h
> @@ -593,6 +593,7 @@ struct hid_usage_id {
>   * @report_fixup: called before report descriptor parsing (NULL means nop)
>   * @input_mapping: invoked on input registering before mapping an usage
>   * @input_mapped: invoked on input registering after mapping an usage
> + * @feature_mapping: invoked on feature registering
>   * @suspend: invoked on suspend (NULL means nop)
>   * @resume: invoked on resume if device was not reset (NULL means nop)
>   * @reset_resume: invoked on resume if device was reset (NULL means nop)
> @@ -636,6 +637,9 @@ struct hid_driver {
>  	int (*input_mapped)(struct hid_device *hdev,
>  			struct hid_input *hidinput, struct hid_field *field,
>  			struct hid_usage *usage, unsigned long **bit, int *max);
> +	void (*feature_mapping)(struct hid_device *hdev,
> + 			struct hid_input *hidinput, struct hid_field *field,
> + 			struct hid_usage *usage);
>  #ifdef CONFIG_PM
>  	int (*suspend)(struct hid_device *hdev, pm_message_t message);
>  	int (*resume)(struct hid_device *hdev);
> -- 
> 1.7.3.4
> 

Thanks,
Henrik

  reply	other threads:[~2011-01-07 19:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07 18:42 [RFC v3 0/5] hid-multitouch: a first step towards multitouch unification Benjamin Tissoires
2011-01-07 18:42 ` [RFC v3 1/5] hid: add feature_mapping callback Benjamin Tissoires
2011-01-07 18:59   ` Henrik Rydberg [this message]
2011-01-07 19:09     ` Benjamin Tissoires
2011-01-07 18:42 ` [RFC v3 2/5] hid: set HID_MAX_FIELD at 128 Benjamin Tissoires
2011-01-07 18:42 ` [RFC v3 3/5] hid-multitouch: support for PixCir-based panels Benjamin Tissoires
2011-01-07 19:49   ` Henrik Rydberg
2011-01-10 19:10     ` Benjamin Tissoires
2011-01-11 13:00       ` Henrik Rydberg
2011-01-11 13:53         ` Benjamin Tissoires
2011-01-11 15:10           ` Benjamin Tissoires
2011-01-07 18:42 ` [RFC v3 4/5] hid-multitouch: added support for Cypress TrueTouch panels Benjamin Tissoires
2011-01-07 20:00   ` Henrik Rydberg
2011-01-10 19:13     ` Benjamin Tissoires
2011-01-07 18:42 ` [RFC v3 5/5] hid-mulitouch: added support for the 'Sensing Win7-TwoFinger' Benjamin Tissoires
2011-01-07 20:03   ` Henrik Rydberg
2011-01-07 19:12 ` [RFC v3 0/5] hid-multitouch: a first step towards multitouch unification Benjamin Tissoires
2011-01-07 20:08 ` Henrik Rydberg
2011-01-07 21:06   ` Benjamin Tissoires
2011-01-07 22:58 ` Jiri Kosina
2011-01-07 23:00   ` Jiri Kosina
2011-01-08 21:25     ` Jiri Kosina
2011-01-10 18:32       ` Jiri Kosina
2011-01-10 19:24         ` Benjamin Tissoires
2011-01-11 10:37           ` Jiri Kosina

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=20110107185939.GA29913@polaris.bitmath.org \
    --to=rydberg@euromail.se \
    --cc=benjamin.tissoires@enac.fr \
    --cc=chatty@enac.fr \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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).