All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 207843] New: Some ACPI discovered BRCM HCI UART chip write clock failed.
Date: Fri, 22 May 2020 02:56:53 +0000	[thread overview]
Message-ID: <bug-207843-62941@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=207843

            Bug ID: 207843
           Summary: Some ACPI discovered BRCM HCI UART chip write clock
                    failed.
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.6.13
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: low
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: zechfox@gmail.com
        Regression: No

Created attachment 289213
  --> https://bugzilla.kernel.org/attachment.cgi?id=289213&action=edit
dmesg output

>Overview:
>>My tablet uses AP6255 wifi/bluetooth module with BCM43455 chip.
>>The bluetooth controller worked well except bluetooth headset play sound
>>glitch.It's not configuration problem in bluez or pulseaudio.
>>Some log in dmesg indicated that baud rate was not correctly configured. 
>>dmesg:
>>>Bluetooth: BCM: failed to write clock (-56)
>>>Bluetooth: Failed to set baudrate.

>Steps to Reproduce:
>>1. Power on bluetooth headset.
>>2. If it was not automatically connect, connect to headset by bluetoothctl.
>>3. play sound.
>Actual Results:
>>sound glitches.
>Expect Results:
>>sound well.
>Additional Information: 
>>I suspect the baud rate was too low to transmit audio.
>>It seems the chip can't support write clock HCI command. Then bluetooth
>>driver used default 115200 baud rate.
>>I tried to force configure 4Mbps baud rate to my chip after write clock
>>failed, but reset it failed.  Then I hardcode baud rate to 3Mbps, it solved
>>the glitch problem. 
>>And I found the commit that introduced the 4Mbsp to ACPI device:
>>https://github.com/torvalds/linux/commit/74183a1c50a3c61e62d2e585107ea3c0b942a3ff
>>It seems not all ACPI discovered devices can support write clock.
>>So maybe the driver should fallback baud rate to 3Mbps if write clock failed.

-- 
Smiles ^__________^ zech

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2020-05-22  2:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-207843-62941@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-bluetooth@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.