linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Ott <alan@signal11.us>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: linux-input@vger.kernel.org, Jiri Kosina <jkosina@suse.cz>,
	Jim Paris <jim@jtan.com>, Ranulf Doswell <ralf@ranulf.net>,
	falktx@gmail.com
Subject: Re: [RFC, PATCH] HID: hid-sony, override usbhid_output_raw_report    for Sixaxis
Date: Thu, 14 Oct 2010 11:09:33 -0400	[thread overview]
Message-ID: <4CB71D2D.90200@signal11.us> (raw)
In-Reply-To: <20101014094840.e215ef88.ospite@studenti.unina.it>

On 10/14/2010 03:48 AM, Antonio Ospite wrote:
>
> The point about overriding hid_output_raw_report() is not about
> sixaxis_set_operational_usb() sending a control message, but about any
> _output_ (not feature) report the user would like to send via
> hidraw_write(), the sixaxis will accept those only if sent on the
> control endpoint (it will discard them if sent on the interrupt ep,
> like the current usbhid code does) maybe I didn't state that clearly,
> sorry.
>    

Ok, that makes a lot more sense then. You're saying it's not about the 
code _in_ your driver, it's about userspace code accessing the sixaxis 
via hidraw.

My personal preference is that I like the override idea better than the 
quirk. An override will be slightly faster, because of not having to 
check for the quirk in non-sixaxis cases.

> About sixaxis_set_operational_usb(), I don't remember _any_ change to
> it except its name, but I guess we can very well make it call
> hid_output_raw_report(), just only after your hidraw feature report
> patches land to mainline.
>
>    

sixaxis_set_operational_usb() doesn't bother me. I was confused about 
the original intent of your patch.

Alan.



  reply	other threads:[~2010-10-14 15:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-02 15:59 hidraw, sixaxis and output reports Antonio Ospite
2010-10-04 13:58 ` Alan Ott
2010-10-13 20:57   ` [RFC, PATCH 0/2] Enable setting leds via hidraw on Sixaxis Antonio Ospite
2010-10-13 22:15     ` Alan Ott
2010-10-13 22:27       ` Antonio Ospite
2010-10-13 22:54       ` [RFC, PATCH] HID: hid-sony, override usbhid_output_raw_report for Sixaxis Antonio Ospite
2010-10-13 23:23         ` Alan Ott
2010-10-14  7:48           ` Antonio Ospite
2010-10-14 15:09             ` Alan Ott [this message]
2010-10-19 14:13               ` [PATCH] " Antonio Ospite
2010-10-20 14:51                 ` Jiri Kosina
2010-10-13 20:57   ` [RFC, PATCH 1/2] HID: usbhid, new quirk to force out reports on the control ep Antonio Ospite
2010-10-13 20:57   ` [RFC, PATCH 2/2] HID: hid-sony, use HID_QUIRK_FORCE_OUT_CONTROL_EP for Sixaxis Antonio Ospite

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=4CB71D2D.90200@signal11.us \
    --to=alan@signal11.us \
    --cc=falktx@gmail.com \
    --cc=jim@jtan.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=ospite@studenti.unina.it \
    --cc=ralf@ranulf.net \
    /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).