Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp2220992rwb; Sat, 19 Nov 2022 11:14:57 -0800 (PST) X-Google-Smtp-Source: AA0mqf6iLIz1qVDrR5o06ryQFkaCARk7D9OVjAO2BNqwzs56o6gyE0mg2GWVOE2r48SZN6Nhv6lu X-Received: by 2002:a17:906:7e51:b0:78d:4fcb:1303 with SMTP id z17-20020a1709067e5100b0078d4fcb1303mr10619608ejr.182.1668885296805; Sat, 19 Nov 2022 11:14:56 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1668885296; cv=none; d=google.com; s=arc-20160816; b=ZkZBBZ9PB7sGYgHYJvoBfKABpv/9d77FFF7Nv2kMAEj+AesbJeKCj9In0lBkDrFUzB TtMQwjRVPIXAD5FcqhUYMJ2e8wuiIV3Nwd37Ttlz2L0k3w5lW9eMwpmEIuqY3kqwRRKc +UjJVroNSmXnaSuDuhoNy4KvRaCPkMFGxCuylEsIDdyKRfxHPYg1Xdwexi4DqkPj4Qau M9l+bdYhEGYPYG41qupzUMwISZfug41mA6Geq53kMhrz3AuLSdyWYap9Axz9dNNiWbgs imiWuTsQk6ZHdLIlaJzmdjd/np4Lj2rX2ktfYUsXEvoOqYhJPJy779BedWqkoWU+xUNH f4lg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=ngbtUsaSkr0xAQANdeKSQxqNZ35BF9l5Sh9sCXu0iLg=; b=P98DVfPHrnZIi3CT5myvLuLaVAIvl19rCimTjbJ7/y+4a2JKka3VnbF0Zwu8j+pqGA 98UtOth9esiQN5BkMNpBlg250n2iOLkpJ+kowQIwsbxUUuGIaQQdVm9QpwRszBF3BM7Q 5bhz/xr2sZ5JsEC+R9qWay4Ydf2jkvBz/grCA+6vvm95tvJf/bjGBJwrZlrDOe8GKgMJ S4JNiS4rhqB8A5zOe2cbgtJJFZddtZwetAqn2brstpfNg5/joSb5hSrUFgIL6hkhWOPM xmiX6Ke4hwKKed5Ez1brgIA6nuXxApUIxQIqHggQa16jCBMzZywFhRP8C92gKqKXF81k DLgQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id xg2-20020a170907320200b007adca6532d5si5365161ejb.708.2022.11.19.11.14.27; Sat, 19 Nov 2022 11:14:56 -0800 (PST) Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230398AbiKSTDz (ORCPT + 99 others); Sat, 19 Nov 2022 14:03:55 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52366 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233576AbiKSTDx (ORCPT ); Sat, 19 Nov 2022 14:03:53 -0500 Received: from netrider.rowland.org (netrider.rowland.org [192.131.102.5]) by lindbergh.monkeyblade.net (Postfix) with SMTP id B56DD25FB for ; Sat, 19 Nov 2022 11:03:51 -0800 (PST) Received: (qmail 71881 invoked by uid 1000); 19 Nov 2022 14:03:50 -0500 Date: Sat, 19 Nov 2022 14:03:50 -0500 From: Alan Stern To: Andrew McNaughton Cc: linux-usb@vger.kernel.org, linux-bluetooth@vger.kernel.org Subject: Re: How to get USB bluetooth device supported? Message-ID: References: <8AA450C9-623F-45C0-9981-93F3A3A7AAA0@me.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,SPF_HELO_PASS,SPF_PASS autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org On Sat, Nov 19, 2022 at 11:37:51AM +0000, Andrew McNaughton wrote: > How does one go about getting a device that should work with btusb but doesn’t? It works fine with Microsoft generic bt drivers. You might try CC'ing the linux-bluetooth mailing list. They probably have a better idea of what's going on with the btusb driver than people on the linux-usb mailing list do. > I can see people adding new VID/PID’s to btusb but I don’t know if that’s all that’s needed here. It probably won't make any difference. Your excerpt from /sys/kernel/debug/usb/devices below shows that the btusb driver is already binding to the device. Alan Stern > This is for a Bluetooth 5.3 transceiver. There’s not a lot of these about yet but I think important for accessing newer/upcoming audio purposes. > > > From /sys/kernel/debug/usb/devices: > > T: Bus=02 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 > D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 > P: Vendor=10d7 ProdID=b012 Rev=88.91 > S: Manufacturer=Actions > S: Product=general adapter > S: SerialNumber=ACTIONS1234 > C:* #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr=100mA > I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb > E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=1ms > E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms > E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms > I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb > E: Ad=01(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms > E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms > I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb > E: Ad=01(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms > E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms > I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb > E: Ad=01(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms > E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms > I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb > E: Ad=01(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms > E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms > I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb > E: Ad=01(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms > E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms > I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb > E: Ad=01(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms > E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms > > > This is on Linux Kernel: 6.0.8-300.fc37.aarch64 > > > This needs to be added to the usb.ids (I’ve tried submitting to the update robot but I don’t know if that is still alive): > > 10d7 Actions Semiconductor Co., Ltd > b012 ATS2851 Bluetooth 5.3 Transceiver [Ugreen CM591] > > > > Thanks in advance. > -- > Andrew McNaughton > > email: andrewmcnaughton@me.com > >