From: Szymon Janc <szymon.janc@gmail.com>
To: David Herrmann <dh.herrmann@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Simon Wood <simon@mungewell.org>,
Frank Praznik <frank.praznik@oh.rr.com>
Subject: Re: [PATCH 3/3] input: Add DualShock 4 detection
Date: Sat, 18 Jan 2014 16:13:32 +0100 [thread overview]
Message-ID: <1572567.ZoR782tNKQ@athlon> (raw)
In-Reply-To: <CANq1E4Tm2na1zVCdeDK5ihS0fQKCpJ10P0a+pTVUmcURTqCV9A@mail.gmail.com>
Hi,
On Saturday 18 January 2014 16:05:26 David Herrmann wrote:
> Hi
>
> @Simon and Frank:
> This patch might help fix your DS4 issues.
>
> Cheers
> David
Just for clarification, this does not add DS4 support, just detection for it
in input server. There is some problem with getting SDP records from DS4 by
bluetoothd (works with sdptool) which prevents idev from being created.
I'm working on fixing this, but no ETA yet.
>
> On Sat, Jan 18, 2014 at 3:57 PM, Szymon Janc <szymon.janc@gmail.com> wrote:
> > DS4 tries to connect right after pairing before SDP search completed
> > and no idev is present yet.
> > ---
> >
> > profiles/input/server.c | 16 +++++++++++-----
> > 1 file changed, 11 insertions(+), 5 deletions(-)
> >
> > diff --git a/profiles/input/server.c b/profiles/input/server.c
> > index 3814eaf..21c589c 100644
> > --- a/profiles/input/server.c
> > +++ b/profiles/input/server.c
> > @@ -118,18 +118,24 @@ static void sixaxis_browse_sdp(const bdaddr_t *src,
> > const bdaddr_t *dst,>
> > static bool dev_is_sixaxis(const bdaddr_t *src, const bdaddr_t *dst)
> > {
> >
> > struct btd_device *device;
> >
> > + uint16_t vid, pid;
> >
> > device = btd_adapter_find_device(adapter_find(src), dst);
> > if (!device)
> >
> > return false;
> >
> > - if (btd_device_get_vendor(device) != 0x054c)
> > - return false;
> > + vid = btd_device_get_vendor(device);
> > + pid = btd_device_get_product(device);
> >
> > - if (btd_device_get_product(device) != 0x0268)
> > - return false;
> > + /* DualShock 3 */
> > + if (vid == 0x054c && pid == 0x0268)
> > + return true;
> > +
> > + /* DualShock 4 */
> > + if (vid == 0x054c && pid == 0x05c4)
> > + return true;
> >
> > - return true;
> > + return false;
> >
> > }
> >
> > static void connect_event_cb(GIOChannel *chan, GError *err, gpointer
> > data)
> >
> > --
> > 1.8.5.3
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-bluetooth"
> > in the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Szymon K. Janc
szymon.janc@gmail.com
next prev parent reply other threads:[~2014-01-18 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 14:57 [PATCH 1/3] eir: Add support for parsing DeviceID info Szymon Janc
2014-01-18 14:57 ` [PATCH 2/3] adapter: Add support for setting DID info from EIR Szymon Janc
2014-01-18 14:57 ` [PATCH 3/3] input: Add DualShock 4 detection Szymon Janc
2014-01-18 15:05 ` David Herrmann
2014-01-18 15:13 ` Szymon Janc [this message]
2014-01-20 4:37 ` Frank Praznik
2014-01-18 19:09 ` [PATCH 1/3] eir: Add support for parsing DeviceID info Johan Hedberg
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=1572567.ZoR782tNKQ@athlon \
--to=szymon.janc@gmail.com \
--cc=dh.herrmann@gmail.com \
--cc=frank.praznik@oh.rr.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=simon@mungewell.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).