Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751762AbbFVOYH (ORCPT ); Mon, 22 Jun 2015 10:24:07 -0400 Received: from mail-ob0-f182.google.com ([209.85.214.182]:33215 "EHLO mail-ob0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750906AbbFVOXz (ORCPT ); Mon, 22 Jun 2015 10:23:55 -0400 Message-ID: <55881A78.7060203@lwfinger.net> Date: Mon, 22 Jun 2015 09:23:52 -0500 From: Larry Finger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Marcel Holtmann CC: Xi Ruoyao , "Gustavo F. Padovan" , Johan Hedberg , linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org, Daniel Drake Subject: Re: [PATCH] Bluetooth: btusb: Add Realtek devices into module device table References: <55860F8C.4050205@lwfinger.net> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 968 Lines: 20 On 06/22/2015 05:33 AM, Marcel Holtmann wrote: Marcel, > these Realtek devices are causing the most messy setup in a generic driver. And Bluetooth USB support has been really clean and simple for the last 10 years. I really wonder how many ways this gets done wrong before someone gets a clue and gets this right. At the end of the day this USB transport is 15 years old. > > Anyway, for obvious reasons the content of /sys/kernel/debug/usb/devices should be included here so that someone can actually look at how the USB endpoints are configured. I cannot disagree about the messiness of the Realtek setup. I hope that Xi's posting of the /sys file will help. Unfortunately, I do not have ready access to one of these devices, but I'm making arrangements to gain ssh access tomorrow so that I can test any suggested patches. Larry -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in Please read the FAQ at http://www.tux.org/lkml/