linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org, marcel@holtmann.org,
	linux-kernel@vger.kernel.org, anssi.hannula@gmail.com,
	Jiri Slaby <jslaby@suse.cz>
Subject: Re: [PATCH 06/10] HID: move logitech report quirks
Date: Wed, 4 Jun 2008 15:21:52 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0806041520140.10085@jikos.suse.cz> (raw)
In-Reply-To: <1210931362-18422-6-git-send-email-jirislaby@gmail.com>

On Fri, 16 May 2008, Jiri Slaby wrote:

>  static const struct hid_device_id hid_blacklist[] = {
> +	{ HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_MX3000_RECEIVER) },
> +	{ HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_S510_RECEIVER) },
> +	{ HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_S510_RECEIVER_2) },
>  	{ }
>  };

This shouldn't be needed as soon as the userspace supports the proper 
module autoloading, right?

> +#define LOGITECH_RDESC	0x1
> +
> +/*
> + * Certain Logitech keyboards send in report #3 keys which are far
> + * above the logical maximum described in descriptor. This extends
> + * the original value of 0x28c of logical maximum to 0x104d
> + */
> +static void lg_report_fixup(struct hid_device *hdev, __u8 *rdesc,
> +		unsigned int rsize)
> +{
> +	if (rsize >= 90 && rdesc[83] == 0x26
> +			&& rdesc[84] == 0x8c
> +			&& rdesc[85] == 0x02) {
> +		dev_info(&hdev->dev, "fixing up Logitech keyboard report "
> +				"descriptor\n");
> +		rdesc[84] = rdesc[89] = 0x4d;
> +		rdesc[85] = rdesc[90] = 0x10;
> +	}
> +}
> +
> +static const struct hid_device_id lg_devices[] = {
> +	{ HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_MX3000_RECEIVER),
> +		.driver_data = LOGITECH_RDESC },
> +	{ HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_S510_RECEIVER),
> +		.driver_data = LOGITECH_RDESC },
> +	{ HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_S510_RECEIVER_2),
> +		.driver_data = LOGITECH_RDESC },
> +	{ }

You set the LOGITECH_RDESC flag here, but it is then never used anywhere. 
I guess that your original intent was to check for this flag in 
lg_report_fixup(), right?

Thanks,

-- 
Jiri Kosina
SUSE Labs

  parent reply	other threads:[~2008-06-04 13:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16  9:49 [PATCH 01/10] modpost: add support for hid Jiri Slaby
2008-05-16  9:49 ` [PATCH 02/10] HID: make a bus from hid code Jiri Slaby
2008-05-16  9:49   ` [PATCH 03/10] HID: hid, make parsing event driven Jiri Slaby
2008-05-16  9:49     ` [PATCH 04/10] HID: move ids into separate file Jiri Slaby
2008-05-16  9:49       ` [PATCH 05/10] HID: move usage input mapping to hid.h Jiri Slaby
2008-05-16  9:49         ` [PATCH 06/10] HID: move logitech report quirks Jiri Slaby
2008-05-16  9:49           ` [PATCH 07/10] HID: move ignore quirks Jiri Slaby
2008-05-16  9:49             ` [PATCH 08/10] HID: move apple quirks Jiri Slaby
2008-05-16  9:49               ` [PATCH 09/10] HID: add compat support Jiri Slaby
2008-06-04  8:55                 ` Jiri Kosina
2008-06-04  9:00                   ` Jiri Slaby
2009-01-24  5:55                 ` Jaswinder Singh Rajput
2009-01-25 13:03                   ` Jiri Slaby
2009-01-25 16:57                   ` Jiri Kosina
2009-01-25 17:11                     ` Jaswinder Singh Rajput
2008-06-04 14:13               ` [PATCH 08/10] HID: move apple quirks Jiri Kosina
2008-06-09 10:40                 ` Jiri Slaby
2008-06-04 12:16           ` [PATCH 06/10] HID: move logitech report quirks Jiri Kosina
2008-06-09 10:29             ` Jiri Slaby
2008-06-16 10:15               ` Jiri Kosina
2008-06-04 13:21           ` Jiri Kosina [this message]
2008-06-09 10:33             ` Jiri Slaby
2008-06-11 14:13               ` Jiri Kosina
2008-06-11 15:39                 ` Oliver Neukum
2008-06-11 18:35                   ` Jiri Slaby
2008-06-11 18:23                 ` Anssi Hannula
2008-05-19 13:36 ` [PATCH 01/10] modpost: add support for hid Jiri Kosina
2008-05-19 13:38   ` Jiri Slaby
2008-05-19 13:50 ` [PATCH v2] " Jiri Slaby
2008-06-05  9:26 ` [PATCH 01/10] " Jiri Kosina
2008-06-09 10:41   ` Jiri Slaby

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=Pine.LNX.4.64.0806041520140.10085@jikos.suse.cz \
    --to=jkosina@suse.cz \
    --cc=anssi.hannula@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jirislaby@gmail.com \
    --cc=jslaby@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.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).