All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Frank Praznik <frank.praznik@gmail.com>
Cc: Simon Wood <simon@mungewell.org>,
	Roderick Colenbrander <roderick@gaikai.com>,
	linux-input@vger.kernel.org, Jiri Kosina <jikos@kernel.org>,
	Tim Bird <tim.bird@am.sony.com>,
	Roderick Colenbrander <roderick.colenbrander@sony.com>,
	Frank Praznik <frank.praznik@oh.rr.com>,
	Antonio Ospite <ao2@ao2.it>
Subject: Re: [PATCH 4/5] HID: sony: Send ds4 output reports on output end-point
Date: Fri, 7 Oct 2016 17:56:28 +0200	[thread overview]
Message-ID: <20161007155628.GE30411@mail.corp.redhat.com> (raw)
In-Reply-To: <740B6F90-3CBB-45F6-AE7A-CA510D397B92@gmail.com>

On Oct 05 2016 or thereabouts, Frank Praznik wrote:
> 
> > On Oct 5, 2016, at 13:35, Simon Wood <simon@mungewell.org> wrote:
> > 
> > On Wed, October 5, 2016 10:54 am, Frank Praznik wrote:
> >> The best answer I can give is "not to my knowledge”.  Rumble and LEDs
> >> have standard kernel interfaces but obviously we can’t guarantee 100% that
> >> nobody is using hidraw directly.  Commercial games and engines aren't
> >> running as root and thus can’t use hidraw so I think we can safely say
> >> that no major commercial software will be broken by this.
> > 
> > There are a couple of projects I know of, but I am unable to say whether
> > they are still active or whether proposed changes will affect them...
> > https://thp.io/2010/psmove/
> > http://moveonpc.blogspot.ca/
> > https://github.com/chrippa/ds4drv
> > 
> > Audio output is one area of the DS4 which is not supported in kernel,
> > maybe some renewed interest can get this working.
> > 
> > I agree with Frank that we should move forward, if something gets broken
> > we can work a better solution.
> > Simon.
> > 
> > acked-by: Simon Wood <simon@mungewell.org>
> > 
> > 
> > 
> 
> This change only affects sending rumble/LED output reports to the DS4, so hidraw input reports and sending/receiving feature reports will be unchanged as will anything not in the DS4 codepath (ie. Move controllers).  It looks like ds4drv has both a hidraw backend and one which uses raw Bluetooth sockets.  The raw socket backend should be unaffected, but the hidraw backend will probably have issues.  It should be trivial to patch it to append the CRC to the raw data packet like the kernel module does though.  It also looks like hidraw isn’t the default Bluetooth backend which reduces the odds that it will be an issue even further.
> 
> I’m definitely in favor of moving toward more correct behavior as long as the ds4drv project is given a warning to start sending CRC-ed output reports.
> 
> acked-by: Frank Praznik <frank.praznik@gmail.com>

Then:
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
For the user-space change: Acked-by me too.

Cheers,
Benjamin

  reply	other threads:[~2016-10-07 15:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05  2:58 [PATCH 0/5] HID: sony: game controller updates Roderick Colenbrander
2016-10-05  2:58 ` [PATCH 1/5] HID: sony: Fix race condition in sony_probe Roderick Colenbrander
2016-10-05  2:58 ` [PATCH 2/5] HID: sony: Adjust HID report size name definitions Roderick Colenbrander
2016-10-05  2:58 ` [PATCH 3/5] HID: sony: Perform CRC check on bluetooth input packets Roderick Colenbrander
2016-10-05  8:24   ` Benjamin Tissoires
2016-10-05  2:58 ` [PATCH 4/5] HID: sony: Send ds4 output reports on output end-point Roderick Colenbrander
2016-10-05  8:31   ` Benjamin Tissoires
2016-10-05 16:54     ` Frank Praznik
2016-10-05 17:35       ` Simon Wood
2016-10-05 20:35         ` Frank Praznik
2016-10-07 15:56           ` Benjamin Tissoires [this message]
2016-10-05 18:53       ` Roderick Colenbrander
2016-10-05  2:58 ` [PATCH 5/5] HID: sony: Handle multiple touch events input record Roderick Colenbrander
2016-10-05  8:35   ` Benjamin Tissoires
2016-10-05 15:29     ` Simon Wood
2016-10-05 17:25       ` Roderick Colenbrander
2016-10-07 16:02         ` Benjamin Tissoires
2016-10-18 23:27           ` Roderick Colenbrander
2016-10-31  8:21             ` Benjamin Tissoires

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=20161007155628.GE30411@mail.corp.redhat.com \
    --to=benjamin.tissoires@redhat.com \
    --cc=ao2@ao2.it \
    --cc=frank.praznik@gmail.com \
    --cc=frank.praznik@oh.rr.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=roderick.colenbrander@sony.com \
    --cc=roderick@gaikai.com \
    --cc=simon@mungewell.org \
    --cc=tim.bird@am.sony.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.