linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: pires.carvalho@gmail.com
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Kernel module btusb.c: Adding module options and Patch for Cambridge Silicon Radio
Date: Wed, 11 Sep 2019 21:10:34 +0200	[thread overview]
Message-ID: <49926046-9534-41D5-88C6-D8F53AE37F4E@holtmann.org> (raw)
In-Reply-To: <CAEG94HT5G5Z-TLf7QgGk2=rGqEpOcSm1GV=-mFCZi0=LOveKDA@mail.gmail.com>

Hi Fernando,

> Please check the attached patch proposal for drivers/bluetooth/btusb.c
> 0.8.1 (for 5.3-rc6/rc8 kernels).
> 
> I haven't tested it thoroughly but I can get sound with these changes
> on my "Cambridge Silicon Radio, Ltd Bluetooth Dongle" adapters
> (ATTRS{idVendor}=="0a12", ATTRS{idProduct}=="0001",
> ATTRS{bcdDevice}=="8891").
> 
> Also, the added kernel module parameters should allow easier testing
> of the available fixups allowing them to be turned on/off via modprobe
> (and keep traditional behavior wen not used).
> 
> * Changes: Patching for Cambridge Silicon Radio, Ltd Bluetooth Dongle(HCI mode)
> *          Adapting patches for HCI_QUIRK_BROKEN_STORED_LINK_KEY
> *              based on patch by Szymon Janc <szymon.janc@codecoup.pl>
> *              https://pastebin.com/dHepfTmR
> *          Adding patch for CSR bcdDevice == 0x8891 by Sergey Kondakov from
> *                https://bugzilla.kernel.org/show_bug.cgi?id=60824#c37
> *          Minor Changes allowing some fixups/quirks to be tested and
> *          enabled/disabled via kernel module options:
> *              debug;
> *              disable_csrfix,     force_csrfix;
> *              disable_fakecsr,    force_fakecsr;
> *              disable_npsetup,    force_npsetup;
> *              disable_sniffer,    force_sniffer;
> *              disable_intelboot,  force_intelboot;
> *              disable_scofix,     force_scofix;
> *              disable_slkfix,     force_slkfix;
> *              disable_rocfix,     force_rocfix;
> *              disable_noisoc,     force_noisoc;
> *              disable_ath3012,    force_ath3012;
> *              disable_digianswer, force_digianswer;
> *              disable_intel,      force_intel;
> *              disable_intelnew,   force_intelnew;
> *              disable_marvel,     force_marvel;
> *              disable_mediatek,   force_mediatek;
> *              disable_qcarome,    force_qcarome;
> *              disable_bcm92035,   force_bcm92035;
> *              disable_swave,      force_swave;

why would I add a ton of kernel module options?

Regards

Marcel


      reply	other threads:[~2019-09-11 19:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11 18:07 Kernel module btusb.c: Adding module options and Patch for Cambridge Silicon Radio pires.carvalho
2019-09-11 19:10 ` Marcel Holtmann [this message]

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=49926046-9534-41D5-88C6-D8F53AE37F4E@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pires.carvalho@gmail.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 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).