From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B92EAC3F68F for ; Sun, 9 Feb 2020 05:05:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8B7B32080C for ; Sun, 9 Feb 2020 05:05:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="YpCKXdq4" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725796AbgBIFFF (ORCPT ); Sun, 9 Feb 2020 00:05:05 -0500 Received: from mail-qk1-f195.google.com ([209.85.222.195]:36299 "EHLO mail-qk1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725730AbgBIFFF (ORCPT ); Sun, 9 Feb 2020 00:05:05 -0500 Received: by mail-qk1-f195.google.com with SMTP id w25so3359269qki.3; Sat, 08 Feb 2020 21:05:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0WxM1glhIHjjmYurDeLuwSMUWAv8GZusKOox9UoQmHA=; b=YpCKXdq4e/ZXIPs4qBNeOCqrj4t31kXsyUGJRwzK1YGTllAuHfzDWtC9x1Nev/Mu5c BOJIn7lBL0zRHBTAIGnQkXDokkbZqfKh5Q07zFXt+LKS3ga0IZ1JvXGDVcJpr7St8wev 62bXjtn0Vin3/1dSsOR62vxp6a226jATfZt0YhKGYaRIYMBnVb43DOJzyL59mWnpXfYb qb/sGW8pIIL+F9xJfgxKztWCqJ+jYOTKSGwNlQl7stYGkoO2ZheIL4HZYYZqAhysQEQV xChdPkoFSQg5dkPouEyTi0nb5+zgihtSNZueFNFnmVduA2aTKjiTO/lvK+yqn019eco+ BSZw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0WxM1glhIHjjmYurDeLuwSMUWAv8GZusKOox9UoQmHA=; b=r/NF5s1tdktiwvbXZBVEzW88Jylep42XMD6CmbfvmQsB5GYZQDruffw3/eyKIQSTlx GkQO0cvkTwFtmyXI1vxytW+hpAzLcfUc5Hi5TbYrIrT5QRcKa5uo0TUAysQG875UlFkB lZW72BI8hwdae8eVANISb5OIjofPq9pjOh0ICr3E82lMz6hls5x7Ev7LVWEAvNLY7/91 VwOfIFo5wjMLbNkLOIcQA9brNEt3AKM4zXP0MenAGJiCONBHZ0MTIJugrZyo5f+IK1UK G6m5Xlpet68wRkkfxIzRbtAb71M+IS9FKdbJ6VEp39TlZkPdw5jgA+IcMX+TmG3iW0l9 ehEg== X-Gm-Message-State: APjAAAUqO05RM3WeoNoDldnUyJBHwfQEhdw7cw/6ulWtXKiJQvRIG1Xm l42xfcF2h8kwVNt0hWOmwpWfDCB+DCt0F19ta2R64Q== X-Google-Smtp-Source: APXvYqxMaFnuxS5GfhlBEbE5HlQXiqUXBYU/S6sHRodHl12GIYOkvxTkK0Tx3b3UzFErLCu+nhZEdGVj9grt366ooac= X-Received: by 2002:a37:e109:: with SMTP id c9mr5238665qkm.366.1581224702791; Sat, 08 Feb 2020 21:05:02 -0800 (PST) MIME-Version: 1.0 References: <20200126194513.6359-1-martyn@welchs.me.uk> <7234b9c22612f43c9458e84f74faf32f658b0015.camel@hadess.net> In-Reply-To: <7234b9c22612f43c9458e84f74faf32f658b0015.camel@hadess.net> From: Roderick Colenbrander Date: Sat, 8 Feb 2020 21:04:51 -0800 Message-ID: Subject: Re: [PATCH] HID: Sony: Add support for Gasia controllers To: Bastien Nocera Cc: Benjamin Tissoires , Jiri Kosina , Martyn Welch , linux-input , lkml , "Conn O'Griofa" , "Colenbrander, Roelof" Content-Type: text/plain; charset="UTF-8" Sender: linux-input-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-input@vger.kernel.org On Thu, Feb 6, 2020 at 1:34 AM Bastien Nocera wrote: > > On Thu, 2020-02-06 at 09:09 +0100, Benjamin Tissoires wrote: > > > > > If this is something Roderick would be interested in, we can then try > > to extend this initial work on Bluetooth controllers and the > > DualShock > > ones. > > Adding the clones ones based on the current kernel code is something > > doable, but I do not expect Sony to be involved in that process. > > Sony didn't provide any of the code that allows us to support those > devices over Bluetooth, and support isn't complete either. > > I'd certainly appreciate getting information about how to pair those > devices (if there's anything on top of the code already implemented), > how to pair the PS3 headset and keyboard accessories (which are still > unsupported), and how to access the headset pairing for the PS4 > controllers. > At this point our main priority is supported related to DS4 (this is what our permission is for). The other areas are very hard for me to get info on, so I can't promise that right now. Audio related stuff for DS4 is a maybe at some point. It is very complicated and all tunnelled through HID... (in case of Bluetooth). Thanks, Roderick