linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Dillow <dave@thedillows.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: fold ps3remote driver into generic Sony driver
Date: Tue, 28 May 2013 09:30:47 -0400	[thread overview]
Message-ID: <1369747847.3675.3.camel@obelisk.thedillows.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1305281035370.3914@pobox.suse.cz>

On Tue, 2013-05-28 at 10:38 +0200, Jiri Kosina wrote:
> Let's follow the structure we are trying to keep for most of the specific 
> HID drivers, and let the separation follow the producing vendor.
> Merge functionality provided by ps3remote driver into hid-sony.
> 
> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
> ---

I've not had a chance to test yet, but I noticed one issue:
 
> @@ -548,6 +722,11 @@ static const struct hid_device_id sony_devices[] = {
>  		.driver_data = BUZZ_CONTROLLER },
>  	{ HID_USB_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_WIRELESS_BUZZ_CONTROLLER),
>  		.driver_data = BUZZ_CONTROLLER },
> +	/* PS3 BD Remote Control */
> +	{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_SONY, USB_DEVICE_ID_SONY_PS3_BDREMOTE),
> +		.driver_data = PS3REMOTE },
> +	/* Logitech Harmony Adapter for PS3 */
> +	{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_LOGITECH_HARMONY_PS3) },

I think you need .driver_data = PS3REMOTE for the Harmony as well; it
uses the same protocol.

Also, have you given any thought to making 'make oldconfig' work? Those
of us that build are own kernels are likely to have some fun tracking
down why our remotes don't work any more...

  reply	other threads:[~2013-05-28 13:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28  8:38 [PATCH] HID: fold ps3remote driver into generic Sony driver Jiri Kosina
2013-05-28 13:30 ` David Dillow [this message]
2013-05-28 13:45   ` Jiri Kosina
2013-06-01  4:55     ` David Dillow
2013-06-13  2:33       ` David Dillow
2013-06-13 10:05         ` 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=1369747847.3675.3.camel@obelisk.thedillows.org \
    --to=dave@thedillows.org \
    --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).