From: Stefan Wahren <wahrenst@gmx.net>
To: "Marcel Holtmann" <marcel@holtmann.org>,
"Johan Hedberg" <johan.hedberg@gmail.com>,
"Ondřej Jirman" <megous@megous.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
linux-bluetooth@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Subject: Re: [PATCH V4 01/10] bluetooth: hci_bcm: Fix RTS handling during startup
Date: Tue, 17 Dec 2019 13:59:26 +0100 [thread overview]
Message-ID: <5bbda434-d0e4-7162-8634-9900a4fa9148@gmx.net> (raw)
In-Reply-To: <6f05f4d8-fa84-ae81-ac4f-00ab12fabeea@gmx.net>
Hi Ondrej,
Am 16.12.19 um 19:28 schrieb Stefan Wahren:
> Hi Ondrej,
>
> Am 16.12.19 um 14:25 schrieb Ondřej Jirman:
>>
>> Meanwhile i will play with modifications of original patch on the
>> Raspberry Pi 4 and come back to you.
could you please test this patch [2] on top of current bluetooth-next?
This is the solution in case we don't find the cause of this issue. I
don't prefer this one, because this is next stuff and we need to revert
the offending patch for Linux 5.5.
[2] - https://gist.github.com/lategoodbye/3d39e4b07d401f07fa9f9c2f11e1f17d
>
> Thanks
> Stefan
>
> [1] -
> http://www.sparklan.com/p2-products-detail.php?PKey=4984FVukjcpylzifQiM-TGFE-IKXD--BCwf4P15KfrU&AP6256
>
next prev parent reply other threads:[~2019-12-17 12:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 15:28 [PATCH V4 00/10] ARM: Add minimal Raspberry Pi 4 support Stefan Wahren
2019-10-06 15:28 ` [PATCH V4 01/10] bluetooth: hci_bcm: Fix RTS handling during startup Stefan Wahren
2019-10-20 21:17 ` Stefan Wahren
2019-12-16 13:25 ` Ondřej Jirman
2019-12-16 18:28 ` Stefan Wahren
2019-12-16 19:42 ` Ondřej Jirman
2019-12-16 19:56 ` Stefan Wahren
2019-12-17 12:59 ` Stefan Wahren [this message]
2019-12-17 13:41 ` Ondřej Jirman
2019-12-19 19:54 ` Marcel Holtmann
2019-10-21 15:05 ` Marcel Holtmann
2019-10-06 15:28 ` [PATCH V4 02/10] ARM: dts: bcm283x: Remove simple-bus from fixed clocks Stefan Wahren
2019-10-06 15:28 ` [PATCH V4 03/10] ARM: dts: bcm283x: Remove brcm,bcm2835-pl011 compatible Stefan Wahren
2019-10-06 15:28 ` [PATCH V4 04/10] ARM: dts: bcm283x: Move BCM2835/6/7 specific to bcm2835-common.dtsi Stefan Wahren
2019-10-06 15:28 ` [PATCH V4 05/10] dt-bindings: arm: Convert BCM2835 board/soc bindings to json-schema Stefan Wahren
2019-10-06 15:28 ` [PATCH V4 06/10] dt-bindings: arm: bcm2835: Add Raspberry Pi 4 to DT schema Stefan Wahren
2019-10-06 15:28 ` [PATCH V4 07/10] ARM: bcm: Add support for BCM2711 SoC Stefan Wahren
2019-10-06 15:28 ` [PATCH V4 08/10] ARM: dts: Add minimal Raspberry Pi 4 support Stefan Wahren
2019-10-06 15:28 ` [PATCH V4 09/10] arm64: dts: broadcom: Add reference to RPi 4 B Stefan Wahren
2019-10-06 15:28 ` [PATCH V4 10/10] MAINTAINERS: Add BCM2711 to BCM2835 ARCH Stefan Wahren
2019-10-07 10:07 ` [PATCH V4 00/10] ARM: Add minimal Raspberry Pi 4 support Matthias Brugger
2019-10-11 14:46 ` Stefan Wahren
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=5bbda434-d0e4-7162-8634-9900a4fa9148@gmx.net \
--to=wahrenst@gmx.net \
--cc=f.fainelli@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=megous@megous.com \
--cc=nsaenzjulienne@suse.de \
/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).